After upoad from Zumo 590: Tracklog "current(1) is not identical with the single tracklogs.
-
When uploading from my Zumo 590 a tracklog it brings a file "current(1)". This file is not identical with the single tracklogs and it is also not identical to the route file. What track is this "current (1)"? The current(1)-file also shows no date and time in opposite to the partial tracklogs. Thanks for any answer.
-
Could it be the track currently being recorded?
-
De ZUMO slaat in current.gpx tot ongeveer 10.000 punten op. Als dat aantal bereik wordt worden er punten overgeschreven naar een nieuw bestand; 1.gpx
Daarna 2.gpx en zo verder.
Deze staan je als je het navigatiesysteem aansluit aan een computer in de map /garmin/gpx/archieveals 1.gpx dus vol is (dus weer 10.000 punten wordt 2.gpx volgeschreven enz. tot 20.gpx
Dan heb je dus 21 bestanden met ongeveer 10.000 punten per stuk.
Het kan dus zijn dat je het eerste stuk van de track mist omdat deze naar een ander bestand verplaatst is door het toestel. -
When uploading from my Zumo 590 a tracklog it brings a file "current(1)". This file is not identical with the single tracklogs and it is also not identical to the route file. What track is this "current (1)"? The current(1)-file also shows no date and time in opposite to the partial tracklogs. Thanks for any answer.
Import all the tracklog files to mra and compare them with your route
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login-
18743.8k
-
1443.2k
-
0617
-
08211
-
05111
-
15170
-
0240
-
0228
