Custom Query (125 matches)


Show under each result:

Results (91 - 93 of 125)

Ticket Resolution Summary Owner Reporter
#40 fixed CF Checker falls over when standard_name attribute is the empty string. cf-checker@… ros

The CF checker was falling over in the event of a standard_name attribute which was an empty string, as it did "string.split(.....)[0]" on the attribute value.

#39 fixed Error in check of units attribute for coordinate variables cf-checker@… ros

3.1 of the convention states that "The units attribute is required for all variables that represent dimensional quantities."

Yet a Netcdf file like the following does not generate errors indicating that the units attribute is missing for any of the coordinate variables.

       longitude = 144 ;
       latitude = 91 ;
       press = 10 ;
       species = 6 ;
       rec = UNLIMITED ; // (12 currently)
       word = 13 ;

       float concentrations(rec, species, press, latitude, longitude) ;
             concentrations:long_name = "CFC concentrations" ;
             concentrations:Units = "pptv" ;
       float longitude(longitude) ;
       float latitude(latitude) ;
       float press(press) ;
       float species(species) ;
             species:long_name = "species" ;
             species:coord_labels = "species" ;
             species:selection_category = "NULL" ;
       float rec(rec) ;
             rec:long_name = "month" ;
             rec:coord_labels = "month" ;
             rec:selection_category = "NULL" ;
       char const_labels(species, word) ;
             const_labels:selection_category = "NULL" ;
       char month(rec, word) ;
             month:selection_category = "NULL" ;
#37 fixed Conventions for Point Observation Data stevehankin caron

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:

Note: See TracQuery for help on using queries.