Changes between Initial Version and Version 1 of Ticket #4215
- Timestamp:
- 10/24/18 05:57:31 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4215 – Description
initial v1 6 6 principle this should still be acceptable but the actual implementation (in a poorly documented 7 7 “feature”) does this by converting every value to an integer. So pixels with a temperature of 8 13.49 and 12.51 are merged incorrectly (and the value stored is 13 which is also incorrect) }}} 8 13.49 and 12.51 are merged incorrectly (and the value stored is 13 which is also incorrect) 9 }}} 9 10 10 11 Looking at code we have branching on whether GDAL>F<Polygonize is available, and that looks hardcoded to "no". We're supporting GDAL 1.10+ and GDALFpolygonize is available since 1.9.0, so branching can be removed.