Custom Query (125 matches)


Show under each result:

Results (70 - 72 of 125)

Ticket Resolution Summary Owner Reporter
#36 fixed Correction proposed to subsection headings of Appendix D cf-conventions@… jonathan

The various vertical coordinates described by Appendix D of the CF standard should be titled as unnumbered subsections, not as examples. They were unnumbered subsections in the beta CF standard document, and the formatting was changed when the document was translated to docbook. There was a similar problem with Appendix F, which was corrected by ticket 18.


#42 fixed Amendments to CF Conformance document cf-conventions@… ros

Whilst updating the checker I came across a couple of omissions in the conformance document. I propose the follow additions, which are implied in the convention but not explicitly stated in the conformance document.

3.5 Flags

 * If the flag_values attribute is present then the flag_meanings attribute must be specified.

 * The type of the flag_meanings attribute is a string whose value is a
blank separated list of words or phrases (words connected by underscores).
#44 fixed clarify that coordinates indicate gridpoint location cf-conventions@… jonathan

In view of the problem raised by Thomas Lavergne on the email list in the thread "X and Y projection coordinate (center vs corner)", I propose that we insert the following clarification at the end of the introduction to section 4 of the CF standard:

The values of a coordinate variable or auxiliary coordinate variable indicate the locations of the gridpoints. The locations of the boundaries between cells are indicated by bounds variables (see section 7.1 on "Cell Boundaries"). If bounds are not provided, an application might reasonably assume the gridpoints to be at the centers of the cells, but we do not require that in this standard.

I don't believe that inserting this text would change the intention of the CF standard.

Note: See TracQuery for help on using queries.