NOTE: The netcdf-hdf mailing list is no longer active. The list archives are made available for historical reasons.
From: NCF::CDFSUPPORT 21-MAY-1992 11:20:00.63
To: @CDFUSERS
CC: CDFSUPPORT
Subj: CDF Version 2.2 Release Announcement
Dear CDF users,
With great fanfare we would like to announce the release of CDF
V2.2.0 (we know, it's about time). CDF V2.2 has been ported to the
IBM PC running MS-DOS (as well as another UNIX machine, the HP 9000
series running HP-UX). A number of other enhancements have been
made which are described in the "Release Notes" chapter of the CDF
User's Guide (which now consists of only one version for all of the
supported machines/operating systems).
CDFSUPPORT
The CDF V2.2 distribution is available via anonymous FTP and NSInet
for VMS systems, via anonymous FTP only for UNIX systems, and via
anonymous FTP and floppy disks for MS-DOS systems.
For VAX/VMS systems via anonymous FTP:
ANONYMOUS account on NSSDCA.GSFC.NASA.GOV (128.183.36.23)
in [.CDF.CDF22-DIST]. The files you need are README.DOC and
CDF22-DIST.BCK. Documentation is in [.CDF.CDF22-DIST.DOC].
It is a PostScript file named CDFUG.PS (CDF User's Guide).
For VAX/VMS systems via NSInet (formerly SPAN):
Copy the files:
NSSDCA::ANON_DIR:[CDF.CDF22-DIST]CDF22-DIST.BCK
NSSDCA::ANON_DIR:[CDF.CDF22-DIST]README.DOC
Documentation is in:
NSSDCA::ANON_DIR:[CDF.CDF22-DIST.DOC]. It is a PostScript
file named CDFUG.PS (CDF User's Guide).
For UNIX systems via anonymous FTP:
"anonymous" account on ncgl.gsfc.nasa.gov (128.183.10.238) in
pub/cdf/cdf22-dist. The files you need are README.doc and
cdf22-dist.tar.Z (use binary mode to transfer the compressed
tar file). Documentation is in pub/cdf/cdf22-dist/doc. It is
a compressed PostScript file named cdfug.ps.Z (CDF User's Guide).
For MS-DOS systems via anonymous FTP:
"anonymous" account on ncgl.gsfc.nasa.gov (128.183.10.238) in
pub/cdf/cdf22-dist/ms-dos. The files you need are README.DOC
and *.EXE (use binary mode to transfer the executables).
For MS-DOS systems via floppy disk:
Send a request to CDFSUPPORT with your mailing address and the
type of floppy disk you are able to read.
The `readme' file explains how to build the distribution and print the
documentation.
We have a user support office (USO) for CDF that you should contact when you
need assistance. For Email requests send to:
Internet -- CDFSUPPORT@xxxxxxxxxxxxxxxxxxxx (128.183.36.23)
NSInet (SPAN) -- NSSDCA::CDFSUPPORT
There is an actual person for this account - her name is Kim Blackwell and
her phone number is (301) 286-9506.
Please let us know (via Email to CDFSUPPORT) if you get the distribution.
We would like to know who has the distribution so we know who to contact
when updates are available.
CDFSUPPORT
>From owner-netcdf-hdf@xxxxxxxxxxxxxxxx 16 2004 Jul -0600 09:49:54
Message-ID: <wrx3c3srly5.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
Date: 16 Jul 2004 09:49:54 -0600
From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
In-Reply-To: <200407160404.i6G44wFE005073@xxxxxxxxxxxxxxxxxxxxxx>
To: netcdf-hdf@xxxxxxxxxxxxxxxx
Subject: Re: Strings (was: Re: HDF5 bitfields...)
Received: (from majordo@localhost)
by unidata.ucar.edu (UCAR/Unidata) id i6GFnuNA005760
for netcdf-hdf-out; Fri, 16 Jul 2004 09:49:56 -0600 (MDT)
Received: from rodney.unidata.ucar.edu (rodney.unidata.ucar.edu
[128.117.140.88])
by unidata.ucar.edu (UCAR/Unidata) with ESMTP id i6GFntaW005756
for <netcdf-hdf@xxxxxxxxxxxxxxxx>; Fri, 16 Jul 2004 09:49:55 -0600 (MDT)
Organization: UCAR/Unidata
Keywords: 200407161549.i6GFntaW005756
References: <200407160404.i6G44wFE005073@xxxxxxxxxxxxxxxxxxxxxx>
Lines: 36
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-netcdf-hdf@xxxxxxxxxxxxxxxx
Precedence: bulk
Reply-To: netcdf-hdf@xxxxxxxxxxxxxxxx
Quincey Koziol <koziol@xxxxxxxxxxxxx> writes:
> Hi Ed,
>
> > > You may also wish to refer to the H5 user's guide,
> > >
> > > http://hdf.ncsa.uiuc.edu/HDF5/doc/UG/
> > >
> > > and there is a tutorial program at:
> > >
> > >
> > > http://hdf.ncsa.uiuc.edu/training/other-ex5/sample-programs/StringOpaque.html
> > >
> >
> > Excellent! Looks to me like we can use the H5T_NATIVE_CHAR type for
> > strings and HDF5 will provide everything we need.
> >
> > One question: you guys can handle n-dimensional arrays of strings -
> > for example a 3 dimensional array of strings? And use the space
> > manipulation functions to define the dimensions, all in the usual HDF5
> > way?
> Yep. You can have any combination of dataspace and datatype that you'd
> like. (a 17 dimensional space of variable-length sequences of arrays of
> strings, etc... :-)
>
> Quincey
Excellent!
Do you allow any conversion to other types? I expect not...
Russ and John, are we going to say that not all types are convertible
in netCDF? At this moment, any type can be converted into any other,
but are we going to try that with string? Doesn't seem to make much
sense...
Ed
>From owner-netcdf-hdf@xxxxxxxxxxxxxxxx 16 2004 Jul -0600 10:02:02
Message-ID: <wrxy8lkq6th.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
Date: 16 Jul 2004 10:02:02 -0600
From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
In-Reply-To: <200407160410.i6G4AIb1005130@xxxxxxxxxxxxxxxxxxxxxx>
To: netcdf-hdf@xxxxxxxxxxxxxxxx
Subject: Re: how does HDF5 really store time? As float, int, string?
Received: (from majordo@localhost)
by unidata.ucar.edu (UCAR/Unidata) id i6GG23A9007028
for netcdf-hdf-out; Fri, 16 Jul 2004 10:02:03 -0600 (MDT)
Received: from rodney.unidata.ucar.edu (rodney.unidata.ucar.edu
[128.117.140.88])
by unidata.ucar.edu (UCAR/Unidata) with ESMTP id i6GG22aW007024
for <netcdf-hdf@xxxxxxxxxxxxxxxx>; Fri, 16 Jul 2004 10:02:02 -0600 (MDT)
Organization: UCAR/Unidata
Keywords: 200407161602.i6GG22aW007024
References: <200407160410.i6G4AIb1005130@xxxxxxxxxxxxxxxxxxxxxx>
Lines: 25
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-netcdf-hdf@xxxxxxxxxxxxxxxx
Precedence: bulk
Reply-To: netcdf-hdf@xxxxxxxxxxxxxxxx
Quincey Koziol <koziol@xxxxxxxxxxxxx> writes:
> Hi Ed,
>
> > HDF5 folk:
> >
> > How do you really store the time type?
> >
> > As a floating point number, number of seconds since Jan 1, 1970, or
> > something like that?
> We do normally store it as the number of seconds since the UNIX epoch
> (Jan 1, 1970). However, we there's a few different time datatypes defined
> and we don't convert between them. Frankly, I think including them is a
> mistake currently, since they are bringing "units & quantities" into a part
> of the library that doesn't really understand how to do unit conversions, etc.
> I would also lean toward not including them in the netCDF4 types, at least
> initially.
>
> Quincey
OK, I will let Russ and Mike reconsider whether they want a time type
for netCDF-4 before we move forward any further with these
requirements...
Ed
netcdf-hdf archives: