Auto-generated from 2b3c5a1

cf-conventions.html

@@ -779,11 +779,11 @@ <h1>NetCDF Climate and Forecast (CF) Metadata Conventions</h1>
 3.3. <a href="#table-flag-variable-bit-2-and-3">Flag Variable Bit 2 and Bit 3 (from Example)</a><br>
 A.1. <a href="#table-attributes">Attributes</a><br>
 C.1. <a href="#table-standard-name-modifiers">Standard Name Modifiers</a><br>
-D.1. <a href="#table-computed-standard-names">Table D.1.  Consistent sets of values for the standard_names of formula terms and the computed_standard_name needed in defining the ocean sigma coordinate, the ocean s-coordinate,  the ocean_sigma over z coordinate, and the ocean double sigma coordinate.</a><br>
+D.1. <a href="#table-computed-standard-names">Consistent sets of values for the standard_names of formula terms and the computed_standard_name needed in defining the ocean sigma coordinate, the ocean s-coordinate,  the ocean_sigma over z coordinate, and the ocean double sigma coordinate.</a><br>
 E.1. <a href="#table-cell-methods">Cell Methods</a><br>
 F.1. <a href="#table-grid-mapping-attributes">Grid Mapping Attributes</a><br>
-I.1. <a href="#table-cf-concepts">Table I.1. The elements of the CF-netCDF conventions. The relationships to netCDF elements are shown in [figure-cf-concepts].</a><br>
-I.2. <a href="#table-cf-constructs">Table I.2. The constructs of the CF data model. The relationships between the constructs and CF-netCDF elements are shown in in [figure-field], [figure-dim-aux] and [figure-coordinate-reference].</a></p>
+I.1. <a href="#table-cf-concepts">The elements of the CF-netCDF conventions. The relationships to netCDF elements are shown in [figure-cf-concepts].</a><br>
+I.2. <a href="#table-cf-constructs">The constructs of the CF data model. The relationships between the constructs and CF-netCDF elements are shown in in [figure-field], [figure-dim-aux] and [figure-coordinate-reference].</a></p>
 </div>
 <div class="paragraph">
 <p><strong>List of Examples</strong></p>
@@ -806,13 +806,13 @@ <h1>NetCDF Climate and Forecast (CF) Metadata Conventions</h1>
 5.2. <a href="#two-dimensional-coordinate-variables-ex">Two-dimensional coordinate variables</a><br>
 5.3. <a href="#reduced-horizontal-grid-ex">Reduced horizontal grid</a><br>
 5.6. <a href="#rotated-pole-grid-ex">Rotated pole grid</a><br>
-5.7. <a href="#lambert-conformal-projection">Example 5.7, "Lambert conformal projection"</a><br>
+5.7. <a href="#lambert-conformal-projection">"Lambert conformal projection"</a><br>
 5.8. <a href="#latitude-and-longitude-on-a-spherical-earth">Latitude and longitude on a spherical Earth</a><br>
 5.9. <a href="#latitude-and-longitude-on-the-wgs-1984-datum">Latitude and longitude on the WGS 1984 datum</a><br>
 5.10. <a href="#british-national-grid">British National Grid</a><br>
 5.11. <a href="#latitude-and-longitude-on-the-wgs-1984-datum-in-crs-wkt-format">Latitude and longitude on the WGS 1984 datum + CRS WKT</a><br>
 5.12. <a href="#british-national-grid-newlyn-datum-in-crs-wkt-format">British National Grid + Newlyn Datum in CRS WKT format</a><br>
-5.13. <a href="#multiple-forecasts-from-single-analysis">Example 5.13, "Multiple forecasts from a single analysis"</a><br>
+5.13. <a href="#multiple-forecasts-from-single-analysis">"Multiple forecasts from a single analysis"</a><br>
 6.1. <a href="#northward-heat-transport-in-atlantic-ocean-ex">Northward heat transport in Atlantic Ocean</a><br>
 6.1.2. <a href="#taxa-ex">Taxon names and identifiers</a><br>
 6.2. <a href="#model-level-numbers-ex">Model level numbers</a><br>
@@ -838,15 +838,16 @@ <h1>NetCDF Climate and Forecast (CF) Metadata Conventions</h1>
 8.4. <a href="#example-1d-interpolation-of-2d-domain">One-dimensional tie point interpolation of two-dimensional domain.</a><br>
 8.5. <a href="#example-VIIRS">Multiple interpolation variables with interpolation parameter attributes.</a><br>
 8.6. <a href="#example-grid-mapping-and-interpolation-with-time-not-interpolated">Combining a grid mapping and coordinate interpolation, with time as a non-interpolated dimension.</a><br>
+8.7. <a href="#example-interpolation-of-cell-boundaries">Interpolation of 2D Cell Boundaries corresponding to [figure_interpolation_of_cell_boundaries]</a><br>
 B.1. <a href="#name-table-three-entries-ex">A name table containing three entries</a><br>
-H.1. <a href="#example-h.1">Example H.1, "Point data"</a><br>
+H.1. <a href="#example-h.1">"Point data"</a><br>
 H.2. <a href="#example-h.2">Timeseries with common element times in a time coordinate variable using the orthogonal multidimensional array representation.</a><br>
 H.3. <a href="#example-h.3">Timeseries of station data in the incomplete multidimensional array representation.    </a><br>
 H.4. <a href="#example-h.4">A single timeseries.</a><br>
 H.5. <a href="#example-h.5">A single timeseries with time-varying deviations from a nominal point spatial location</a><br>
 H.6. <a href="#example-h.6">Timeseries of station data in the contiguous ragged array representation.</a><br>
 H.7. <a href="#example-h.7">Timeseries of station data in the indexed ragged array representation.</a><br>
-H.8. <a href="#example-h.8">Example H.8, "Atmospheric sounding profiles for a common set of vertical coordinates stored in the orthogonal multidimensional array representation."</a><br>
+H.8. <a href="#example-h.8">"Atmospheric sounding profiles for a common set of vertical coordinates stored in the orthogonal multidimensional array representation."</a><br>
 H.9. <a href="#example-h.9">Data from a single atmospheric sounding profile.</a><br>
 H.10. <a href="#example-h.10">Atmospheric sounding profiles for a common set of vertical coordinates stored in the contiguous ragged array representation.</a><br>
 H.11. <a href="#example-h.11">Atmospheric sounding profiles for a common set of vertical coordinates stored in the indexed ragged array representation.</a><br>
@@ -861,7 +862,7 @@ <h1>NetCDF Climate and Forecast (CF) Metadata Conventions</h1>
 H.20. <a href="#example-h.20">Time series of atmospheric sounding profiles along a set of trajectories stored in a multidimensional array representation.</a><br>
 H.21. <a href="#example-h.21">Time series of atmospheric sounding profiles along a trajectory stored in a multidimensional array representation.</a><br>
 H.22. <a href="#example-h.22">Time series of atmospheric sounding profiles along a set of trajectories stored in a ragged array representation.</a><br>
-I.1. <a href="#cdl-domain-anc-coordinate">Example I.1 A single CF-netCDF variable corresponding to two data model constructs.</a></p>
+I.1. <a href="#cdl-domain-anc-coordinate">A single CF-netCDF variable corresponding to two data model constructs.</a></p>
 </div>
 </div>
 </div>
@@ -5551,7 +5552,7 @@ <h4 id="compression-by-coordinate-subsampling-interpolation-of-cell-boundaries">
 <p><strong>Bounds Tie Point Attribute and Bounds Tie Point Variable</strong><br>
 A <strong><code>bounds_tie_points</code></strong> attribute must be defined for each tie point coordinate variable corresponding to reconstituted coordinates with cell boundaries.
 It is a single word of the form <em>“bounds_tie_point_variable”</em> that identifies a bounds tie point variable, containing a bounds tie point coordinate value for each tie point stored in its tie point coordinate variable, and therefore the bounds tie point variable has the same set of dimensions as its tie point coordinate variable.
-An example of the usage of the <strong><code>bounds_tie_points</code></strong> is shown in <a href="#example_interpolation_of_cell_boundaries">Example 8.7</a>.
+An example of the usage of the <strong><code>bounds_tie_points</code></strong> is shown in <a href="#example_interpolation_of_cell_boundaries">[example_interpolation_of_cell_boundaries]</a>.
 Since a bounds tie point variable is considered to be part of a tie point coordinate variable’s metadata, it is not necessary to provide it with attributes such as long_name and units, following the same rules as for the bounds of an uncompressed coordinate variable, see <a href="#cell-boundaries">Section 7.1, "Cell Boundaries"</a>.</p>
 </div>
 <div class="paragraph">
@@ -5569,8 +5570,8 @@ <h4 id="compression-by-coordinate-subsampling-interpolation-of-cell-boundaries">
 <p><strong>Uncompression of two-dimensional coordinate bounds</strong><br>
 For two-dimensional coordinate bounds, in the second step of the process, for each index pair <code>(j, i)</code> of the interpolated dimension, the four bounds of the boundary variable is set to the value of the interpolated bounds point grid at index pairs <code>B0</code>, <code>B1</code>, <code>B2</code> and <code>B3</code>, respectively, where the index pairs are defined above under <a href="#compressing_two_dimensional">"Compressing two-dimensional coordinate bounds"</a>.</p>
 </div>
-<div id="example_interpolation_of_cell_boundaries" class="exampleblock">
-<div class="title">Example 8.7 Interpolation of 2D Cell Boundaries corresponding to <a href="#figure_interpolation_of_cell_boundaries">Figure 8.4</a></div>
+<div id="example-interpolation-of-cell-boundaries" class="exampleblock">
+<div class="title">Example 8.7. Interpolation of 2D Cell Boundaries corresponding to <a href="#figure_interpolation_of_cell_boundaries">[figure_interpolation_of_cell_boundaries]</a></div>
 <div class="content">
 <div class="listingblock">
 <div class="content">
@@ -7371,7 +7372,7 @@ <h3 id="_ocean_double_sigma_coordinate"><a class="anchor" href="#_ocean_double_s
 <div class="content">
 <img src="NFFFFFF-1.0.png" alt="NFFFFFF 1.0">
 </div>
-<div class="title">Table D.1.  Consistent sets of values for the standard_names of formula terms and the computed_standard_name needed in defining the ocean sigma coordinate, the ocean s-coordinate,  the ocean_sigma over z coordinate, and the ocean double sigma coordinate.</div>
+<div class="title">Consistent sets of values for the standard_names of formula terms and the computed_standard_name needed in defining the ocean sigma coordinate, the ocean s-coordinate,  the ocean_sigma over z coordinate, and the ocean double sigma coordinate.</div>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
@@ -9169,7 +9170,7 @@ <h4 id="_orthogonal_multidimensional_array_representation_of_profiles"><a class=
 <div class="sect3">
 <h4 id="_incomplete_multidimensional_array_representation_of_profiles"><a class="anchor" href="#_incomplete_multidimensional_array_representation_of_profiles"></a>H.3.2. Incomplete multidimensional array representation of profiles</h4>
 <div class="paragraph">
-<p>If there are the same number of levels in each profile, but they do not have the same set of vertical coordinates, one can use the incomplete multidimensional array representation, which the vertical coordinate variable is two-dimensional e.g. replacing z(z) in <a href="#example-h.8">Example H.8, "Atmospheric sounding profiles for a common set of vertical coordinates stored in the orthogonal multidimensional array representation."</a> with alt(profile,z).
+<p>If there are the same number of levels in each profile, but they do not have the same set of vertical coordinates, one can use the incomplete multidimensional array representation, which the vertical coordinate variable is two-dimensional e.g. replacing z(z) in <a href="#example-h.8">"Atmospheric sounding profiles for a common set of vertical coordinates stored in the orthogonal multidimensional array representation."</a> with alt(profile,z).
 This representation also allows one to have a variable number of elements in different profiles, at the cost of some wasted space.
 In that case, any unused elements of the data and auxiliary coordinate variables must contain missing data values (section 9.6).</p>
 </div>
@@ -10312,7 +10313,7 @@ <h3 id="data-model-elements-of-cf-netcdf"><a class="anchor" href="#data-model-el
 The CF data model has been derived from these CF-netCDF elements and relationships with the aims of removing aspects specific to the netCDF encoding, and reducing the number of elements, whilst retaining the ability to describe the CF conventions fully, in order to meet the design criteria.</p>
 </div>
 <table id="table-cf-concepts" class="tableblock frame-all grid-all stretch">
-<caption class="title">Table I.1. The elements of the CF-netCDF conventions. The relationships to netCDF elements are shown in <a href="#figure-cf-concepts">[figure-cf-concepts]</a>.</caption>
+<caption class="title">The elements of the CF-netCDF conventions. The relationships to netCDF elements are shown in <a href="#figure-cf-concepts">[figure-cf-concepts]</a>.</caption>
 <colgroup>
 <col style="width: 50%;">
 <col style="width: 50%;">
@@ -10392,7 +10393,7 @@ <h3 id="data-model-the-cf-data-model"><a class="anchor" href="#data-model-the-cf
 The constructs, listed in <a href="#table-cf-constructs">Table I.2</a>, are related to CF-netCDF elements (<a href="#figure-cf-concepts">Figure I.1</a>), which in turn relate to the components of netCDF file.</p>
 </div>
 <table id="table-cf-constructs" class="tableblock frame-all grid-all stretch">
-<caption class="title">Table I.2. The constructs of the CF data model. The relationships between the constructs and CF-netCDF elements are shown in in <a href="#figure-field">[figure-field]</a>, <a href="#figure-dim-aux">[figure-dim-aux]</a> and <a href="#figure-coordinate-reference">[figure-coordinate-reference]</a>.</caption>
+<caption class="title">The constructs of the CF data model. The relationships between the constructs and CF-netCDF elements are shown in in <a href="#figure-field">[figure-field]</a>, <a href="#figure-dim-aux">[figure-dim-aux]</a> and <a href="#figure-coordinate-reference">[figure-coordinate-reference]</a>.</caption>
 <colgroup>
 <col style="width: 50%;">
 <col style="width: 50%;">
@@ -10676,7 +10677,7 @@ <h4 id="data-model-domain-ancillary"><a class="anchor" href="#data-model-domain-
 In the case of a named term being a type of coordinate variable, that variable will correspond to an independent domain ancillary construct in addition to the coordinate construct; that is, a single CF-netCDF variable is translated into two constructs (see <a href="#cdl-domain-anc-coordinate">Example I.1</a>).</p>
 </div>
 <div id="cdl-domain-anc-coordinate" class="exampleblock">
-<div class="title">Example I.1 A single CF-netCDF variable corresponding to two data model constructs.</div>
+<div class="title">A single CF-netCDF variable corresponding to two data model constructs.</div>
 <div class="content">
 <div class="listingblock">
 <div class="content">
@@ -11420,6 +11421,9 @@ <h2 id="revhistory"><a class="anchor" href="#revhistory"></a>Revision History</h
 <li>
 <p><a href="https://github.com/cf-convention/cf-conventions/issues/410">Issue #410</a>: Delete "on a spherical Earth" from the definition of the <code>latitude_longitude</code> grid mapping in Appendix F</p>
 </li>
+<li>
+<p><a href="https://github.com/cf-convention/cf-conventions/issues/286">Issue #286</a>: Some labels of examples contain "Example" so that their label in the list of examples contains "Example" (affects four examples)</p>
+</li>
 </ul>
 </div>
 <div class="sect2">
@@ -11850,13 +11854,13 @@ <h3 id="_version_1_1_17_january_2008"><a class="anchor" href="#_version_1_1_17_j
 <p>25 November 2005: <a href="#atmosphere-hybrid-height-coordinate">the section called "Atmosphere hybrid height coordinate"</a> : Fixed definition of atmosphere hybrid height coordinate.</p>
 </li>
 <li>
-<p>22 October 2004: Added <a href="#lambert-conformal-projection">Example 5.7, "Lambert conformal projection"</a>.</p>
+<p>22 October 2004: Added <a href="#lambert-conformal-projection">"Lambert conformal projection"</a>.</p>
 </li>
 <li>
 <p>20 September 2004: <a href="#cell-methods">Section 7.3, "Cell Methods"</a> : Changed several incorrect occurrences of the cell method <strong><code>"standard deviation"</code></strong> to <strong><code>"standard_deviation"</code></strong>.</p>
 </li>
 <li>
-<p>1 July 2004: <a href="#multiple-forecasts-from-single-analysis">Example 5.13, "Multiple forecasts from a single analysis"</a> : Added <strong><code>positive</code></strong> attribute to the scalar coordinate p500 to make it unambiguous that the pressure is a vertical coordinate value.</p>
+<p>1 July 2004: <a href="#multiple-forecasts-from-single-analysis">"Multiple forecasts from a single analysis"</a> : Added <strong><code>positive</code></strong> attribute to the scalar coordinate p500 to make it unambiguous that the pressure is a vertical coordinate value.</p>
 </li>
 <li>
 <p>1 July 2004: <a href="#scalar-coordinate-variables">Section 5.7, "Scalar Coordinate Variables"</a> : Added note that use of scalar coordinate variables inhibits interoperability with COARDS conforming applications.</p>
@@ -11940,7 +11944,7 @@ <h3 id="_references"><a class="anchor" href="#_references"></a>References</h3>
 <div id="footer">
 <div id="footer-text">
 Version 1.11 draft<br>
-Last updated 2023-08-21 15:06:32 UTC
+Last updated 2023-08-28 17:31:18 UTC
 </div>
 </div>
 </body>

conformance.html

@@ -1495,7 +1495,7 @@ <h3 id="parametric-vertical-coordinates">Appendix D Parametric Vertical Coordina
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2023-08-21 15:06:28 UTC
+Last updated 2023-08-28 17:31:12 UTC
 </div>
 </div>
 </body>