Fix for rounding issue when formatting whole number

[0x686578]

The function sprintf discards digits after the decimal point if the format string '%d' is used, causing numbers like 35.999999999999 to be displayed as 35 instead of rounding it to 36.

This results in some quirks with coordinates like LatLongValue(52.01, 10.01) with a precision of 0.01 (in DMS format), which would be displayed as

52° 0' 35" N, 10° 0' 35" E

but should be properly rounded and displayed as

52° 0' 36" N, 10° 0' 36" E

Another example is LatLongValue(52.02, 10.02) with a precision of 0.01, which would be displayed as

52° 1' 12" N, 10° 1' 11" E

but should be displayed as

52° 1' 12" N, 10° 1' 12" E

This patch fixes this rounding issue by simply using the format string '%.0F' (0 digits after the decimal point) for whole numbers instead, in which case the number is properly rounded.

[JeroenDeDauw]

Thanks for the pull request!

+1 from my side but I'd like someone with more attention to detail to check this.

[mariushoch]

+1. Change looks good to me, but I'm not into this enough to confidently merge it.

[thiemowmde]

This is a rare IEEE edge cases, when rounding leaves a number that's a billionths of a degree smaller, but %d simply cuts instead of rounding up. I tested this for a while and can approve that this is a correct fix. Thanks a lot for submitting it!

[0x686578]

You're welcome and thanks for merging. It's weird though that this wasn't noticed before with the unit test that I also needed to correct.