remove all-error-codes.md

docs/CMakeLists.txt

@@ -90,7 +90,7 @@ netcdf.m4 DoxygenLayout.xml Doxyfile.in footer.html
 mainpage.dox tutorial.dox guide.dox types.dox
 architecture.dox internal.dox windows-binaries.md
 building-with-cmake.md CMakeLists.txt groups.dox install.md notes.md
-install-fortran.md all-error-codes.md credits.md auth.md
+install-fortran.md credits.md auth.md
 obsolete/fan_utils.html bestpractices.md filters.md indexing.md
 inmemory.md DAP2.dox FAQ.md
 known_problems.md

docs/Doxyfile.in

@@ -747,7 +747,6 @@ INPUT = \
     @abs_top_srcdir@/docs/byterange.dox \
     @abs_top_srcdir@/docs/nczarr.md \
     @abs_top_srcdir@/docs/notes.md \
-    @abs_top_srcdir@/docs/all-error-codes.md \
     @abs_top_srcdir@/docs/building-with-cmake.md \
     @abs_top_srcdir@/docs/FAQ.md \
     @abs_top_srcdir@/docs/known_problems.md \
@@ -762,6 +761,7 @@ INPUT = \
     @abs_top_srcdir@/include/netcdf.h \
     @abs_top_srcdir@/include/netcdf_mem.h \
     @abs_top_srcdir@/include/netcdf_par.h \
+    @abs_top_srcdir@/include/netcdf_filter.h \
     @abs_top_srcdir@/libdispatch/dfile.c \
     @abs_top_srcdir@/libdispatch/ddim.c \
     @abs_top_srcdir@/libdispatch/dvar.c \
@@ -782,6 +782,7 @@ INPUT = \
     @abs_top_srcdir@/libdispatch/derror.c \
     @abs_top_srcdir@/libdispatch/dv2i.c \
     @abs_top_srcdir@/libdispatch/dcopy.c \
+    @abs_top_srcdir@/libdispatch/dfilter.c \
     @abs_top_srcdir@/libsrc4/nc4var.c \
     @abs_top_srcdir@/libhdf5/nc4hdf.c \
     @abs_top_srcdir@/libsrc4/nc4internal.c \
@@ -790,6 +791,7 @@ INPUT = \
     @abs_top_srcdir@/libsrc4/ncfunc.c \
     @abs_top_srcdir@/libsrc4/nc4dim.c \
     @abs_top_srcdir@/libsrc4/nc4attr.c \
+    @abs_top_srcdir@/libsrc4/nc4cache.c \
     @abs_top_srcdir@/libhdf5/nc4info.c \
     @abs_top_srcdir@/libsrc4/nc4dispatch.c \
     @abs_top_srcdir@/libnczarr/zarr.c \
@@ -2037,7 +2039,7 @@ SKIP_FUNCTION_MACROS   = YES
 
 # TAGFILES               = html/guide.tag=./html_guide "html/tutorial.tag = ./html_tutorial"
 #TAGFILES = ../../NUG/html/nug.tag=../../../NUG/html
-TAGFILES = ../../NUG/html/nug.tag=https://docs.unidata.ucar.edu/nug
+#TAGFILES = ../../NUG/html/nug.tag=https://docs.unidata.ucar.edu/nug
 
 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
 # tag file that is based on the input files it reads. See section "Linking to

docs/FAQ.md

@@ -67,7 +67,7 @@ that is part of the netCDF software distribution. It is a command line
 tool that provides a text representation of a netCDF file's data, just its
 metadata, or just the data for specified
 variables, depending on what arguments you use. For more information,
-see the \ref ncdump_guide documentation.
+see the [ncdump User's Guide](https://docs.unidata.ucar.edu/nug/current/netcdf_utilities_guide.html#ncdump_guide) documentation.
 
 Another good tool for conversion of netCDF data to text is the ["ncks" program](http://nco.sourceforge.net/nco.html#ncks-netCDF-Kitchen-Sink) that's one of the utility programs in the [NCO (NetCDF Operators)](software.html#NCO) package. Similar capabilities are available using programs from the [CDO (Climate Data Operators)](software.html#CDO) software, commands from [NCL (NCAR Command Language)](software.html#NCL), or various other packages such as [ANAX](http://science.arm.gov/~cflynn/ARM_Tested_Tools/), cdf2asc, and NOESYS, all "third party" netCDF utilities developed and supported by other organizations. You can find more information about these third-party packages on the [Software for Manipulating or Displaying NetCDF Data](software.html) page.
 
@@ -322,7 +322,7 @@ We test releases on the following operating systems with various compilers:
 -   Solaris
 -   Windows (some versions, see below)
 
-The [NetCDF Installation and Porting Guide](@ref getting_and_building_netcdf) explains how to build netCDF from source on various platforms. Often, it's as easy as running
+The [NetCDF Installation and Porting Guide](https://docs.unidata.ucar.edu/nug/current/getting_and_building_netcdf.html) explains how to build netCDF from source on various platforms. Often, it's as easy as running
 
 ~~~~ {.boldcode}
   ./configure
@@ -483,7 +483,7 @@ How do I build and install netCDF for a specific development environment? {#How-
 You have to build and install the netCDF C library first, before you build and install other language libraries that depend on it, such as Fortran, C++, or Python netCDF libraries. The netCDF Java library is mostly independent of the netCDF C library, unless you need to write netCDF-4 files from Java, in which case you will also need an installed netCDF C library.
 
 For more details, see
-[NetCDF Installation and Porting Guide](@ref getting_and_building_netcdf).
+[NetCDF Installation and Porting Guide](https://docs.unidata.ucar.edu/nug/current/getting_and_building_netcdf.html).
 
 
 ----------

docs/Makefile.am

@@ -8,16 +8,12 @@
 
 # These files will be included with the dist.
 EXTRA_DIST = netcdf.m4 DoxygenLayout.xml Doxyfile.in footer.html	\
-mainpage.dox tutorial.dox			\
-architecture.dox internal.md windows-binaries.md dispatch.md \
-building-with-cmake.md CMakeLists.txt groups.dox notes.md	\
-install-fortran.md all-error-codes.md credits.md auth.md filters.md \
-obsolete/fan_utils.html indexing.dox	\
-inmemory.md FAQ.md	                \
-known_problems.md COPYRIGHT.md		\
-inmeminternal.dox              \
-testserver.dox byterange.dox   \
-nczarr.md
+mainpage.dox tutorial.dox architecture.dox internal.dox			\
+windows-binaries.md dispatch.md building-with-cmake.md CMakeLists.txt groups.dox	\
+notes.md install-fortran.md credits.md auth.md filters.md		\
+obsolete/fan_utils.html indexing.dox inmemory.md FAQ.md			\
+known_problems.md COPYRIGHT.md inmeminternal.dox testserver.dox		\
+byterange.dox nczarr.md
 
 # Turn off parallel builds in this directory.
 .NOTPARALLEL:

docs/nczarr.md

@@ -190,7 +190,7 @@ be a prefix of any other key.
 There several other concepts of note.
 1. __Dataset__ - a dataset is the complete tree contained by the key defining
 the root of the dataset.
-Technically, the root of the tree is the key <dataset>/.zgroup, where .zgroup can be considered the _superblock_ of the dataset.
+Technically, the root of the tree is the key \<dataset\>/.zgroup, where .zgroup can be considered the _superblock_ of the dataset.
 2. __Object__ - equivalent of the S3 object; Each object has a unique key
 and "contains" data in the form of an arbitrary sequence of 8-bit bytes.
 

docs/notes.md

@@ -107,3 +107,44 @@ that is returned by nc_open() and nc_create().)
 For netCDF-4/HDF5 files, netCDF IDs can come not just from nc_open()
 and nc_create(), but also from nc_def_grp(), nc_inq_grps(),
 nc_inq_ncid(), nc_inq_grp_parent(), and nc_inq_grp_full_ncid().
+
+# NetCDF Names {#object_name}
+
+## Permitted Characters in NetCDF Names
+
+The names of dimensions, variables and attributes (and, in netCDF-4
+files, groups, user-defined types, compound member names, and
+enumeration symbols) consist of arbitrary sequences of alphanumeric
+characters, underscore '_', period '.', plus '+', hyphen '-', or at
+sign '@', but beginning with an alphanumeric character or
+underscore. However names commencing with underscore are reserved for
+system use.
+
+Beginning with versions 3.6.3 and 4.0, names may also include UTF-8
+encoded Unicode characters as well as other special characters, except
+for the character '/', which may not appear in a name.
+
+Names that have trailing space characters are also not permitted.
+
+Case is significant in netCDF names.
+
+## Name Length
+
+A zero-length name is not allowed.
+
+Names longer than ::NC_MAX_NAME will not be accepted any netCDF define
+function. An error of ::NC_EMAXNAME will be returned.
+
+All netCDF inquiry functions will return names of maximum size
+::NC_MAX_NAME for netCDF files. Since this does not include the
+terminating NULL, space should be reserved for ::NC_MAX_NAME + 1
+characters.
+
+## NetCDF Conventions
+
+Some widely used conventions restrict names to only alphanumeric
+characters or underscores.
+
+Note that, when using the DAP2 protocol to access netCDF data, there
+are reserved keywords, the use of which may result in undefined
+behavior. See DAP2 Reserved Keywords for more information.