Custom Query (124 matches)


Show under each result:

Results (13 - 15 of 124)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#20 fixed Incorrect parsing of flag_values attribute ros ros

Section 3.5 of the conventions document states that "The flag_values attribute is the same type as the variable to which it is attached, and contains a list of the possible flag values."


current_speed_qc:flag_values = 0b, 1b, 2b ;

But Appendix A specified the flag_values type as string. This is what the checker based the check on which is incorrect.

The conventions document has been corrected. The CF checker needs to implement this change too.

#21 fixed Coordinate Types/Systems checks for CF-1.1 cf-checker@… ros

Following clarification of the axis attribute in CF-1.1 the following 2 checks need to be added to the CF Checker.

Section 4: "Coordinate Types"
Requirement: The axis attribute is not allowed for auxiliary coordinate variables.

Section 5: "Coordinate Systems"
Recommendation: All horizontal coordinate variables (in the unidata sense) should have an axis attribute.

#22 fixed missing_value & _FillValue bug fix ros ros

Section 2.5.1 states that the missing_value and _FillValue attributes must be the same type as the variable to which they are attached. The CF checker throws a python error if these attributes are of type string/char.

The following generates the error, but is actually valid.

char variable(time) ;
    variable:standard_name = "surface_temperature" ;
    variable:_FillValue = "M" ;
    variable:missing_value = "M" ;

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.