793ecc8e60
re: https://github.com/Unidata/netcdf-c/issues/1876 and: https://github.com/Unidata/netcdf-c/pull/1835 and: https://github.com/Unidata/netcdf4-python/issues/1041 The change in PR 1835 was correct with respect to using %20 instead of '+' for encoding blanks. However, it was a mistake to assume everything was unencoded and then to do encoding ourselves. The problem is that different servers do different things, with Columbia being an outlier. So, I have added a set of client controls that can at least give the caller some control over this. The caller can append the following fragment to his URL to control what gets encoded before sending it to the server. The syntax is as follows: ```` https://<host>/<path>/<query>#encode=path|query|all|none ```` The possible values: * path -- URL encode (i.e. %xx encode) as needed in the path part of the URL. * query -- URL encode as needed in the query part of the URL. * all -- equivalent to ````#encode=path,query````. * none -- do not url encode any part of the URL sent to the server; not strictly necessary, so mostly for completeness. Note that if "encode=" is used, then before it is processed, all encoding is turned of so that ````#encode=path```` will only encode the path and not the query. The default is ````#encode=query````, so the path is left untouched, but the query is always encoded. Internally, this required changes to pass the encode flags down into the OC2 library. Misc. Unrelated Changes: * Shut up those irritating warning from putget.m4 |
||
|---|---|---|
| .github | ||
| cmake | ||
| conda.recipe | ||
| ctest_scripts | ||
| dap4_test | ||
| debug | ||
| docs | ||
| examples | ||
| h5_test | ||
| hdf4_test | ||
| include | ||
| libdap2 | ||
| libdap4 | ||
| libdispatch | ||
| libhdf4 | ||
| libhdf5 | ||
| liblib | ||
| libnczarr | ||
| libsrc | ||
| libsrc4 | ||
| libsrcp | ||
| nc_perf | ||
| nc_test | ||
| nc_test4 | ||
| ncdap_test | ||
| ncdump | ||
| ncgen | ||
| ncgen3 | ||
| nctest | ||
| nczarr_test | ||
| NUG | ||
| oc2 | ||
| plugins | ||
| unit_test | ||
| .gitignore | ||
| .travis.yml | ||
| acinclude.m4 | ||
| appveyor.yml | ||
| bootstrap | ||
| 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 | ||
| 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.