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.
Jason, Are you using the declaration implicit none to make sure the 'NF90_FORMAT_NETCDF4' flag is not merely yielding the value 0 as an uninitialized integer variable? If you compile and run the little test program I sent, we should be able to determine if the resulting foo.nc file is a classic netCDF format file or an HDF5 filoe. I suspect it is still a classic netCDF file. To find out, run ncdump -k foo.nc and if the output is classic the 'NF90_FORMAT_NETCDF4' flag is being ignored. If the output is hdf5 then a netCDF-4/HDF5 file was created. I still haven't determined when the name of the flag option was changed, but if we released a version of the F90 code in which NF90_FORMAT_NETCDF4 was a valid nf90_create() flag, we should still be supporting that name as an alias for any new name such as NF90_HDF5. Do you know if you areusing a beta version of netCDF-4 such as netCDF-4-beta1 or a daily snapshot version? --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: YTY-788071 Department: Support netCDF Priority: Normal Status: Closed