Changes between Version 5 and Version 9 of Ticket #151


Ignore:
Timestamp:
07/07/16 01:50:01 (3 years ago)
Author:
martin.juckes
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #151 – Description

    v5 v9  
    55=== region ===
    66
    7 A variable with the `standard_name` of `region` contains strings which indicate a geographical region or integers which can be translated to strings using `flag_values` and `flag_meanings` attributes. These strings are standardised. Values must be taken from the CF standard region list.
     7A variable with the `standard_name` of `region` contains strings which indicate a geographical region or flags which can be translated to strings using `flag_values` and `flag_meanings` attributes. These strings are standardised. Values must be taken from the CF standard region list.
    88
    99=== area_type ===
    1010
    11 A variable with the `standard_name` of `area_type` contains strings which indicate the nature of the surface e.g. land, sea, sea_ice, or integers which can be translated to strings using `flag_values` and `flag_meanings` attributes. These strings are standardised. Values must be taken from the area_type table.
     11A variable with the `standard_name` of `area_type` contains strings which indicate the nature of the surface e.g. land, sea, sea_ice, or flags which can be translated to strings using `flag_values` and `flag_meanings` attributes. These strings are standardised. Values must be taken from the area_type table.
    1212
    1313== New usage example in CF Convention text ==
    14 ''The following should be placed at the end of 6.1.1, after example 6.2''
     14''The following should be placed after example 3.3, renumbering examples 3.4 and 3.5 to 3.5 and 3.6 respectively (text checked for cross-references to "3.4" and "3.5" and none found)''
    1515
    16 A variable with standard name of `region`, `area_type` or any other standard name which requires string-valued values from a defined list may alternatively be of integer type and use `flag_values` and `flag_meanings` attributes to record the translation between the integers and the string values, for instance:
     16A variable with standard name of `region`, `area_type` or any other standard name which requires string-valued values from a defined list may use flags together with `flag_values` and `flag_meanings` attributes to record the translation to the string values. The following example illustrates this using integer flag values:
    1717
     18Example 3.4. Flag variable with controlled values, using `flag_values`
    1819{{{
    1920int basin(lat, lon);
     
    2627}}}
    2728 
    28 == New Appendix Section ==
    29 ''Change "Appendix B: Standard Name Table Format" to:''
     29== Hook in section 3.3 to highlight existence of constraints implied by standard name ==
    3030
    31 == Appendix B: Standard Names ==
    32 === B.1: Standard Name Table Format ===
    33 .....
     31''In section 3.3, append to the paragraph about "description", after
     32"The description is meant to clarify the qualifiers of the fundamental quantities such as which surface a quantity is defined on or what the flux sign conventions are. We don"t attempt to provide precise definitions of fundumental physical quantities (e.g., temperature) which may be found in the literature." the following:''
    3433
    35 ''and''
     34The description may define rules on the variable type and attributes (such as in example 3.4) which must be complied with by any variable carrying that standard name.
    3635
    37 === B.2 Constraints for specific standard names ===
    38 
    39 B.2.1: region
    40 
    41 Variables with standard name `region` must be one of:
    42  * type character, with values taken from the CF standard region list;
    43  * type integer, with `flag_values` and `flag_meanings` attributes. The flag_meanings attributes must be a space separatd list of values from the CF standard region list (see example 6.2).
    44 
    45 Variables with standard name `area_type` must be one of:
    46  * type character, with values taken from the area type table;
    47  * type integer, with `flag_values` and `flag_meanings` attributes. The flag_meanings attributes must be a space separatd list of values from the area type table (analogous to example 6.2).
     36''Note that also that there is a typo in the text cited aboove `don"t` instead of `don't`''
    4837
    4938