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)?
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)?
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/)?
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)?
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/)?