Bug in duration shown for my tracks

[RsH]

Unfortunately, I'm not letting the program print out the relevant information into the log but onto the console. So I need the console output. The problem has to to do something with time zones, which I thought I had eliminated by explicitly using GMT.

[Also sent in an email...]
Keyed in manually from the Command Prompt window:

java -jar routeconverterprerelease.jar
Logging to C:\...\RouteConverter.log
GMT: Jul 13, 2009 11:15:39 AM
milliSeconds: 0 cal: Dec 31, 1969 7:00:00 PM
minus one hour: Dec 31, 1969 6:00:00 PM
GMT: Jul 13, 2009 11:15:39 AM
milliSeconds: 0 cal: Dec 31, 1969 7:00:00 PM
minus one hour: Dec 31, 1969 6:00:00 PM
GMT: Jul 13, 2009 11:15:39 AM
milliSeconds: 0 cal: Dec 31, 1969 7:00:00 PM
minus one hour: Dec 31, 1969 6:00:00 PM
GMT: Jul 13, 2009 11:15:43 AM
milliSeconds: 0 cal: Dec 31, 1969 7:00:00 PM
minus one hour: Dec 31, 1969 6:00:00 PM
GMT: Jul 13, 2009 11:15:43 AM
milliSeconds: 5541000 cal: Dec 31, 1969 8:32:21 PM
minus one hour: Dec 31, 1969 7:32:21 PM
GMT: Jul 13, 2009 11:15:44 AM
milliSeconds: 0 cal: Dec 31, 1969 7:00:00 PM
minus one hour: Dec 31, 1969 6:00:00 PM
GMT: Jul 13, 2009 11:15:44 AM
milliSeconds: 0 cal: Dec 31, 1969 7:00:00 PM
minus one hour: Dec 31, 1969 6:00:00 PM
GMT: Jul 13, 2009 11:15:44 AM
milliSeconds: 122000 cal: Dec 31, 1969 7:02:02 PM
minus one hour: Dec 31, 1969 6:02:02 PM
GMT: Jul 13, 2009 11:15:44 AM
milliSeconds: 3483000 cal: Dec 31, 1969 7:58:03 PM
minus one hour: Dec 31, 1969 6:58:03 PM
GMT: Jul 13, 2009 11:15:44 AM
milliSeconds: 5471000 cal: Dec 31, 1969 8:31:11 PM
minus one hour: Dec 31, 1969 7:31:11 PM
GMT: Jul 13, 2009 11:15:44 AM
milliSeconds: 5541000 cal: Dec 31, 1969 8:32:21 PM
minus one hour: Dec 31, 1969 7:32:21 PM
GMT: Jul 13, 2009 11:15:46 AM
milliSeconds: 0 cal: Dec 31, 1969 7:00:00 PM
minus one hour: Dec 31, 1969 6:00:00 PM
GMT: Jul 13, 2009 11:15:46 AM
milliSeconds: 0 cal: Dec 31, 1969 7:00:00 PM
minus one hour: Dec 31, 1969 6:00:00 PM
GMT: Jul 13, 2009 11:15:46 AM
milliSeconds: 122000 cal: Dec 31, 1969 7:02:02 PM
minus one hour: Dec 31, 1969 6:02:02 PM
GMT: Jul 13, 2009 11:15:46 AM
milliSeconds: 3483000 cal: Dec 31, 1969 7:58:03 PM
minus one hour: Dec 31, 1969 6:58:03 PM
GMT: Jul 13, 2009 11:15:46 AM
milliSeconds: 5471000 cal: Dec 31, 1969 8:31:11 PM
minus one hour: Dec 31, 1969 7:31:11 PM
GMT: Jul 13, 2009 11:15:46 AM
milliSeconds: 5541000 cal: Dec 31, 1969 8:32:21 PM
minus one hour: Dec 31, 1969 7:32:21 PM

C:\....\GPS [ended program, back to DOS prompt.

So the program seems to have done the same thing, time wise, three times in the above list of what appears in the Command Prompt window, before I closed the program down. However that GMT: Jul 13 2009 11:15:46 AM is NOT GMT, but the time here in EDT or GMT-4 in Toronto at this time, as it is the time showing on my computer. If it was supposed to be GMT then it would have to have been 3:15:46 PM or, without the AM/PM 15:15:46 GMT to match the local time. Note also that Windows XP is set to show a 24 hour clock on my desktop, so it shows 15:15 when it is 3:15 PM local time. That likely has nothing to do with the problem, as that is a recent change I made to my time display and the 18 hour difference existed before that change was made as well as now, after it was made. Also that 7PM time was there at 9AM this morning, local time, when I first ran the program and saw this type of display in the window, so that fact that the actual time changed by over 2 hours did NOT impact the result. All of the other times, and the millisecond offsets from 0 to the final value are identical. I do not recall if the intermediate millisecond numbers were the same or not, but that should not matter...

Hope that helps..

RsH [AKA Bob]