07.09.2009, 23:37
(07.09.2009, 19:04)routeconverter Wrote:(07.09.2009, 17:23)RsH Wrote: I've already pointed out Route Converter on that site in my review, but would ADD to that review by stating that Route Converter will correct the time problem that Streets and Trips has created.
Date, time and especially time zones are not my friend in Java. Please try the latest prerelease 1.29.16 whether it works for you. I was very conservative and thus RouteConverter should convert the time from track (and only track) positions in a GPX 1.1 file with creator "Microsoft Streets & Trips" from the time zone to GMT.
On my machine, a position with "2009-09-04T19:10:03-05:00" is shown in the UI as "2009-09-05T02:10:03 AM" (local time: GMT+2) and stored as "2009-09-05T00:10:03.000Z" (GMT). Does that make sense?
The real time of the file was between 15:10:03 and 15:24:45 and the file was created at 15:29:26 showing that it covered 19:10:03-05:00 to 19:24:45-05:00 when it should have shown 19:10:30Z to 19:24:45Z if my math is correct. Or so I think. Let me try again tomorrow to create a path where I am definite on the precise time and look at it. Note that that 15:29:26 creation time is in the header information, created by S&T when I exported the GPX data, and is based on the actual time EDST in Toronto.
So you should be showing 21:10:03 I think if you are 2 hours east of Zulu time. I'm frankly not certain what they are doing at this point!