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.
Hi John, > There's a bug you may be aware of in ncdump -v applied to netCDF-4 files. > It always reports 'group not found'. The reason is that only varid is returned > by dumplib.c:nc_inq_gvarid() and saved in a list; the associated ncid isn't > returned or saved. But for netCDF-4 it's both you need. Thanks for reporting this bug. It's now fixed and a test added to the distribution, so it should work in the next snapshot. The behavior is a little more flexible now also. When you name a variable in the -v option, you can use either a relative name (not beginning with "/") or an absolute name (beginning with "/"). If a relative name is used, it specifies all matching variables in the file, perhaps in several groups. If an absolute name is used, then it specifies just that variable. Please let us know if you see any more problems with ncdump after getting and trying the next snapshot release. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: HKX-214469 Department: Support netCDF Priority: Normal Status: Closed