Erratic location and times in GPX exports

[GoogleCodeExporter]

My Tracks 1.1.13

Problem appeared after 2011 12 24, probably since version 1.1.13.
Verified only on GPS exports, data in db deleted, and now back to 1.1.9.
File in attachement is an example, but all GPS exports have same problems.
Time problem is very common, location problem uncommon.

Thanks for your work.
Benoît Hommel

Original issue reported on code.google.com by benoit.h...@gmail.com on 3 Jan 2012 at 1:08

Attachments:

• [281211 1255.gpx](https://storage.googleapis.com/google-code-attachments/mytracks/issue-743/comment-0/281211 1255.gpx)

[GoogleCodeExporter]

Verified only on GPS exports -> Verified only on GPX exports

Original comment by benoit.h...@gmail.com on 3 Jan 2012 at 1:12

[GoogleCodeExporter]

Hi,
The tracks has the correct date but when I import to GPX it adds a day. I 
didn't detected any problem with location. I synchronized with pictures adding 
an offset day on the date.
I'll try to correct GPX.

Original comment by fjherra...@gmail.com on 9 Jan 2012 at 10:05

[GoogleCodeExporter]

Hi,

I think there is no problem with gpx export, but only on data recording (in
db).  But I only check data on PC with gpx files, I never check data in
MyTrack.
Am I really the only one having this problem?

Original comment by benoit.h...@gmail.com on 9 Jan 2012 at 10:47

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi Benoît,
I'm only a user. I forgot to say before. That was the problem I had and how I 
fix it.
The tracks' dates is OK in phone's tracks' list. But when I check the dates on 
the GPX file it have the next day date that the tracks were recorded.
I was annoyed for that before I realized that the GPX files have the correct 
date in the GPX files' name (the true date and hour) but the points' dates (or 
trkpt on XML GPX file) in the GPX files are the next day.
EG:
I recorded a track on 2012/1/3 13:48:05.
The GPX file's name is "2012/01/03 13:48:05.gpx" but the points inside this 
file the time flags are <time>2012-01-04T13:48:05Z</time>
This error make me crazy while I was trying to synchronize pictures with that 
GPX file because Geosetter (an EXIFtool GUI) said there are no track for that 
date. Now I synchronize adding a day of offset.
You could try to open on a text editor your GPX files and check the <time> 
flags.
When did you save the track you attached in your original post?
Regards.

Original comment by fjherra...@gmail.com on 9 Jan 2012 at 11:26

[GoogleCodeExporter]

Hello,

I think your problem is different. What is your version ? I think it
isn't 1.1.13.
Your GPX files names are in form "yyyy mm dd". Since version 1.1.13 GPX
files are in local form with short year (for me, in France," dd mm yy").
And my GPS track didn't have your problem. His name is "281211 1255.gpx"
(it's mean 28 december 2011 in french format) and all dates in are on 28
december 2011.

You can open another case (with your correct version number).

Original comment by benoit.h...@gmail.com on 10 Jan 2012 at 7:22

[GoogleCodeExporter]

Hello,
Mine is 1.1.13 too. The format for dates in Spain is dd/mm/yyyy and the GPX
track are saved in the same way. I wrote with that format because I thought
tracks were exported in that way.
Regards.

Original comment by fjherra...@gmail.com on 25 Jan 2012 at 11:50

[GoogleCodeExporter]

Hi Benoit,

I looked at all the "<time>" tag in your attached "281211 1255.gpx" file. Can 
you tell me why they look erratic to you?

fjherranzt,
Can you test if the extra day error is still occurring with My Tracks 1.1.15. 
If so, please file a new bug.

Thanks

Original comment by jshih@google.com on 29 Feb 2012 at 11:18

[GoogleCodeExporter]

Looks like some GPS chip had a bug that didn't take into account leap year. 
Thus the GPS chip reports the date off by one. This requires a hardware update.

Original comment by jshih@google.com on 21 Jun 2012 at 10:36

• Changed state: WontFix