The current spec says "Missing data can either be expressed as null or given a specific missing_value numeric or string value which is defined in the attributes". This contradicts the current CF recommendation, which says: "If only one missing value is needed for a variable then we recommend that this value be specified using the _FillValue attribute".
We should probably allow both missing_value and _FillValue, or maybe even better just restrict it to _FillValue? The more we restrict the options, the easier it is to write parsers / importers that can deal with "any valid CF-JSON"... so making it easier for the consumer / client side. But of course also less flexible.
There are definitely examples where at the moment, our APIs are breaking our spec :)
The current spec says "Missing data can either be expressed as null or given a specific missing_value numeric or string value which is defined in the attributes". This contradicts the current CF recommendation, which says: "If only one missing value is needed for a variable then we recommend that this value be specified using the _FillValue attribute".
We should probably allow both missing_value and _FillValue, or maybe even better just restrict it to _FillValue? The more we restrict the options, the easier it is to write parsers / importers that can deal with "any valid CF-JSON"... so making it easier for the consumer / client side. But of course also less flexible.
There are definitely examples where at the moment, our APIs are breaking our spec :)
http://cfconventions.org/cf-conventions/cf-conventions.html#missing-data