Closed soxofaan closed 2 years ago
Yeah, so this was meant to say that NaN is not implicitly also a no-data value as some may have understood it. Of course, it should possible that NaN is a nodata value if explicitly specified as such. I'll issue a PR to fix this.
See PR #362
In our geotrellis implementation IEEE754 NaN is used as no-data value for float raster cubes.
This creates a conflict in the definition of
is_nodata(NaN)
: https://github.com/Open-EO/openeo-processes/blob/2cfd022fdc4826af89166d88880a873cbea20e90/is_nodata.json#L4=>
is_nodata(NaN) = true
=>
is_nodata(NaN) = false