Keeping the date and time as I move points

[RsH]

I have now completed the cruise and have lots of GPX files where the path has deviated from the actual road due to tall buildings, too many waves while at sea, and just unaccounted for jumps to the left or right of the actual path the ship, bus, taxi or walker took. I want to eliminate spurious points at the start and end of each GPX file, where the ship was not yet moving, or while I was sitting down in place with the I-GotU recording puck in my pocket. However that leaves the points during the excursion where I need to move the point back to the road, or slightly off the road for a stop, or otherwise shift the point. When i do that with an existing point I want to KEEP the date and time already assigned to that point. However Routeconverter removes the date and time, forcing me to manually put it back, since I then use the corrected file for geocoding my photographs. That, in fact, is the reason behind the GPX files in the first place, and without the date and time in the GPX file the whole is useless for doing any geocoding.

HELP... I need a way to KEEP the date and time for each point, even when I manually shift them. I can always then adjust the time slightly if it is appropriate, without also having to reenter the date as well. I am looking to retain my data and reduce the manual key entry of data that was IN the file when I started.

RsH

[routeconverter]

I want to eliminate spurious points at the start and end of each GPX file, where the ship was not yet moving, or while I was sitting down in place with the I-GotU recording puck in my pocket.
[..]
I need a way to KEEP the date and time for each point, even when I manually shift them.

Hi Robert,

I've changed the behaviour for the 2.0 version since a user convinced me that modifying the coordinates of a recorded position means time and elevation cannot be the same as before.

Since 4 or 5 users have already complained about this, I'm changing the behaviour back to that of the pre-2.0 version: moving a position does not affect time and elevation. Please download the latest prelease if you'd like to profit from this change.

For those, who like the 2.0 behaviour, there is a registry switch in the hidden RouteConverter options to change the behaviour:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\JavaSoft\Prefs\slash\navigation\converter\gui\mapview]
"clean/Elevation/On/Move"="true"
"clean/Time/On/Move"="true"

gives the 2.0 behaviour back.

[RsH]

Thank you for making this change. I find that I can insert points, move points and then refine the positions of the points via use of the 'speed' calculation. I then get the inserted points in approximately the correct position relative to those I have not moved by keeping the speed within a kilometer an hour of the original speed. At the distances I am working with, the errors will only be on the order of a few meters, which are no more than the errors of the GPS in the first instance. Having to play with the date and time for every moved point was just one added obstacle to successfully refining the points, particularly in a city where tall buildings shift the points via reflection of satellite signals.