Custom Query (125 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (76 - 78 of 125)

Ticket Resolution Summary Owner Reporter
#112 fixed create FAQ seed document for CF conventions graybeal graybeal
Description

Create a seed document for a FAQ for CF conventions. Expect it to be added to the (new) CF wiki on github, exact place to be determined. (Matthew Harris and Jeff Painter to discuss the exact place.)

#118 fixed Add an attribute in Appendix F to identify the geoid or other geopotential datum davidhassell jonathan
Description

Some geophysical quantities, including some vertical coordinates, are defined with reference to the geoid. For example, the standard_name of altitude is the height above the geoid. CF does not have a default geoid, because the convention is used for both model-generated and real-world data, and climate models typically do not use a real-world geoid. When CF is used for real-world data, it may be necessary to desirable to specify which geoid is being used.

This proposal is to define a new attribute geoid_name to be included in the table of Appendix F for the legal attributes of the grid_mapping variable. This attribute will have type S (string) and its description will be "The name of the geoid. Corresponds to an OGC WKT VERT_DATUM name."

Ticket 80, which was agreed a long time ago for inclusion in CF 1.7, also adds some attributes to Appendix F. This proposal is complementary to and consistent with that one.

Jonathan Gregory

#123 fixed clarification of "difference sources" in Section 3.3 davidhassell jonathan
Description

Following a suggestion of Aaron Sweeney, I propose that this sentence in the first paragraph of Sect 3.3 should be amended:

"For some applications it would be desirable to have a more definitive description of the quantity, which would allow users of data from different sources to determine whether quantities were in fact comparable."

to read

"For some applications it would be desirable to have a more definitive description of the quantity, which would allow users of data from different sources (some of which might be models and others observational) to determine whether quantities were in fact comparable."

Since this is a defect ticket, which aims to clarify the convention but not to alter it in meaning, it will be accepted by default unless there is an objection or alternative suggestion.

Jonathan

Note: See TracQuery for help on using queries.