Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Tom Rink wrote:
Hi, We would like to use the Java-NetCDF library, which I believe is the basis of the CDM, for reading HDF5 files. Since the final version of these files has not been finalized, we need to know if the Java-NetCDF library can completely read *any* HDF5 file produced by the native version of the HDF5 library. Is it possible to use some HDF5 structure for data that would not be even recognized, and thus, and be readable? Tom _______________________________________________ netcdf-java mailing list netcdf-java@xxxxxxxxxxxxxxxxFor list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
Hi Tom:As of version 4.1, the CDM can read all versions of HDF5 through version 1.8.4, except for the following HDF5 features:
SZIP compression. The SZIP library is proprietary and does not have a Java implementation. Its not clear if we can even legally write one if we wanted to.
Dataset region references. These are used in NPOESS, but their purpose is unclear. Since they point to other datasets that are accessible through the CDM, all the data in the file can still be read by the CDM. However, whatever information the region reference represents is not currently accessible.
There may be something Ive missed, but its likely minor and would be considered a bug (ie fixed). Ive heard rumors of new features in future versions of HDF5, so stick with 1.8 for now.
netcdf-java archives: