fixed [REPORTED]Steerpoint creation, decimals enter 1 lower then typed

I noticed that decimals that you type in when creating new steer points don't enter exactly what you typed in, for example

I typed in N26.10.478

and it came out as N26.10.477 when I pressed enter.

This doesn't happen all the time, some are entered correctly.

F16 new stp decimal wrong .trk

For some reason, it rounds some numbers.

I’ve seen this as well.

<shrug>

It happens in a lot of DCS modules or even simulators beyond DCS. My guess is that it's something like

userInput -> function.convertLLtoXYZ -> store XYZ

retrieve XYZ -> function.convertXYZtoLL -> displayLL

Due to rounding or truncation or whatever this round trip through conversions alters the number slightly.

The only way to be sure that display doesn't change is to store the entered value separately than the converted positional information or fix the conversation process to have enough precision, round nearest instead of truncate, or whatever mathematical prudence makes such errors impossible.

I wonder: Is the six-digit LAT/LON the Hornet can enter more or less accurate than the seven-digit LAT/LON used by the Viper (with it’s tendency to round)?

What about the A-10C? Does it round seven-digit LAT/LON?

(Yes, I know there are proper names for the different coordinates versions, but they escape me at the moment)