#154: Machine Readable Standardised Region List
-----------------------------+------------------------------
Reporter: martin.juckes | Owner: cf-conventions@…
Type: task | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
Description changed by martin.juckes:
Old description:
> The CF Standardised Region List http://cfconventions.org/Data/cf-
> standard-names/docs/standardized-region-names.html is currently only
> available as a HTML page. Ideally, it should be available as a machine
> readable document, so that the CF checker and other software can access
> the names, as discussed, for instance, in #153.
>
> This, with #153, would bring the number of CF vocabulary documents to 4:
> * CF Standard Names
> * CF Area Types
> * CF Standardised Regions
> * CF Rules Related to Standard Names (under discussion: #153)
>
> There should be some common approach to structuring these documents,
> based on the establised practise with the CF Standard Names (an XML
> reference document, exported to SKOS). There is also an interest in
> having JSON versions, which are easier to import into python.
New description:
The CF Standardised Region List http://cfconventions.org/Data/cf-standard-
names/docs/standardized-region-names.html is currently only available as a
HTML page. Ideally, it should be available as a machine readable document,
so that the CF checker and other software can access the names, as
discussed, for instance, in #153.
This, with #153, would bring the number of CF vocabulary documents to 4:
* CF Standard Names
* CF Area Types
* CF Standardised Regions
* CF Rules Related to Standard Names (under discussion: #153)
There should be some common approach to structuring these documents, based
on the establised practise with the CF Standard Names (an XML reference
document, exported to SKOS). There is also an interest in having JSON
versions, which are easier to import into python.
The general structure used for the standard names and area types is clear:
some header information followed by a sequence of "entry" elements, each
with an "id" attribute and one or more simple child elements. The schema
used for area types could be used directly for standard regions. The CF
standard name schema could be adapted for the rules with some minor change
of terminology.
--
--
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/154#comment:2>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
