netCDF4 create option for valid_min/max, valid_range
|Reported by:||jacobst||Owned by:||warmerdam|
Current netCDF driver reads the CF attributes, including valid_min, valid_max and valid_range. Moreover, it honours them by eg putting pixel values outside valid_range to no-data value when the data variables are read.
Underlying netCDF libs typically make this range-filtering optional and it could be undesirable for users (each pixel value needs to be checked against the range, which can affect read speeds for large files).
Please add a create option (-co) to netCDF driver to make it read pixel values as they are stored, ie regardless if they are inside or outside of valid_range.