Skip to content

stac-extensions/cmip6

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

30 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CMIP6 Extension Specification

This document explains the CMIP6 Extension to the SpatioTemporal Asset Catalog (STAC) specification.

This extension specifies a set of properties for the Coupled Model Intercomparison Project Phase 6 (CMIP6) prefixed with cmip6.

Fields

The fields in the table below can be used in these parts of STAC documents:

  • Catalogs
  • Collections
  • Item Properties (incl. Summaries in Collections)
  • Assets (for both Collections and Items, incl. Item Asset Definitions in Collections)
  • Links
Field Name Type Description
cmip6:activity_id string e.g. ScenarioMIP
cmip6:data_specs_version string e.g. 01.00.28
cmip6:frequency string e.g. mon
cmip6:further_info_url string e.g. https://furtherinfo.es-doc.org/CMIP6.UA.MCM-UA-1-0.ssp245.none.r1i1p1f2
cmip6:grid string e.g. lat-lon
cmip6:grid_label string e.g. gn
cmip6:institution string e.g.
cmip6:institution_id string e.g. UA
cmip6:mip_era string e.g. CMIP6
cmip6:source string e.g.
cmip6:source_id string e.g. MCM-UA-1-0
cmip6:source_type string e.g. AOGCM
cmip6:experiment string e.g.
cmip6:experiment_id string e.g. ssp245
cmip6:sub_experiment string e.g.
cmip6:sub_experiment_id string e.g. none
cmip6:nominal_resolution string e.g. 250 km
cmip6:table_id string e.g. Amon
cmip6:variable_id string e.g. psl
cmip6:variant_label string e.g.
cmip6:Conventions string e.g.
cmip6:creation_date string e.g.
cmip6:forcing_index integer e.g.
cmip6:initialization_index integer e.g.
cmip6:license string e.g.
cmip6:physics_index integer e.g.
cmip6:realization_index integer e.g.
cmip6:product string e.g.
cmip6:realm string e.g.
cmip6:tracking_id string e.g.

All contributions are subject to the STAC Specification Code of Conduct. For contributions, please follow the STAC specification contributing guide Instructions for running tests are copied here for convenience.

Running tests

The same checks that run as checks on PR's are part of the repository and can be run locally to verify that changes are valid. To run tests locally, you'll need npm, which is a standard part of any node.js installation.

First you'll need to install everything with npm once. Just navigate to the root of this repository and on your command line run:

npm install

Then to check markdown formatting and test the examples against the JSON schema, you can run:

npm test

This will spit out the same texts that you see online, and you can then go and fix your markdown or examples.

If the tests reveal formatting problems with the examples, you can fix them with:

npm run format-examples

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 3

  •  
  •  
  •