lookin at the NUG, how about saying: In file types that don't offer native support for unsigned types, integer or byte variables that are to be interpreted as unsigned must have the attribute _Unsigned = "true".
On Fri, Sep 22, 2017 at 1:10 AM, Chris Barker <[email protected]> wrote: > LGTM. > > "One byte numeric data should be stored using the byte >> > or unsigned byte data type." >> > > >> It too is copied from CF 1.7, and I think its intent was to tell >> people to store 1-byte numeric data as type byte not type char. >> With that rationale, if the sentence was in 1.7 then >> it should probably be in 1.8, > > > yup --it's clear to me, and not annoyingly redundant. > > The truth is that char type IS used a lot on old C code for numeric data. > > -CHB > > > >> although I'll go with >> the consensus. >> >> -- >> Charlie Zender, Earth System Sci. & Computer Sci. >> University of California, Irvine 949-891-2429 )'( >> _______________________________________________ >> CF-metadata mailing list >> [email protected] >> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata >> >> > > > -- > > 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 > > [email protected] > > _______________________________________________ > CF-metadata mailing list > [email protected] > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > > -- Dr. Richard P. Signell (508) 457-2229 USGS, 384 Woods Hole Rd. Woods Hole, MA 02543-1598
_______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
