31.12.2010, 23:53
(31.12.2010, 18:47)routeconverter Wrote: 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...
I actually compared 2.0 and 2.1 side-by-side (as I couldn't remember what 2.0 did, 2.1 seemed a bit of a shock...) and 2.0 seemed to correctly convert UTC time (in the GPS log) to local time in RC display.
That's where the "didn't make sense" came from

(31.12.2010, 18:47)routeconverter Wrote:(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?
I certainly would (always willing to help)!
I think another option would be the ability to set the timezone of the file. I think that'd be simpler, could be stored as an .ini next to the file. The only difficulty would be if the one file had various timezoned points in it (how often does that happen?).
Certainly, having the option to access a webservice would be neat (and almost perfect?), but does require www access (so a fallback option would be beneficial anyway??)