This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
One other detail I think worth mentioning, if you're using ncdump/ncgen to "conserve data integrity as much as possible during conversion to netCDF", is the "-p" option of ncdump to specify precision of the string representation for floating-point values. Check out the ncdump man page documentation for this option, which says the default for floating-point and double precisions are 7 and 15 respectively, but to preserve every bit of the binary representations, you need 9 and 17 digits in the string representation for some ranges of values, as described in this paper: What Every Computer Scientist should Know About Floating-Point Arithmetic http://www.validlab.com/goldberg/paper.pdf --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: LHC-295018 Department: Support netCDF Priority: Normal Status: Closed