Custom Query (125 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 125)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#39 fixed Error in check of units attribute for coordinate variables cf-checker@… ros
Description

3.1 of the convention states that "The units attribute is required for all variables that represent dimensional quantities."

Yet a Netcdf file like the following does not generate errors indicating that the units attribute is missing for any of the coordinate variables.

dimensions:
       longitude = 144 ;
       latitude = 91 ;
       press = 10 ;
       species = 6 ;
       rec = UNLIMITED ; // (12 currently)
       word = 13 ;

variables:
       float concentrations(rec, species, press, latitude, longitude) ;
             concentrations:long_name = "CFC concentrations" ;
             concentrations:Units = "pptv" ;
       float longitude(longitude) ;
       float latitude(latitude) ;
       float press(press) ;
       float species(species) ;
             species:long_name = "species" ;
             species:coord_labels = "species" ;
             species:selection_category = "NULL" ;
       float rec(rec) ;
             rec:long_name = "month" ;
             rec:coord_labels = "month" ;
             rec:selection_category = "NULL" ;
       char const_labels(species, word) ;
             const_labels:selection_category = "NULL" ;
       char month(rec, word) ;
             month:selection_category = "NULL" ;
} 
#40 fixed CF Checker falls over when standard_name attribute is the empty string. cf-checker@… ros
Description

The CF checker was falling over in the event of a standard_name attribute which was an empty string, as it did "string.split(.....)[0]" on the attribute value.

#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.
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.