[CF-metadata] Add new integer types to CF?
chris.barker at noaa.gov
Sun Sep 10 16:39:13 MDT 2017
lookslike a good idea.
one thought: maybe toolate now, but:
One byte numeric data should be stored using the byte
or unsigned byte data type. It is possible to treat the byte type as
> unsigned by using the NUG convention of indicating the unsigned range
> using the valid_min, valid_max, or valid_range attributes.
So is there an "unsigned byte" type or not? if so, why bother with the text
about valid-min, etc....?
In my experience, unsigned byte is far more common that signed byte anyway.
(is it too late to call them something like uint8 and int8 ?
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