Suggestions after prerelease 1.28.13

[routeconverter]

1. I like the way speed now shows the speed at under 10km/h as it has to be of benefit to walkers and bicycle riders, at a minimum. For consistent display, you might want to add that one decimal place to all speed entries. While trivial for those running at 100km/h it is still of interest, and might prove useful if challenging a speeding ticket <grin>

How accurate is the speed information? I thought its not more than 10 to 20%. Actually that was the reason why I limit the number of decimal place.

2. It would be nice, from my viewpoint, if when I asked the program to get rid of all 0 meter movement records, it were to leave the first and the last should I so desire, so that I could see the 0 km/h speed points, when the car was actually standing still. That is only possible now if I manually go through the track after selecting all of the 0 meter traveled points and unselect one at the end or start to force the program to leave 2 so that the 0 movement is only removed leaving the first and last entries at that point behind.

Ok, I understand the use case as one which is targetted at the post-processing of tracks. The program currently aims at supporting the conversion of tracks to routes. I'm really interested in supporting more use cases without increasing the complexity of the program. Any ideas how to achieve this for the 0 movements?

3 I still have to choose between having the location or having the postal address, as, for example, in a shopping trip ALL of the locations are in Lansing, but the postal address keeps changing, and NONE of the postal addresses contain the word 'Lansing'... Oh well...

Frankly, I have no idea how to solve this.

4. If I accidentally ask for the positions to be numbered twice, I end up with the number at the front of the line twice... The way to get rid of that is to re-do Add Postal Address and then re-do add position number as there is no way to 'remove' the position number if it has accidentally been added twice <grin>

Ok, put it on my todo list.

5. While the duration is one value, and an important one, the driving time is not readily available unless the 0 movement seconds can be removed, which leads back to another reason #2 above is useful, at least to me, as it permits me to more easily compute driving time since I can then calculate the 0 movement time. That could be automated, I suspect, to have the program compute both duration and travel time, which are very different in my case, since I leave the GPS on when I go shopping, and therefore often remove thousands of points from the gross track, as there are 3600 points per hour that might be 0 movement! I grant that is a nice to have, and that I can actually get it using Street Atlas, but I'd rather do it in one program if possible. There is absolutely no urgency in it, however.

Duration and travel time... I guess another post-processing use case.

6. 1 meter is 3.28083989501312336 feet and 1 mile is 1.609344 kilometers, if you need these values.

Thank you. Wikipedia helped me already.