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.
Wei-keng, > I notice the value of FILL_DOUBLE defined in the classic format spec contains > only 6 bytes. > FILL_DOUBLE = \x47 \x9E \x00 \x00 \x00 \x00 //(double)9.9692099683868690e+36 > > Shouldn't it be? (2 tail bytes are missing) > FILL_DOUBLE = \x47 \x9E \x00 \x00 \x00 \x00 \x00 \x00 > //(double)9.9692099683868690e+36 > > I can see it is just the same copy from the formal document from NASA "NetCDF > Classic and 64-bit Offset File Formats". Maybe contact them to fix? Yes, you're right, thanks for reporting this! We'll fix it for the upcoming release. I'll send a note to NASA as well. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: OYN-551561 Department: Support netCDF Priority: Normal Status: Closed