#151: Clarification of use of standard region names in "region" variables.
-----------------------------+------------------------------
Reporter: martin.juckes | Owner: cf-conventions@…
Type: enhancement | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
Comment (by jonathan):
Dear Martin
Thanks for making this proposal. As you know I agree with the principle.
I'd like to generalise it to other similar cases, so I would suggest
modifying your text
A variable with standard name of `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:
to
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:
and then give your example as it is. (I think "translate" is more explicit
than "relationship" but you may disagree!) This also requires a modified
definition for `area_type`:
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.
I'm not convinced about modifying Appendix B. I feel that it should be
adequate to note the constraints for specific standard names in the table
itself. We could also make a note about the existence of constraints on
the standard name page. If we were to make a separate list of them, it
should be comprehensive. For instance, there are a number which expect or
require particular coordinates variables to exist.
Best wishes
Jonathan
--
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/151#comment:1>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
