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 ? -CHB -- Christopher Barker, Ph.D. Oceanographer 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.bar...@noaa.gov
_______________________________________________ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
