[CF-metadata] Add new integer types to CF?
chris.barker at noaa.gov
Thu Sep 21 15:00:43 MDT 2017
regarding all the unsigned byte talk:
I agree with Charlie's point that the "old" way need to be retained for
backward compatibility. but the text could use some clarifying. Maybe
Unsigned types should be used for unsigned data if possible. If the
underlying file format dows not support unsigned types, byte, short, or int
types can be treated as unsigned by using the NUG convention of indicating
the unsigned range using the valid_min, valid_max, or valid_range
Christopher Barker, Ph.D.
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CF-metadata