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

Re: netcdf/mfhdf

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: Re: netcdf/mfhdf
  • Date: Wed, 9 Apr 1997 15:47:00 -0600
On Apr 9,  5:19pm, Arlindo da Silva wrote:
> Subject: Re: netcdf/mfhdf
> Glenn,
>
> >
> > If you didn't hear it from us, or from NCSA, then you can't really count on
it.
> > If you heard it from us or from NCSA, then we already told you all we were
> >  willing to commit to publicly. :-)
> >
>
> I was afraid of that...
>
> > UCAR/Unidata and NCSA's HDF group drafted a memo which basically stated our
> > intention to work cooperatively towards a file format our interfaces can
> > share. The idea is that if/when either of us has to come up with a *new*
file
> > format, different from our current respective ones, that we will share
> > the format. This would reduce the backward compatibility and
interoperability
> > features to a single feature.
>
> I see. I thought the integration would happen at the API level. I just
> ported both NetCDF and HDF to the Cygnus GNU Win32 compiler (I'll post
> something on that soon), simply because MFHDF cannot write XDR. I was
> hoping this feature was coming soon. I guess not.
>
>   Thank you for your answer.
>
>         Arlindo.

BTW, for any porting work on the netcdf C library,
you should probably use netcdf-3.
ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf-3.3a.tar.Z

This really should have been marked as "released" by now, but
the documentation is hung up. Netcdf-3 ports much more easily
than netcdf-2.

-glenn