9983b9d911
re pull request https://github.com/Unidata/netcdf-c/pull/405 re pull request https://github.com/Unidata/netcdf-c/pull/446 Notes: 1. This branch is a cleanup of the magic.dmh branch. 2. magic.dmh was originally merged, but caused problems with parallel IO. It was re-issued as pull request https://github.com/Unidata/netcdf-c/pull/446. 3. This branch + pull request replace any previous pull requests and magic.dmh branch. Given an otherwise valid netCDF file that has a corrupted header, the netcdf library currently crashes. Instead, it should return NC_ENOTNC. Additionally, the NC_check_file_type code does not do the forward search required by hdf5 files. It currently only looks at file position 0 instead of 512, 1024, 2048,... Also, it turns out that the HDF4 magic number is assumed to always be at the beginning of the file (unlike HDF5). The change is localized to libdispatch/dfile.c See https://support.hdfgroup.org/release4/doc/DSpec_html/DS.pdf Also, it turns out that the code in NC_check_file_type is duplicated (mostly) in the function libsrc4/nc4file.c#nc_check_for_hdf. This branch does the following. 1. Make NC_check_file_type return NC_ENOTNC instead of crashing. 2. Remove nc_check_for_hdf and centralize all file format checking NC_check_file_type. 3. Add proper forward search for HDF5 files (but not HDF4 files) to look for the magic number at offsets of 0, 512, 1024... 4. Add test tst_hdf5_offset.sh. This tests that hdf5 files with an offset are properly recognized. It does so by prefixing a legal file with some number of zero bytes: 512, 1024, etc. 5. Off-topic: Added -N flag to ncdump to force a specific output dataset name. |
||
---|---|---|
.github | ||
cmake | ||
dap4_test | ||
docs | ||
examples | ||
h5_test | ||
include | ||
libdap2 | ||
libdap4 | ||
libdispatch | ||
liblib | ||
libsrc | ||
libsrc4 | ||
libsrcp | ||
nc_test | ||
nc_test4 | ||
ncdap_test | ||
ncdump | ||
ncgen | ||
ncgen3 | ||
nctest | ||
oc2 | ||
.gitignore | ||
.travis.yml | ||
acinclude.m4 | ||
cf | ||
cf.cmake | ||
cmake_uninstall.cmake.in | ||
CMakeInstallation.cmake | ||
CMakeLists.txt | ||
COMPILE.cmake.txt | ||
config.h.cmake.in | ||
config.h.cmake.in.old-works | ||
configure.ac | ||
CONTRIBUTING.md | ||
COPYRIGHT | ||
CTestConfig.cmake.in | ||
CTestCustom.cmake | ||
dods.m4 | ||
FixBundle.cmake.in | ||
INSTALL.md | ||
lib_flags.am | ||
libnetcdf.settings.in | ||
Make0 | ||
Makefile.am | ||
mclean | ||
nc-config.cmake.in | ||
nc-config.in | ||
netcdf.pc.in | ||
netCDFConfig.cmake.in | ||
PostInstall.cmake | ||
postinstall.sh.in | ||
README.md | ||
RELEASE_NOTES.md | ||
test_common.in | ||
test_prog.c | ||
test_prog.f90 | ||
test_prog.F | ||
test-driver-verbose | ||
wjna |
Unidata NetCDF
About
The Unidata network Common Data Form (netCDF) is an interface for scientific data access and a freely-distributed software library that provides an implementation of the interface. 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. The current netCDF software provides C interfaces for applications and data. Separate software distributions available from Unidata provide Java, Fortran, Python, and C++ interfaces. They have been tested on various common platforms.
Properties
NetCDF files are self-describing, network-transparent, directly
accessible, and extendible. Self-describing
means that a netCDF file
includes information about the data it contains. Network-transparent
means that 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
means that a small subset of a
large dataset may be accessed efficiently, without first reading through
all the preceding data. Extendible
means that data can be appended to
a netCDF dataset without copying it or redefining its structure.
Use
NetCDF is useful for supporting access to diverse kinds of scientific data in heterogeneous networking environments and for writing application software that does not depend on application-specific formats. For information about a variety of analysis and display packages that have been developed to analyze and display data in netCDF form, see
More information
For more information about netCDF, see
Latest releases
You can obtain a copy of the latest released version of netCDF software for various languages:
Copyright
Copyright and licensing information can be found here, as well as in the COPYRIGHT file accompanying the software
Installation
To install the netCDF-C software, please see the file INSTALL in the netCDF-C distribution, or the (usually more up-to-date) document:
Documentation
A language-independent User's Guide for netCDF, and some other language-specific user-level documents are available from:
- Language-independent User's Guide
- NetCDF-C Tutorial
- Fortran-90 User's Guide
- Fortran-77 User's Guide
- netCDF-Java/Common Data Model library
- netCDF4-python
A mailing list, netcdfgroup@unidata.ucar.edu, exists for discussion of the netCDF interface and announcements about netCDF bugs, fixes, and enhancements. For information about how to subscribe, see the URL
Feedback
We appreciate feedback from users of this package. Please send comments, suggestions, and bug reports to support-netcdf@unidata.ucar.edu.