A custom attribute to identify netCDF4 files sounds perfectly reasonable as
an iteration on the netCDF4 spec.
But I'd like emphasize that it's important to continue to treat netCDF4 as
a specification rather than merely whatever libnetcdf knows how to read and
write. Doing so keeps you honest and
If you have hdf5 files that should be readable, then I will undertake to
look at them and see what the problem is.
ok, thank you
WRT to old files: We could produce a utility that would redef the file
and insert the
_NCProperties attribute. This would allow someone to wholesale
Dennis
I am in the process of adding a global attribute in the root group
that captures both the netcdf library version and the hdf5 library version
whenever a netcdf file is created. The current form is
_NCProperties="version=...|netcdflibversion=...|hdflibversion=..."
ok, good to know,
Hi,
On 21/04/16 17:33, Pedro Vicente wrote:
[...]
>>>Hmmm. Is there any big reason NOT to try to read a netCDF produced HDF5
file with
the native HDF5 library if someone so chooses?
It's possible to read a netCDF file using HDF5, yes.
There are 2 things that you will miss doing this:
1) the
DETECTING HDF5 VERSUS NETCDF GENERATED FILES
REQUEST FOR COMMENTS
AUTHOR: Pedro Vicente
AUDIENCE:
1) HDF, netcdf developers,
Ed Hartnett
Kent Yang
2) HDF, netcdf users, that replied to this thread
Miller, Mark C.
John Shalf
3 ) netcdf tools developers
Mary Haley , NCL
4) HDF,
Dear Alison,
That's great. Thank you very much for your reply.
Regards,
Alejandro
> -Original Message-
> From: alison.pamm...@stfc.ac.uk [mailto:alison.pamm...@stfc.ac.uk]
> Sent: 21 April 2016 15:27
> To: Bodas-Salcedo, Alejandro; cf-metadata@cgd.ucar.edu
> Subject: RE: [CF-metadata]
Dear Alejandro,
Apologies for the delay in replying to your question. I can confirm that these
names, units and definitions are all accepted for inclusion in the standard
name table (see
http://cfeditor.ceda.ac.uk/proposals/1?status=accepted==Alejandro+and+display=Filter)
for up to date
