31.12.2010, 18:47
(31.12.2010, 02:13)scribbly Wrote: Just upgraded to 2.1 (thanks BTW), and noted that a new feature "always displays times in GMT/UTC timezone" and was just wondering why this was done (as it doesn't really make any sense)?
GPS data is always UTC. And I hope with 2.1 all timezone-related bugs are squeezed out of the code. Lots of users complained about them...
(31.12.2010, 02:13)scribbly Wrote: Well, it makes sense in that it's the GPS value exactly and converting to current timezone will not be correct in all situations, but having to add 10 or 11 hours (dependant on DST) is a little frustrating.
Am wondering if it may not be better to add a timezone to the GPS log (for quick and dirty conversions)?
Well, if it would be that easy... but determining the correct timezone for a GPS position and a GMT-time is non-trivial.
(31.12.2010, 02:13)scribbly Wrote: Or is it possible to get the timezone of the track (probably need to be points I guess) and then convert to local (eg http://chrischandler.name/ruby/convertin...timezones/)?
I thought about using http://www.geonames.org/export/web-servi...l#timezone to convert GMT-timezones to local ones. Would you be willing to test and validate the results it produces?
--
Christian
Christian