Changes between Version 9 and Version 10 of Ticket #151


Ignore:
Timestamp:
07/07/16 02:03:33 (3 years ago)
Author:
martin.juckes
Comment:

Dear Jonathan,

I have made those changes. I also amended the new standard name definition to specify use of strings or flags (instead of strings or integers), as it appears sensible to allow the use of flags of type byte, as done in the other examples in section 3.5. I've put in a cross-reference to section 6.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #151 – Description

    v9 v10  
    1414''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 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:
     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 for a variable with standard name `region` and `flag_values` selected from the [http://cfconventions.org/Data/cf-standard-names/docs/standardized-region-names.html standardized region names] (see section 6.1.1):
    1717
    1818Example 3.4. Flag variable with controlled values, using `flag_values`
     
    2121       standard_name: region;
    2222       flag_values: 1, 2, 3;
    23        flag_meanings:'atlantic_arctic_ocean indo_pacific_ocean global_ocean';
     23       flag_meanings:"atlantic_arctic_ocean indo_pacific_ocean global_ocean";
    2424......
    2525values::