1a7531392f
Primary fixes to get -ansi to work. 1. Convert all '//' C++ style comments to /*...*/ or to use #if 0...#endif 2. It turns out that when -ansi is specified, then a number of functions no longer are defined in the header -- but they are still in the .so file.<br> The big example is strdup(). So, added code to include/ncconfig.h to define externs for those missing functions that occur in more than one place. These are enabled if !_WIN32 && __STDC__ == 1 (__STDC__ is supposed to be the equivalent compile time flag to -ansi). Note that this requires config.h (which references ncconfig.h) to be included in files where it is currently not included. Single uses will be only in the file that uses them. 3. Added mmap test for the MAP_ANONYMOUS flag to configure.ac. Apparently this is not always defined with -ansi. 4. fix some large integer constants in nc_test4/tst_atts3.c and nc_test4/tst_filterparser.c to avoid compiler complaints. 5. fix a double constant in nc_test4/tst_filterparser.c to avoid compiler complaints. [Note I suspect #4 and #5 will be a problem on big-endian machines, but we have no way to test] Misc. Changes: 1. convert more instances of _MSC_VER to _WIN32. 2. added some debugging code to include/nctestserver.h 3. added comment about libdispatch/drc.c always being compiled. 4. modify parser generation in ncgen to remove unneeded files. |
||
|---|---|---|
| .github | ||
| cmake | ||
| conda.recipe | ||
| dap4_test | ||
| debug | ||
| docs | ||
| examples | ||
| h5_test | ||
| hdf4_test | ||
| include | ||
| libdap2 | ||
| libdap4 | ||
| libdispatch | ||
| libhdf4 | ||
| libhdf5 | ||
| liblib | ||
| libsrc | ||
| libsrc4 | ||
| libsrcp | ||
| nc_test | ||
| nc_test4 | ||
| ncdap_test | ||
| ncdump | ||
| ncgen | ||
| ncgen3 | ||
| nctest | ||
| oc2 | ||
| plugins | ||
| .gitignore | ||
| .travis.yml | ||
| acinclude.m4 | ||
| appveyor.yml | ||
| cmake_uninstall.cmake.in | ||
| CMakeInstallation.cmake | ||
| CMakeLists.txt | ||
| CODE_OF_CONDUCT.md | ||
| 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 | ||
| 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-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.