Changes between Version 2 and Version 5 of Ticket #151


Ignore:
Timestamp:
07/05/16 02:51:48 (3 years ago)
Author:
martin.juckes
Comment:

Dear Jonathan,

In the draft of CF-1.7 section 6 is "Labels and Alternative Coordinates" and 6.1 is "Labels", which looks suitable to me. Example 6.2 has a region variable as a coordinate, but the text is about how to encode geographical regions in a variable. I can't see how this fits into section 5 ("Coordinates"). Am I missing something here?

On the cf-checker: a NetCDF file with a variable:

float basin(index):
  standard_name: region

is passed by the checker as valid, with a warning for the absence of a units attribute on the variable. If the variable is defined as in the example above and invalid region names are used, this is also passed (I've updated the example to change flag_values from a string, which the checker does not allow, to a list of integers). So these details are not currently checked.

regards. Martin

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #151 – Description

    v2 v5  
    1919int basin(lat, lon);
    2020       standard_name: region;
    21        flag_values: '1 2 3';
     21       flag_values: 1, 2, 3;
    2222       flag_meanings:'atlantic_arctic_ocean indo_pacific_ocean global_ocean';
    2323......