Unsigned byte according to CF conventions · Issue #493 · Unidata/netcdf4-python (original) (raw)
Description
opened
Reading Section 2.2 of the CF conventions I gather that I can only use np.byte datatypes but if valid_range is using np.ubyte values then the byte data should be interpreted as unsigned.
This is currently not the case in this library. If we want to support this during auto_mask_and_scale then I'm happy to look into it.
Metadata
Metadata
Assignees
No one assigned
Labels
No labels
No labels
Type
No type
Projects
No projects
Milestone
No milestone
Relationships
None yet
Development
No branches or pull requests