It may be worth noting that the IEEE-754 representation was decided by
Unidata and netCDF. If it had been left up to CF, I wonder what would
have happened? ;-)
On 2/3/17 2:41 PM, Bob Simons - NOAA Federal wrote:
...
And it seems odd to reject existing standards that have been so
painstakingly hammered out, in favor of starting the process all over
again. We follow existing standards for other things (e.g., IEEE-754
for representing floating point numbers in binary files), why can't we
follow an existing Simple Features standard?
...
--
CICS-NC <http://www.cicsnc.org/> Visit us on
Facebook <http://www.facebook.com/cicsnc> *Jim Biard*
*Research Scholar*
Cooperative Institute for Climate and Satellites NC <http://cicsnc.org/>
North Carolina State University <http://ncsu.edu/>
NOAA National Centers for Environmental Information <http://ncdc.noaa.gov/>
/formerly NOAA’s National Climatic Data Center/
151 Patton Ave, Asheville, NC 28801
e: [email protected] <mailto:[email protected]>
o: +1 828 271 4900
/Connect with us on Facebook for climate
<https://www.facebook.com/NOAANCEIclimate> and ocean and geophysics
<https://www.facebook.com/NOAANCEIoceangeo> information, and follow us
on Twitter at @NOAANCEIclimate <https://twitter.com/NOAANCEIclimate> and
@NOAANCEIocngeo <https://twitter.com/NOAANCEIocngeo>. /
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
