Custom Query (124 matches)
Results (34 - 36 of 124)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#49 | fixed | Clarification of flag_meanings attribute | jonathan | martin.juckes |
Description |
1. Title
2. ModeratorJonathan Gregory 3. Requirement
4. Initial Statement of Technical Proposal
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
6. Status Quo
|
|||
#150 | duplicate | Clarification of use of standard region names in "region" variables. | cf-conventions@… | martin.juckes |
Description |
The CF standard name region has the current description "A variable with the standard name of region contains strings which indicate geographical regions. These strings must be chosen from the standard region list." This description implies that the variable should be of character type, but it is often more convenient to have an integer variable and make a clear link to the region names using flag_values and flag_meanings. The proposal is to clarify the definition so that either usage is acceptable and include an example of the latter usage in the convention text. It is also proposed that an appendix be added to the CF Convention text to state clearly any constraints on file meta-data which are implied by the CF Standard Name definitions, so that it is possible to test such constraints in the CF checker. New description for CF standard name "region"A variable with the standard name of region must have values associated with geographical regions from the CF standard region list, either as a character variable using the region names directly or as an integer variable with values linked to region names through flag_values and flag_meanings attributes. New usage example in CF Convention textThe following should be placed at the end of 6.1.1, after example 6.2 A variable with standard name 'region' may also be of integer type and use 'flag_values' and 'flag_meanings' attributes to express the relationship between the integers and the region names: integer basin(basin); standard_name: region; flag_values: '1 2 3'; flag_meanings:'atlantic_arctic_ocean indo_pacific_ocean global_ocean'; ...... values:: basin: 1, 2, 3;
New Appendix SectionChange "Appendix B: Standard Name Table Format" to: Appendix B: Standard NamesB.1: Standard Name Table Format..... and B.2 Constraints for specific standard namesB.2.1: region Variables with standard name region must be one of:
|
|||
#100 | fixed | Clarifications to the preamble of sections 4 and 5 | davidhassell | jonathan |
Description |
Dear all I have the honour of opening ticket number 100. In this ticket, Steve Hankin and I have a number of changes to propose to the text of section 5, with the intention of clarifying it, not changing what it means. Therefore this is a defect ticket, but please object if you think it is changing the meaning, or making it any less clear! Cheers Jonathan Replace this text in the first paragraph
with
These changes clarify that coordinate systems belong to data variables (rather than any other type of variable in a CF-netCDF file) and recognise the use of non-spatiotemporal dimensions. Replace this text in the second paragraph
with
These changes remove the implication that spatiotemporal scalar coordinates might be prohibited, and allow for discrete axes (section 4.5, used extensively in section 9). Replace this text in the third paragraph
with
This change is for clarity. Replace this text in the fifth paragraph
with
This change is for simplicity and clarity. The use of coordinate variables where applicable is already required by the second paragraph. Append to the fifth paragraph
This change recognises the use of spatiotemporal scalar coordinates. |