Custom Query (124 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (43 - 45 of 124)

Ticket Resolution Summary Owner Reporter
#103 fixed Corrections to Appendices A and H davidhassell ros
Description

Appendix A:

  • cf_role, featureType, instance_dimension and sample_dimension should all be of type "S" not C or N.
  • It is not obvious that the "Use" should be D for instance_dimension and sample_dimension. The count and index variables are not data variables, but not coord vars either. Suggest putting "-" for them, and add to the key that "-" is for variables with a special purpose.

Appendix H:

  • Section H2: In the examples station_name is an auxiliary coord var and so needs to be identified as one in the coordinates attribute.
  • Section H2: _FillValue for the variables humidity and temp should be -999.9f
  • Example H8: coordinates attribute for pressure, temperature and humidity should be set to "time lon lat z"

I've not looked beyond Section H4 so some of these might apply there as well.

#102 fixed Request for two additional cell_methods davidhassell rhorne@…
Description

The GOES-R ground system generates products that conmtains two statistics that are not defined in the current set of cell methods in the CF standard. The two statistics are:

(1) root_mean_square (2) total_sum_of_squares

This trac item requests that these two statistics be added to the set of CF defined cell_methods. The changes to the CF standard required to support this are as follows...

In CF standard paragraph 7.3. Cell Methods, change this sentence:

The values of method should be selected from the list in Appendix E, Cell Methods, which includes point, sum, mean, maximum, minimum, mid_range, standard_deviation, variance, mode, and median.

To:

The values of method should be selected from the list in Appendix E, Cell Methods, which includes point, sum, mean, maximum, minimum, mid_range, standard_deviation, variance, mode, median, root_mean_square, and total_sum_of_squares.

In CF standard Appendix E Cell Methods, add the following two rows to Table E.1 Cell Methods:

(first new row)

cell_methods column: root_mean_square

Units column u

Description column: Root mean square (RMS)

(second new row)

cell_methods column: total_sum_of_squares

Units column u2

Description column: Total sum of squares (TSS)

#100 fixed Clarifications to the preamble of sections 4 and 5 davidhassell jonathan
Description

Dear all

I have the honour of opening ticket number 100. In this ticket, Steve Hankin and I have a number of changes to propose to the text of section 5, with the intention of clarifying it, not changing what it means. Therefore this is a defect ticket, but please object if you think it is changing the meaning, or making it any less clear!

Cheers

Jonathan

Replace this text in the first paragraph

A variable's spatiotemporal dimensions are used to locate data values in time and space. This is accomplished by associating these dimensions with the relevant set of latitude, longitude, vertical, and time coordinates.

with

A data variable's dimensions are used to locate data values in time and space or as a function of other independent variables. This is accomplished by associating these dimensions with the relevant set of latitude, longitude, vertical, time and any non-spatiotemporal coordinates.

These changes clarify that coordinate systems belong to data variables (rather than any other type of variable in a CF-netCDF file) and recognise the use of non-spatiotemporal dimensions.

Replace this text in the second paragraph

All of a variable's dimensions that are latitude, longitude, vertical, or time dimensions (see Section 1.2, "Terminology") must have corresponding coordinate variables, i.e., one-dimensional variables with the same name as the dimension

with

Any of a variable's dimensions that is an independently varying latitude, longitude, vertical, or time dimension (see Section 1.2, "Terminology") and that has a size greater than one must have a corresponding coordinate variable, i.e., a one-dimensional variable with the same name as the dimension

These changes remove the implication that spatiotemporal scalar coordinates might be prohibited, and allow for discrete axes (section 4.5, used extensively in section 9).

Replace this text in the third paragraph

All of a variable's spatiotemporal dimensions that are not latitude, longitude, vertical, or time dimensions are required to be associated with the relevant latitude, longitude, vertical, or time coordinates via the new coordinates attribute of the variable

with

Any longitude, latitude, vertical or time coordinate which depends on more than one spatiotemporal dimension must be identified by the coordinates attribute of the data variable.

This change is for clarity.

Replace this text in the fifth paragraph

The use of coordinate variables is required whenever they are applicable. That is, auxiliary coordinate variables may not be used as the only way to identify latitude and longitude coordinates that could be identified using coordinate variables.

with

If the longitude, latitude, vertical or time coordinate is multi-valued and varies in only one dimension, it is not permitted to store it as an auxiliary coordinate variable.

This change is for simplicity and clarity. The use of coordinate variables where applicable is already required by the second paragraph.

Append to the fifth paragraph

If the longitude, latitude, vertical or time coordinate is single-valued, it may be stored either as a coordinate variable with a dimension of size one, or as a scalar coordinate variable (Section 5.7).

This change recognises the use of spatiotemporal scalar coordinates.

Note: See TracQuery for help on using queries.