From 0bc82a14643de59903a39e07378be6f8d0427db9 Mon Sep 17 00:00:00 2001 From: Charlie Zender Date: Fri, 26 Jul 2024 13:07:12 -0700 Subject: [PATCH] Update ch08.adoc Co-authored-by: David Hassell --- ch08.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch08.adoc b/ch08.adoc index 5f334a74..13a67958 100644 --- a/ch08.adoc +++ b/ch08.adoc @@ -695,7 +695,7 @@ Use of these conventions ensures that all quantized variables are clearly marked These conventions must not be used with data variables of integer type, or any other kind of CF variable. This is because fields that describe idealized or reference coordinate grids, or grid transformations, are often known to the highest precision possible. -These fields can include spatial and temporal coordinate variables (e.g., **`latitude`**, **`longitude`**, **`level`**, **`time`**) and properties derived from these coordinates (e.g., **`area`**, **`volume`**). +These variables can include spatial and temporal coordinate variables (e.g., **`latitude`**, **`longitude`**, **`level`**, **`time`**), properties derived from these coordinates (e.g., **`area`**, **`volume`**), and variables referenced by the **`formula_terms`** attribute of a coordinate variable. Degrading the precision of such grid properties may have unintended side effects on the accuracy of subsequent operations such regridding, interpolation, and conservation checks which should generally be performed with the highest precision possible. For the same reason, it is recommended not to quantize any data variable which is referenced by a **`formula_terms`** attribute of any variable.