Custom Query (125 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (88 - 90 of 125)

Ticket Resolution Summary Owner Reporter
#43 fixed Upgrade CF checker to CF-1.4 ros ros
Description

Add the following checks for CF-1.4

5.6 Grid Mappings and Projects
Additional valid values of grid_mapping_name are:

lambert_cylindrical_equal_area
latitude_longitude
mercator
orthographic
vertical_perspective

7.3 Cell Methods
Requirements:

  • The type of the cell_methods attribute is a string whose value is one or more blank separated word lists, each with the form
    dim1: [dim2: [dim3: ...]] method [where type1 [over type2]] [within|over days|years] [(comment)]
    
    where brackets indicate optional words. The valid values for dim1 [dim2 [dim3 ...] ] are the names of dimensions of the data variable, names of scalar coordinate variables of the data variable, valid standard names, or the word area. The valid values of method are contained in Appendix E. The valid values for type1 are the name of a string-valued auxiliary or scalar coordinate variable with a standard_name of area_type, or any string value allowed for a variable of standard_name of area_type. If type2 is a string-valued auxiliary coordinate variable, it is not allowed to have a leading dimension (the number of strings) of more than one. When the method refers to a climatological time axis, the suffixes for within and over may be appended.

Recommendations:

  • If a data variable has any dimensions or scalar coordinate variables referring to horizontal, vertical or time dimensions, it should have a cell_methods attribute with an entry for each of these spatiotemporal dimensions or scalar coordinate variables. (The horizontal dimensions may be covered by an area entry.)
  • Except for entries whose cell method is point, all numeric coordinate variables and scalar coordinate variables named by cell_methods should have bounds or climatology attributes.
#42 fixed Amendments to CF Conformance document cf-conventions@… ros
Description

Whilst updating the checker I came across a couple of omissions in the conformance document. I propose the follow additions, which are implied in the convention but not explicitly stated in the conformance document.

3.5 Flags
Requirements:

 * If the flag_values attribute is present then the flag_meanings attribute must be specified.

 * The type of the flag_meanings attribute is a string whose value is a
blank separated list of words or phrases (words connected by underscores).
#41 fixed Upgrade CF checker to CF-1.3 ros ros
Description

CF-1.3 additional requirements include:

Section 3.5 Flags
Requirements:

  • The flag_values attribute must have the same type as the variable to which it is attached.
  • The number of flag_values attribute values must equal the number of words or phrases appearing in the flag_meanings string.
  • The number of flag_masks attribute values must equal the number of words or phrases appearing in the flag_meanings string.
  • Variables with a flag_masks attribute must have a type that is compatible with bit field expression (char, byte, short and int), not floating-point (float, real, double), and the flag_masks attribute must have the same type.
  • The flag_masks attribute values must be non-zero.
  • The flag_values attribute values must be mutually exclusive among the set of flag_values attribute values defined for that variable.

Recommendations:

  • When flag_masks and flag_values are both defined, the Boolean AND of each entry in flag_values with its corresponding entry in flag_masks should equal the flag_values entry, ie, the mask selects all the bits required to express the value.
Note: See TracQuery for help on using queries.