CompanyGateways / mytracks

Automatically exported from code.google.com/p/mytracks
1 stars 0 forks source link

Timestamps of GPX/TCX export are incorrect after 23:59:59 rollover. #445

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Record a MyTracks track
2. Save track, then export as GPX or TCX.
3. Review exported file (either physical review of the file or via upload into 
a tool such as SportTracker 3.0, etc.).

What is the expected output?
Continuous trackpoint times.

What do you see instead?
At the 24:00hr rollover, the date doesn't change. For example:
Track started recording 5/3/2011 @ 18:39:30 (local time) which, in the GPX/TCX 
file it converts to 5/3/2011 @ 23:39:30. The recorded track spanned nearly 1 
hour. At the 23:59:59 roll-over, I would have expected to see the date roll to 
5/4/2011, instead, it remains at 5/3/2011 (thus showing 5/3/2011 @ 00:37:48 as 
the end time). To be sequential, shouldn't the date have rolled to 5/4/2011?

What version of MyTracks are you using? 1.1.4 On what version of Android? 2.2 
On what
phone? HTC Incredible

If possible please provide a log.  Either upload here or send to mytracks-
support@google.com.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:
Recording of other tracks which would not have hit the date/time roll-over do 
not exhibit this behavior.

MyTracks recording settings:
Announcement: Off
Split Frequency: No splitting
Min time between points: highest (recommended)
Min distance between points: 16ft (recommended)
Max distance between points: 656ft (recommended)
Minimum accuracy: 656t (recommended)
Auto-resume track timeout: 10 min

Original issue reported on code.google.com by deeme...@gmail.com on 4 May 2011 at 4:53

GoogleCodeExporter commented 9 years ago

Original comment by sandordo...@google.com on 4 May 2011 at 5:00