Custom Query (124 matches)


Show under each result:

Results (49 - 51 of 124)

Ticket Resolution Summary Owner Reporter
#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" ;

#23 fixed Amendments to CF Conventions documents cf-conventions@… ros

Whilst correcting some bugs in the CF checker I came across some errors/omissions in the CF Conventions document and Conformance Document. I propose the following changes.

2.5.1 Missing Data
The table in Appendix A incorrectly states that missing_value and _FillValue are Numeric attributes. This is inconsistent with CF 2.5.1, which says, "The scalar attribute with the name _FillValue and of the same type as its variable is recognized by the netCDF library as the value used to pre-fill disk space allocated to the variable."

The correction required is:

In Appendix A change the type from N to D for missing_value and _FillValue in the table.

3.3 Standard Name Modifiers
The requirements and recommendations for standard name modifiers are missing from the Conformance document.

Change Section 3.3 to

3.3 Standard Name
 * The standard_name attribute takes a string value comprised of a standard
   name optionally followed by one or more blanks and a standard name
 * The legal values for the standard name are contained in the standard name
 * The legal values for the standard name modifier are contained in Appendix C,
   Standard Name Modifiers.

5.6 Grid Mappings and Projections
The requirements and recommendations for grid mappings are missing from the Conformance document.

Add a section

5.6 Grid Mappings and Projections

 * The type of the grid_mapping attribute is a string whose value is a single
   variable name.
 * The specified variable name (known as a grid mapping variable) must exist
   in the file.
 * The grid mapping variable must have the grid_mapping_name attribute. The 
   legal values for the grid_mapping_name attribute are contained in
   Appendix F.
 * The grid mapping variable should have 0 dimensions.


Note: See TracQuery for help on using queries.