GPX export import extends the track time by one hour

Graf Geo shared this problem 34 hours ago
In Progress

By chance I have now noticed the following problem:

When I export a track as gpx and then import it again, the track time is regularly displayed as being exactly one hour too long.

This only happens with tracks created with the route planner, not with recorded tracks. It could therefore have something to do with the timestamps that Locus generates when planning.

When I look at the gpx of an example track with an editor, the time values look as planned:

First trackpoint: <time>1970-01-01T00:00:00.000Z</time>
Last trackpoint: <time>1970-01-01T02:17:20.267Z</time>

So 2 hours, 17 minutes, 20 seconds.

After import, Locus will then display 3:17:20. See screenshot.

Now I exported the imported track again as GPX and noticed that the first track point now has this timestamp:

<time>1969-12-31T23:00:00.000Z</time>

So exactly 1 hour early, which explains the wrong time. All other trackpoints have a 1970 timestamp unchanged.

What is the reason for this and can it be fixed?

Replies (2)

photo
1

Hi, is the route planned in the app or on the web?

photo
1

Route Planner (App).

photo
photo
1

I investigated the problem further.

It happens during import when the first track point is exactly 0 (zero), i.e.

<time>1970-01-01T00:00:00.000Z</time>


As soon as I edit it to just 1 second, i.e.

<time>1970-01-01T00:00:01.000Z</time>


the track time is displayed correctly after import.


Unfortunately, the first track point is always generated with zero during export; having to edit it manually every time can't be the solution.


Even a single millisecond is enough, as long as it's not completely zero.


<time>1970-01-01T00:00:00.001Z</time>

Leave a Comment
 
Attach a file