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

netcdf-2.4b5-1 (new package)

Date: 10 Jan 96 14:24 UT
Source: netcdf
Binary: netcdf 
Version: 2.4b5-1
 netcdf: An interface for scientific data access.
Priority: Routine
Changes: New package.  a.out format.
 -rw-------   1 krs      users      756323 Jan 10 08:24 netcdf-2.4b5-1.tar.gz
 -rw-------   1 krs      users       28175 Jan 10 08:24 netcdf-2.4b5-1.diff.gz
 -rw-r--r--   1 krs      users      483952 Jan 10 08:23 netcdf-2.4b5-1.deb
 a90e01780d7ca2eb2d7a8467946a6a47  netcdf-2.4b5-1.tar.gz
 ef5a9f365222cb892b94ffb20c2b4ff3  netcdf-2.4b5-1.diff.gz
 5be84385d2dc65098d9d5e7f8540d347  netcdf-2.4b5-1.deb

 NetCDF (network Common Data Form) is an interface for scientific
 data access and a freely-distributed software library that provides an
 implementation of the interface. It was developed by Glenn Davis,
 Russ Rew, and Steve Emmerson at the Unidata Program Center in
 Boulder, Colorado. The netCDF library also defines a
 machine-independent format for representing scientific data.
 Together, the interface, library, and format support the creation,
 access, and sharing of scientific data.
 netCDF data is:
 * Self-Describing: A netCDF file includes information about
   the data it contains.
 * Network-transparent. A netCDF file is represented in a form
   that can be accessed by computers with different ways of
   storing integers, characters, and floating-point numbers.
 * Direct-access. A small subset of a large dataset may be
   accessed efficiently, without first reading through all the
   preceding data.
 * Appendable. Data can be appended to a netCDF dataset along
   one dimension without copying the dataset or redefining its
   structure. The structure of a netCDF dataset can be changed,
   though this sometimes causes the dataset to be copied.
 * Sharable. One writer and multiple readers may
   simultaneously access the same netCDF file.
Karl R. Sackett                                        krs@caos.aamu.edu
Run silent, run deep

Reply to: