2133052c6e
The new plugin path API uses char** to represent a variable lenght vector of variable length strings. FORTRAN is not capable of accessing such structures. So, this PR extends the API to provide a counted string-based API to the plugin path functionality. The new functions are inserted in the netcdf_aux.h/daux.c files. The new functions are just wrappers around other plugin path API function; they are just (I hope) more convenient for FORTRAN users. The new functions are as follows: ### *ncaux_plugin_path_stringlen(void)* * Return the length (as in strlen) of the current plugin path directories encoded as a string. Return -1 if the request fails. ### *int ncaux_plugin_path_stringget(int pathlen, char* path)* * Get the current sequence of directories in the internal global plugin path list encoded as a string path using ';' as a path separator. As an example, it might return "/a/b/c;/home/user/me;/tmp". The arguments are as follows: * *pathlen* -- the length of the path argument. * *path* -- a string into which the current plugin path as a string is stored. * Return NC_NOERR | NC_EINVAL ### *int ncaux_plugin_path_stringset(int pathlen, const char* path)* * Set the current sequence of directories in the internal global plugin path list. As an example, it might take "/a/b/c;/home/user/me;/tmp". The arguments are as follows: * *pathlen* -- the length of the path argument. * *path* -- a string that is parsed to obtain the sequence of directories for the current plugin path. * Return NC_NOERR | NC_EINVAL |
||
---|---|---|
.github | ||
cmake | ||
conda.recipe | ||
ctest_scripts | ||
dap4_test | ||
docs | ||
examples | ||
fuzz | ||
h5_test | ||
hdf4_test | ||
include | ||
libdap2 | ||
libdap4 | ||
libdispatch | ||
libhdf4 | ||
libhdf5 | ||
liblib | ||
libncpoco | ||
libncxml | ||
libnczarr | ||
libsrc | ||
libsrc4 | ||
libsrcp | ||
nc_perf | ||
nc_test | ||
nc_test4 | ||
ncdap_test | ||
ncdump | ||
ncgen | ||
ncgen3 | ||
nctest | ||
nczarr_test | ||
NUG | ||
oc2 | ||
plugins | ||
unit_test | ||
.clang-tidy | ||
.gitignore | ||
acinclude.m4 | ||
bootstrap | ||
CITATION.cff | ||
cmake_uninstall.cmake.in | ||
CMakeInstallation.cmake | ||
CMakeLists.txt | ||
COMPILE.cmake.txt | ||
config.h.cmake.in | ||
config.h.cmake.in.old-works | ||
configure.ac | ||
COPYRIGHT | ||
CTestConfig.cmake.in | ||
CTestCustom.cmake.in | ||
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 | ||
README.md | ||
RELEASE_NOTES.md | ||
s3cleanup.in | ||
s3gc.in | ||
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:
- Building NetCDF with CMake
- Building NetCDF with Autoconf/Automake/Libtool
- Building or Getting Binaries for NetCDF on Windows
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.