Custom Query (125 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (82 - 84 of 125)

Ticket Resolution Summary Owner Reporter
#49 fixed Clarification of flag_meanings attribute jonathan martin.juckes
Description

1. Title

Clarification of flag_meanings attribute

2. Moderator

Jonathan Gregory

3. Requirement

Clear definition and greater range of characters in flag_meanings attribute.

4. Initial Statement of Technical Proposal

Section 3.5 of the convention states "The flag_meanings attribute is a string whose value is a blank separated list of descriptive words or phrases, one for each flag value.", and a "word" is currently interpreted by the CF-checker to consist only of alphanumeric characters, ruling out hyphens and brackets which may be useful in this context. The proposal is that a word in this context should be defined to consist of alphanumeric characters plus underscore '_', period '.', plus '+', hyphen '-', or "at" sign '@', to be consistent with the character set allowed for netCDF variable/dim/attr names [there is no particular need for this consistency, except to avoid having multiple definitions of what constitutes a word].

The above sentence from section 3.5 should be modified to read "The flag_meanings attribute is a string whose value is a blank separated list of descriptive words or phrases, one for each flag value. Each word or phrase consisting of characters from the alphanumeric set or from the following four: '-', '.', '+', '@'.",

5. Benefits

More meaningful "flag_meanings" will be possible.

E.g. for a dataset of eco-regions, flag_meanings such as "Alberta-British Columbia foothills forests" could be used.

6. Status Quo

There is ambiguity in the current standard, which I believe should be alleviated.

#48 fixed Minor typo in equivalent_reflectivity_factor definition apamment Greg Rappa
Description

The word reflectivity is spelled incorrectly as "relectivity".

This typo appears in both files: cf-standard-name-table.html and cf-standard-name-table.xml

#47 fixed error in example 7.4 cf-conventions@… eaton
Description

Example 7.4 in the conventions doc has an unlimited time dimension which must be listed as the first dimension in C ordering. The variables pressure, maxtemp, and ppn all have dimensions (station,time). All three should be modified to read (time,station).

Note: See TracQuery for help on using queries.