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 Paul, > I've just noted a quirk with the latest 3.6.3 netcdf release - it's > described below.. > > Basically, ncdump (3.6.3) complains when non [A-Za-z] characters are the > leading characters in a file name.. This behaviour was not a symptom > of 3.6.2 (as per below).. > > I haven't tried the latest 4.1.1 release, however thought it best to report > this.. > > The host machine is a SUSE10.2 (x86_64) version - the 3.6.2 binaries were > compiled by me (sourced from unidata), the 3.6.3 are system-installed.. > > Cheers, > > P > > *** > 3.6.3: > dur041> ncdump -h > ~/Shared/Temperature/GISTEMP/100506_GISTEMP-corrected-smooth1200_188001-201003.nc > ncdump: name begins with space or control-character: 1 > dur041> which ncdump > /usr/local/bin/ncdump > dur041> /usr/local/bin/ncdump -h > ... > netcdf library version "3.6.3" of Feb 24 2009 13:21:02 $ Thanks, his was a bug in 3.6.3 and 4.0 that has been fixed in subsequent releases: http://www.unidata.ucar.edu/netcdf/docs/known_problems.html#ncdump-numeric-filename The 4.1.1 release fixes other bugs as well, and provides just the netCDF-3 libraries if you don't have HDF-5 installed. But making the one-line change described at the above URL will also fix the problem in 3.6.3. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: QXN-890248 Department: Support netCDF Priority: Normal Status: Closed