Opened 6 months ago

Closed 5 months ago

Last modified 5 months ago

#6857 closed enhancement (fixed)

netCDF4 create option for valid_min/max, valid_range

Reported by: jacobst Owned by: warmerdam
Priority: normal Milestone:
Component: default Version: 2.1.1
Severity: normal Keywords:
Cc:

Description

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.

Change History (2)

comment:1 Changed 5 months ago by Even Rouault

Resolution: fixed
Status: newclosed

In 38005:

netCDF: add a HONOUR_VALID_RANGE=YES/NO open option to control whether pixel values outside of the validity range should be set to the nodata value (fixes #6857)

comment:2 Changed 5 months ago by Even Rouault

In 38006:

netCDF: add a HONOUR_VALID_RANGE=YES/NO open option to control whether pixel values outside of the validity range should be set to the nodata value (fixes #6857)

Note: See TracTickets for help on using tickets.