Custom Query (125 matches)


Show under each result:

Results (73 - 75 of 125)

Ticket Resolution Summary Owner Reporter
#45 fixed Conventions attribute should have value "CF-1.4". cf-conventions@… jonathan

Second paragraph of 1.3 should read

We recommend that the NUG defined attribute Conventions be given the string value "CF-1.4" to identify datasets that conform to these conventions.

This mistake was spotted by Constantine Khroulev. We should remember to keep this sentence up-to-date in each version.


#47 fixed error in example 7.4 cf-conventions@… eaton

Example 7.4 in the conventions doc has an unlimited time dimension which must be listed as the first dimension in C ordering. The variables pressure, maxtemp, and ppn all have dimensions (station,time). All three should be modified to read (time,station).

#51 fixed syntax consistency for dimensionless vertical coordinate definitions cf-conventions@… taylor13

I suggest that for readability and for consistency in the syntax of the definitions of dimensionless vertical coordinates, the following changes be made in the CF documentation.

  1. Where the coordinate definition involves a construction like "for k<=k_c .... for k>k_c ....", follow each "for" phrase with a colon. [This is currently done inconsistently.]
  1. Where the coordinate definition involves a term that is subsequently defined (e.g., the C(k) in the ocean-S coordinate), precede the definition of the term with "where".

These make the definitions easier to read. Note that CF does not mandate storage of the coordinate definitions in the netCDF files, but for CMIP, we store the formulas as a text string attribute attached to the coordinate variable and named "formula".

Note: See TracQuery for help on using queries.