is_nodata(NaN) when NaN is used as no-data value ?

[soxofaan]

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):

openeo-processes/is_nodata.json

Line 4 in 2cfd022

"description": "Checks whether the specified data is missing data, i.e. equals to `null` or any of the no-data values specified in the metadata. The special numerical value `NaN` (not a number) as defined by the [IEEE Standard 754](https://ieeexplore.ieee.org/document/4610935) is not considered no-data and must return `false`.",

data is missing data, i.e. equals to null or any of the no-data values

=> is_nodata(NaN) = true

The special numerical value NaN as defined by IEEE Standard 754 is not considered no-data and must return false.

=> is_nodata(NaN) = false

[m-mohr]

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.

[m-mohr]

See PR #362