[CF-metadata] Use of valid_range etc. to indicate unsigned integers
Dave Allured - NOAA Affiliate
dave.allured at noaa.gov
Tue Oct 24 12:53:51 MDT 2017
I started a new ticket to split off the discussion of encoded unsigned
integers from ticket #166, add new integer types. I suggest discussion be
sent to the new ticket. "Comments are welcome."
Quick summary of the current version:
* Add type short for this encoding method, as requested by Jim Biard.
* Deprecate the entire usage of valid_range, valid_min, valid_max to encode
unsigned integers, in light of new file formats and other alternatives.
Please excuse the delay in announcing this. I am just getting used to some
of the nuances of the trac system. I did not realize that new tickets are
not automatically sent to the CF general mailing list.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CF-metadata