Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Hello, I could be reading the file format wrong, but I am reading the parts as specified in the BNF. Possibly (POSSIBLY), I need to wait for fixed-length data until after reading the header, but even with that, I fail to account for the attr::nelems or the corresponding nc_type, before what looks like the next attr finds its way into the header, at least in a couple of the examples I am trying to read. http://www.unidata.ucar.edu/software/netcdf/docs_rc/file_format_specifications.html http://www.unidata.ucar.edu/software/netcdf/examples/files.html att_list = ABSENT | NC_ATTRIBUTE nelems [attr ...] attr = name nc_type nelems [values ...] I am new (refreshing) with CDF, so I am likely not interpreting something quite right, or it's an undocumented gotcha. Would someone kindly look into this and let me know? I'm sure there's some nuance about the format versus the BNF that I am failing to comprehend somehow. Thank you... Best regards, Michael
netcdfgroup
archives: