16.10.2017, 21:28
> Did the case that a double isNaN() really occur with your files?
> Why didn't you introduce a method to check double for null and isNaN()?
For GPX 1.1 I introduced two new formatting functions formatSpeedAsDouble() and formatTemperatureAsDouble(), which call formatDouble, which returns NaN in case of null. Because of that I had to fix isEmpty(), reorganize setting the value (maybe not necessary) and added some additional checks for isNaN (again maybe not necessary).
> Why did you increase the accuracy of elevation to centimeters when it's decimals at best?
I just set the same accuracy as it was already set in formatElevationAsString() (= 2). Maybe both should be at 1 then?
> Why didn't you introduce a method to check double for null and isNaN()?
For GPX 1.1 I introduced two new formatting functions formatSpeedAsDouble() and formatTemperatureAsDouble(), which call formatDouble, which returns NaN in case of null. Because of that I had to fix isEmpty(), reorganize setting the value (maybe not necessary) and added some additional checks for isNaN (again maybe not necessary).
> Why did you increase the accuracy of elevation to centimeters when it's decimals at best?
I just set the same accuracy as it was already set in formatElevationAsString() (= 2). Maybe both should be at 1 then?