[netCDF #QZA-368409]: netcdf 4 file names

Hi Niles,

> There is/was a known bug with netcdf 4 in that
> file names beginning with "0", "1" or "2" are
> not accepted :
> 
> /usr/local/netcdf4/bin/ncdump ./000000.mdv.nc
> /usr/local/netcdf4/bin/ncdump: name begins with space or
> control-character: 0
> 
> See :
> 
> http://www.unidata.ucar.edu/support/help/MailArchives/netcdf/msg05527.html
> 
> This seems to be present in the version we have installed. Is there
> a release we could grab that does not have this? Many of our
> netcdf files that are generated from mdv files use an
> hhmmss.mdv.nc naming convention (ie. 234009.mdv.nc) and so
> necessarily fall into this bug.

Yes, the bug and fix are described here:

  
http://www.unidata.ucar.edu/software/netcdf/docs/known_problems.html#ncdump-numeric-filename

This bug is fixed in the daily snapshot release and in 4.0.1-beta, 4.0.1, and 
subsequent releases.  Also a one-line 
patch to ncdump/dumplib.c (for either netCDF-4.0 or netCDF-3.6.3) is to replace 
the line

    if((*cp >= 0x01 && *cp <= 0x32) || (*cp == 0x7f))

with the following line instead

    if((*cp >= 0x00 && *cp <= 0x20) || (*cp == 0x7f))

--Russ

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: QZA-368409
Department: Support netCDF
Priority: Normal
Status: Closed