0f4b72c53b
using cygwin64 causes a couple of bugs during make check. Fixes are as follows: 1. in ncdump.c and nccopy.c change all occurrences of 'return EXIT_FAILURE' and 'return EXIT_SUCCESS' with exit(EXIT_FAILURE) and exit(EXIT_SUCCESS) respectively. I have no idea why this works. 2. in libdap2/ncdap3a.c#freeNCDAPCOMMON, remove the call to nc_abort, it is causing a loop; not sure why this is not caught under other operating systems. |
||
|---|---|---|
| cmake | ||
| examples | ||
| h5_test | ||
| include | ||
| libdap2 | ||
| libdispatch | ||
| liblib | ||
| libsrc | ||
| libsrc4 | ||
| libsrc5 | ||
| m4 | ||
| man4 | ||
| nc_test | ||
| nc_test4 | ||
| ncdap_test | ||
| ncdump | ||
| ncgen | ||
| ncgen3 | ||
| nctest | ||
| oc2 | ||
| .gitignore | ||
| acinclude.m4 | ||
| cf | ||
| cmake_uninstall.cmake.in | ||
| CMakeLists.txt | ||
| COMPILE.cmake.txt | ||
| config.h.in.cmake | ||
| configure.ac | ||
| COPYRIGHT | ||
| CTestConfig.cmake | ||
| CTestCustom.cmake | ||
| dods.m4 | ||
| Doxyfile | ||
| FixBundle.cmake.in | ||
| INSTALL | ||
| INSTALL.cmake | ||
| lib_flags.am | ||
| libncdap.tar.gz | ||
| Make0 | ||
| Makefile.am | ||
| mclean | ||
| nc-config.in | ||
| nc-config.in.cmake | ||
| ncdap.m4 | ||
| netcdf-config-version.cmake.in | ||
| netcdf-config.cmake.in | ||
| netcdf.pc.in | ||
| README | ||
| README.md | ||
| RELEASE_NOTES.md | ||
| test_prog.c | ||
| test_prog.f90 | ||
| test_prog.F | ||
Unidata NetCDF
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, and C++ interfaces. They have been tested on various common platforms.
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.
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
For more information about netCDF, see the netCDF Web page at
You can obtain a copy of the latest released version of netCDF software from
Copyright and licensing information can be found here, as well as in the COPYRIGHT file accompanying the software
To install this package, please see the file INSTALL in the distribution, or the (possibly more up-to-date) document:
The netCDF-3 C and FORTRAN-77 interfaces are documented in man(1) pages at
- http://www.unidata.ucar.edu/netcdf/docs/netcdf-man-3.html
- http://www.unidata.ucar.edu/netcdf/docs/netcdf-man-3f.html
User's Guides are also available in several forms from the same location.
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
We appreciate feedback from users of this package. Please send comments, suggestions, and bug reports to support-netcdf@unidata.ucar.edu. Please identify the version of the package (file VERSION).