Skip to content

Can 2.8.0 still create netCDF3 Classic ? #99

@jypeter

Description

@jypeter

@dnadeau4 and @doutriaux1 If I run the script at the end of #98 , I expect to get netCDF3 Classic because I have specified:

# Write NetCDF3 Classic
value = 0
cdms2.setNetcdfShuffleFlag(value) ## where value is either 0 or 1
cdms2.setNetcdfDeflateFlag(value) ## where value is either 0 or 1
cdms2.setNetcdfDeflateLevelFlag(value) ## where value is a integer between 0 and 9 included

If I run the script with my old 2.1.0, I do get NetCDF3 Classic

> ncdump -k t2m_1851.extracted.daily.nc
classic

But If I use 2.8.0, I get netCDF-4 classic

> ncdump -k t2m_1853.extracted.daily.nc
netCDF-4 classic model

Note that if I comment out the cdms2.set lines in the script and run it with 2.1.0, I also get netCDF-4 (as expected)

> ncdump -k t2m_1851.extracted.daily.nc
netCDF-4 classic model

Is this a bug in 2.8.0? Or is there a new flag you have to use if you want netCDF3?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions