Distance Counter

[seligman]

On my loaded data, the accumulated distance loses one decimal place after 37.9 miles. The distance column looks like this:

37.8 mi
37.8 mi
37.9 mi
37.9 mi
38 mi
38 mi
38 mi
38 mi

Is there anyway to fix this?
Any way to fix it so the distance column has two decimal places instead of one?

[routeconverter]

Is there anyway to fix this?

Yes. The limits, when the distance columns starts to reduce the number of decimal places, are configurable via the hidden options. On Windows put the following into the registry:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\JavaSoft\Prefs\slash\navigation\converter\gui\helper]
"maximum/Distance/Displayed/In/Meters"="10000.0"
"maximum/Distance/Displayed/In/Hundred/Meters"="200000.0"

maximum/Distance/Displayed/In/Meters defines the upper limit until which distances are displayed in meters (sorry, I'm sticking to the standard metric units for configuration) respectively feet.

maximum/Distance/Displayed/In/Hundred/Meters defines the upper limit until which distances are displayed in numbers with one decimal place.

Any way to fix it so the distance column has two decimal places instead of one?

There are two obstacles:

• the current logic works well for metric values - above 10000 meters it doesn't make sense to display meters, and above 200 kilometers it doesn't make sense to display 100 meters - but not for statute miles
  
• more decimal places suggest an accuracy that is very often not justified from the data