Custom Query (125 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (31 - 33 of 125)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Ticket Resolution Summary Owner Reporter
#35 fixed delete "associated" in CF standard, chapter 5, introduction, paragraph 3 cf-conventions@… jonathan
Description

This was raised by John Caron, and Brian Eaton and Jonathan Gregory agree.

Change

We recommend that the name of a multidimensional coordinate variable should not match the name of any of its dimensions because that precludes supplying an associated coordinate variable for the dimension.

to

We recommend that the name of a multidimensional coordinate variable should

not match the name of any of its dimensions because that precludes supplying a coordinate variable for the dimension.

i.e. delete "associated", which has a technical meaning in the CF standard that is not meant here.

#36 fixed Correction proposed to subsection headings of Appendix D cf-conventions@… jonathan
Description

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.

Jonathan

#37 fixed Conventions for Point Observation Data stevehankin caron
Description

1. Title

Conventions for Point Observation Data

2. Moderator

Steve Hankin

3. Requirement

Current conventions are oriented towards gridded data. This proposal extends the framework to specify how to encode "point observation" data.

4. Initial Statement of Technical Proposal

We show six types of point observational data, and describe a general way to encode many variations. The main technical extension is a simple way to describe ragged arrays, for the case when rectangular arrays are too inefficient.

5. Benefits

  • Many data providers would like to use CF conventions when storing their observational data.
  • This will allow a standard for converting things like BUFR data into netCDF.

6. Status Quo

Currently sections 5.4 and 5.5 describe 2 examples of point observations (station time series and trajectories). This proposal generalizes those.

7. Detailed Proposal

Because of the length of this, I have written it as a Microsoft Word file to make it easy to edit. I can reformat later when it is close to being finished.

Some background docs and earlier drafts:

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