irfan-arshad-arbisoft / mytracks

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

Bad time in kml file #1432

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. i record a track, all right
2. share to map and download kml, all right
3. but the time reported in the kml for each point is not the actual track 
time. In fact it reports the time exactly 2 hours early.

What is the expected output? What do you see instead?
I expected the local time to be in the kml - it seems standard time? my phone 
time zone is GMT+2 - is this related? looks like.  But is a hassle not to 
receive the local time in the kml. did not find a setting related to this.

What version of MyTracks are you using? On what version of Android? On what
phone?
samsung gt-i9000t, android 2.3.3, local time (automatic) is GMT+2

If possible please provide a log by uploading here.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:

Original issue reported on code.google.com by gmar...@gmail.com on 20 Dec 2013 at 9:52

Attachments:

GoogleCodeExporter commented 9 years ago
The time in the KML file is not intended to be in local time (the "Z" at the 
end is shorthand for UTC in the ISO 8601 date format).

If you want local time, you'll have to convert it yourself.

Original comment by ja...@jamesh.id.au on 13 Jan 2014 at 3:25

GoogleCodeExporter commented 9 years ago
James is right. 

Original comment by jshih@google.com on 17 Jan 2014 at 8:24

GoogleCodeExporter commented 9 years ago
Thanks for your answer
You should maybe explain this better in the help files

Original comment by gmar...@gmail.com on 18 Jan 2014 at 1:41