Skip to content

Commit

Permalink
Update ch07.adoc
Browse files Browse the repository at this point in the history
Sec. 7.1:  Require exact string match for functional attributes on boundary variables.
Issue cf-convention#265
  • Loading branch information
Dave-Allured authored Dec 1, 2020
1 parent 9fd0f4c commit 9fa9ab2
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion ch07.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ When gridded data does not represent the point values of a field but instead rep

To represent cells we add the attribute **`bounds`** to the appropriate coordinate variable(s). The value of **`bounds`** is the name of the variable that contains the vertices of the cell boundaries. We refer to this type of variable as a "boundary variable." __A boundary variable will have one more dimension than its associated coordinate or auxiliary coordinate variable.__ The additional dimension should be the most rapidly varying one, and its size is the maximum number of cell vertices. Since a boundary variable is considered to be part of a coordinate variable's metadata, it is not necessary to provide it with attributes such as **`long_name`** and **`units`**.

Boundary variable attributes which determine the coordinate type (**`units`**, **`standard_name`**, **`axis`** and **`positive`**) or those which affect the interpretation of the array values (**`units`**, **`calendar`**, **`leap_month`**, **`leap_year`** and **`month_lengths`**) must always agree exactly with the same attributes of its associated coordinate, scalar coordinate or auxiliary coordinate variable. To avoid duplication, however, it is recommended that these are not provided to a boundary variable.
Attributes which determine the coordinate type (**`units`**, **`standard_name`**, **`axis`** and **`positive`**), or those which affect the interpretation of the array values (**`units`**, **`calendar`**, **`leap_month`**, **`leap_year`** and **`month_lengths`**), should be inherited from the associated parent coordinate variable, rather than being attached to the boundary variable itself. Duplication of such attributes on the boundary variable is permissible but not recommended. When such duplicate attributes are provided, they must be an exact string match with the same attributes on the parent variable.

If a parametric coordinate variable with a **`formula_terms`** attribute (section 4.3.2) also has a **`bounds`** attribute, its boundary variable must have a **`formula_terms`** attribute too. In this case the same terms would appear in both (as specified in Appendix D), since the transformation from the parametric coordinate values to physical space is realized through the same formula. For any term that depends on the vertical dimension, however, the variable names appearing in the formula terms would differ from those found in the **`formula_terms`** attribute of the coordinate variable itself because the boundary variables for formula terms are two-dimensional while the formula terms themselves are one-dimensional.

Expand Down

0 comments on commit 9fa9ab2

Please sign in to comment.