Custom Query (125 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (79 - 81 of 125)

Ticket Resolution Summary Owner Reporter
#52 fixed Clarification of _FillValue attribute cf-conventions@… ros
Description

Section 2.5.1 of the convention defines the standard for the _FillValue attribute stating that it is "a scalar attribute and must have the same type as its variable." There are no specific exclusions, but I think that allowing the value NaN isn't a good idea.

The NetCDF standard doesn't prohibit the use of NaN as a _FillValue, but I did find several recommendations not to use NaN. The problem with allowing NaN is that any calculation or comparisons with NaN will return false.

I suggest a modification to the convention to recommend against the use of NaN as a _FillValue value.

Thoughts?

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

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".

#50 fixed Upgrade CF Checker to use CDAT-5.x and udunits2 ros ros
Description

Upgrade CF Checker to work with CDAT-5.x and udunits2

Note: See TracQuery for help on using queries.