Unidata - To provide the data services, tools, and cyberinfrastructure leadership that advance Earth system science, enhance educational opportunities, and broaden participation. Unidata
         
  advanced  
 

[netcdfgroup] Potential inconsistency in NUG Attribute Conventions

I want to be able to use unsigned byte and/or unsigned short integers to
store "compressed" data. Under "compressed" I mean floating point values
mapped into integer values via the 'scale_factor' and 'add_offset'
attributes.

The description of the deprecated 'signedness' attribute states:
"Deprecated attribute, originally designed to indicate whether byte
values should be treated as signed or unsigned. The attributes
'valid_min' and 'valid_max' may be used for this purpose. For example,
if you intend that a byte variable store only nonnegative values, you
can use 'valid_min' = 0 and 'valid_max' = 255. This attribute is ignored
by the netCDF library."

How that scheme is supposed to work with 'scale_factor' != 1 and
'add_offset' != 0 ? It would have been simple if 'valid_range' was
referring to the stored, not yet unpacked(unscaled) variables, but it
does not seems to be the case.


Regards,
         Sergey Panov





 
 
  Contact Us     Site Map     Search     Terms and Conditions     Privacy Policy     Participation Policy
 
National Science Foundation (NSF) UCAR Community Programs   Unidata is a member of the UCAR Community Programs, is managed by the University Corporation for Atmospheric Research, and is sponsored by the National Science Foundation.
P.O. Box 3000     Boulder, CO 80307-3000 USA     Tel: 303-497-8643     Fax: 303-497-8690