Time data in tracklog is incorrect
In fixing bug #127, time data was added back to track downloads. However, I just tried to use a downloaded track that was saved to a GPX file for geolocating photos and discovered that the time data is incorrect.
It appears that local times are being downloaded and written to the GPX file, but they are being marked in the GPX file as Universal Time (Z).
DNRGarmin always showed local times in the download window, but correctly converted the local time to UT/Z when writing to GPX.
A sample point from this morning is
<trkpt lat="42.473305464" lon="-73.142884132">
<ele>421.194824</ele>
<time>2012-03-29T08:58:18Z</time>
<name>T1</name>
<type>TRACK</type>
<extensions>
<ogr:lat>42.473305464</ogr:lat>
<ogr:lon>-73.142884132</ogr:lon>
<ogr:y_proj>914942.36215040507</ogr:y_proj>
<ogr:x_proj>64910.735318077466</ogr:x_proj>
<ogr:new_trk>False</ogr:new_trk>
<ogr:new_seg>True</ogr:new_seg>
<ogr:model>garmin GPSMap60CSX </ogr:model>
<ogr:ltime>2012/03/29 08:58:18</ogr:ltime>
</extensions>
</trkpt>
It appears that local times are being downloaded and written to the GPX file, but they are being marked in the GPX file as Universal Time (Z).
DNRGarmin always showed local times in the download window, but correctly converted the local time to UT/Z when writing to GPX.
A sample point from this morning is
<trkpt lat="42.473305464" lon="-73.142884132">
<ele>421.194824</ele>
<time>2012-03-29T08:58:18Z</time>
<name>T1</name>
<type>TRACK</type>
<extensions>
<ogr:lat>42.473305464</ogr:lat>
<ogr:lon>-73.142884132</ogr:lon>
<ogr:y_proj>914942.36215040507</ogr:y_proj>
<ogr:x_proj>64910.735318077466</ogr:x_proj>
<ogr:new_trk>False</ogr:new_trk>
<ogr:new_seg>True</ogr:new_seg>
<ogr:model>garmin GPSMap60CSX </ogr:model>
<ogr:ltime>2012/03/29 08:58:18</ogr:ltime>
</extensions>
</trkpt>
Leave a comment