Custom Query (125 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (40 - 42 of 125)

Ticket Resolution Summary Owner Reporter
#45 fixed Conventions attribute should have value "CF-1.4". cf-conventions@… jonathan
Description

Second paragraph of 1.3 should read

We recommend that the NUG defined attribute Conventions be given the string value "CF-1.4" to identify datasets that conform to these conventions.

This mistake was spotted by Constantine Khroulev. We should remember to keep this sentence up-to-date in each version.

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 fixed Convert CF Conventions to DocBook XML halliday1 halliday1
Description
  • Convert CF Conventions 1.0 and CF Standard Name Table to DocBook? XML.
  • Create scripts to automatically generate PDF, HTML, and chunked HTML output from DocBook?, and make it simple to update the website with new document revisions.
  • Add the baseline documents and build scripts to the CF Subversion repository.
Note: See TracQuery for help on using queries.