USGCRP / gcis-conventions

Repository for the collection, management, and versioning of the GCIS data management conventions.
https://usgcrp.github.io/gcis-conventions/
1 stars 0 forks source link

Regions Convention Discussion #35

Open lomky opened 6 years ago

lomky commented 6 years ago

A ticket to discuss the conventions surrounding Regions.

Current Region Conventions. (n/a)

Finding Fields:

gcis=# \d+ region
                                   Table "gcis_metadata.region"
   Column    |       Type        | Modifiers | Storage  | Stats target |        Description
-------------+-------------------+-----------+----------+--------------+---------------------------
 identifier  | character varying | not null  | extended |              | A descriptive identifier.
 label       | character varying | not null  | extended |              | A human readable label.
 description | character varying |           | extended |              | A description.
Indexes:
    "region_pkey" PRIMARY KEY, btree (identifier)
Check constraints:
    "ck_region_identifier" CHECK (identifier::text ~ similar_escape('[a-z0-9_-]+'::text, NULL::text))
Referenced by:
    TABLE "publication_region_map" CONSTRAINT "publication_region_map_region_identifier_fkey" FOREIGN KEY (region_identifier) REFERENCES region(identifier) ON UPDATE CASCADE ON DELETE CASCADE
Triggers:
    audit_trigger_row AFTER INSERT OR DELETE OR UPDATE ON region FOR EACH ROW EXECUTE PROCEDURE audit.if_modified_func('true')
    audit_trigger_stm AFTER TRUNCATE ON region FOR EACH STATEMENT EXECUTE PROCEDURE audit.if_modified_func('true')

Provenance Connections:
none.

Relationships:

publication
lomky commented 6 years ago

Region Conventions

Current Use Case

None.

Desired Use Case

To be attached to the USGCRP Assessments in support of search and navigation.
Can be added for other publications that specify regions.

Regions should be able to be sub-sets and supersets.

We may also include regions not explicitly called out by reports, such as 'US', "Contiguous US".

Fields

Extant

identifier
A simplified version of the label with dashes.

In the future, we would like to change this to be a UUID to avoid too specific or broad naming.

label
Should match the most recent NCA report specified name of the region.
If no region, should match governmental name.

description
Ideally, taken from the text of the report.
At a minimum, a list of the governmental boundaries contained.

Desired

spatial_extent (sp?)
a geoJSON object

url
Used in the case of USGCRP regions to point to the longform region coverage on globalchange.gov
Could be used for other created regions for other reports, if they have an equivalent page.

Provenance Conventions

Extant

none

Desired

region

region that replaces another in a future report (i.e. NCA3 Great Plains was replaced by NCA4 Northern & Southern Great Plains) using dct:replaces / dct:issReplacedBy

Relationships

Extant

publication
Used to connect reports, chapters, figures, findings, and tables to region(s).

Desired

region
region that is part of another region (i.e. VA is a part of Southeast). Would be created as a region_map with parent/child relationship.

gcmd_keywords
used for the location gcmd keyword set to associate states with their NCA regions.

lomky commented 6 years ago

NCA4 Regions Discussion

NCA3 Matching Regions

Alaska Hawaiʻi and U.S. Affiliated Pacific Islands Midwest Northeast Northwest Southwest

New Needed Regions

NCA3's Southeast and Caribbean
=>
Southeast
U.S. Caribbean

NCA3's Great Plains
=>
Northern Great Plains
Southern Great Plains