Re: Nio.open_file problem : object.__init__() takes no parameters

Hi David,

    Thanks for the tip ('-k'). I hoped it was a true netcdf-4 file,
because I used python-netcdf4 to create it as such, but I didn't know
how to check. What would be a netcdf-4-only feature that I could create
within a file, just to test what error PyNIO throws?

-Sourish

David Brown wrote:
> If you have a NetCDF4 version of ncdump you can answer these questions
> using the '-k' option. It turns out that TM5.th.nc4 is a regular
> NetCDF4 file, not a classic file, according to ncdump:
>
> $ ncdump -k TM5.th.nc4
> netCDF-4
>
> whereas files that are produced by the current NIO library give this:
>
> $ ncdump -k testout.nc4
> netCDF-4 classic model
>
>
> $ ncdump -h TM5.th.nc4
> netcdf TM5.th {
> dimensions:
> time = 17520 ;
> variables:
> float conc(time) ;
> }
>
> Note that the NetCDF 4 file does not contain anything actually
> incompatible with NetCDF 3. In looking at the NCL code, I see that it
> checks the format of the file, but it does not error if it's a true
> (not classic) NetCDF 4 file. So If it did encounter NetCDF4-only
> features it would probably choke. Probably it should return an error
> saying that the format is not supported yet...
> -dave
Received on Wed Feb 17 14:30:46 2010