Export/import GPX has a 3-hour offset

[GoogleCodeExporter]

Instructions to reproduce:
- Open mytracks
- select an already recorded track
- export it as gpx
- delete or rename original track
- rename exported gpx on SD card
- import gpx back (open from file manager)
- export gpx again - you will then have two gpx files

Expected:
The files should be exactly the same (except for the name difference since
you renamed the file before importing)

Actual:
Every point in the file has shifted timestamps between the two.

Possible cause:
Either the importer or exporter is not taking timezones into account.

Attached is an example of such two files. I suspect timezones because the
time difference is 3 hours, and I'm in GMT-3.

Original issue reported on code.google.com by rdama...@google.com on 18 May 2010 at 5:38

Attachments:

• 8106.gpx
• 8106test.gpx

[GoogleCodeExporter]

I think your suspicions were right, the importer is not taking time zones into 
account. Solved in Issue 61.

Original comment by steffen.horlacher@gmail.com on 6 Jun 2010 at 9:04

[GoogleCodeExporter]

Not sure if this should go into this GPX export/import issue, but there is also 
the problem that:
1) Splits are contained in the exported GPX file created by My Tracks, but upon 
import they are gone.
2) Because of the missing the splits following import, the "Moving Time" that 
originally displayed, and can be calculated from the splits, is way off 
(example below)
3) Because the "moving time" is way off, the "Average Moving Speed" is wrong.

In the attached file, I remember (and my secondary cycling computer confirmed) 
before exporting the GPX that the "moving time" was 4hr22min, and the "average 
moving speed" was 16.07mph.  After importing, the new "moving time" that is 
displayed in My Tracks is 4:43:37 and the "average moving speed" is 14.85mph.  
Had I not recorded the original elsewhere, and/or had the ability to use my XML 
parser to recalc from the GPX file, it would be quite depressing to have lost 
the accurate data simply because of the import of a GPX file that "My Tracks" 
created by export. 

Thanks

Original comment by donso...@gmail.com on 31 Aug 2010 at 5:28

Attachments:

• HotterNHell100First70mi.gpx

[GoogleCodeExporter]

That most definitely counts. There are a few other TODOs for the GPX importer, 
such as waypoints.

Original comment by rdama...@google.com on 31 Aug 2010 at 5:42

[GoogleCodeExporter]

Issue 138 has been merged into this issue.

Original comment by rdama...@google.com on 1 Sep 2010 at 4:45

[GoogleCodeExporter]

Original comment by rdama...@google.com on 1 Sep 2010 at 10:54

• Changed state: Started
• Added labels: Priority-Low, Work-Small
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Oops, didn't mean to change the priority

Original comment by rdama...@google.com on 1 Sep 2010 at 10:58

• Added labels: Priority-Medium
• Removed labels: Priority-Low

[GoogleCodeExporter]

This is fixed and verified with.

Original comment by rdama...@google.com on 25 Sep 2010 at 12:14

• Changed state: Verified