[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

960531: HDF/netCDF interface

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.

  • Subject: 960531: HDF/netCDF interface
  • Date: Fri, 31 May 96 09:29:01 -0600
Mary,

> To: address@hidden
> From: address@hidden (Mary Haley)
> Subject: HDF/netCDF interface
> Organization: UCAR/NCAR/SCD
> Keywords: 199605311456.AA07958

In the above message you wrote:

> A user of NCAR Graphics was trying to use NCL to read a netCDF file,
> but it was failing because NCL couldn't recognize the file as a netCDF
> file.  Version 2.4.2 "ncdump" couldn't recognize the file either.
> Since this file was created using the combined HDF/netCDF libraries,
> I'm wondering if it's possible for these libraries to create a netCDF
> file that the regular netCDF libraries won't be able to recognize?

Yes, it's entirely possible (expected even) that a file created by the
HDF/netCDF library via the `netCDF' API will not be accessible by the
UCAR netCDF library.  The HDF/netCDF library puts a netCDF API "veneer"
on top of their HDF library: the underlying file format is still HDF.
(The HDF software people at NCSA liked the netCDF API.)

The user will have to re-link their utility against the HDF/netCDF
library in order to access the file.

--------
Steve Emmerson   <address@hidden>