NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTE: The netcdf-hdf mailing list is no longer active. The list archives are made available for historical reasons.
I did not see this addressed in the mailing list.
Perhaps, this has not been pondered.
The netCDF v3 file extension has been generally
accepted to be ".nc". The new netCDF-HDF5 merger will
write ".h5" HDF5 files. However, the API can not read
a general HDF5. But, only an HDF5 file that was
written by this API.
So, has there been thought to a file extension that
might represent a new netCDF-HDF5 file? If I give
someone a .nc file (which is really an HDF5 file),
they will not be able to read it unless they have
recompiled with the new library. If, however, I send
them, say, a ".nc4" file. They will know immediately
that this is a "new" HD5-based netCDF file. Whew!
Thoughts?
Paul
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
netcdf-hdf archives: