SpatioTemporal Asset Catalog (STAC) specification
The registry entry for STAC, with the body’s development process, the clause map, the crosswalk, adoption, participation channels, tools and updates. Artefacts that apply it carry a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-3, NS-3b, NS-5.
- Open standards: SpatioTemporal Asset Catalog (STAC); OGC API – Features – Part 1: Core; OGC API – Records – Part 1: Core; OGC Cloud Optimized GeoTIFF Standard; GeoParquet; Zarr storage specification; NetCDF Climate and Forecast (CF) Metadata Conventions; RFC 7946 The GeoJSON Format; UN-GGIM Integrated Geospatial Information Framework.
- Data and feeds: NASA Common Metadata Repository (CMR) search API; Copernicus Data Space Ecosystem STAC catalogue; geoBoundaries gbOpen; Global Human Settlement Layer (GHSL); Natural Earth vector and raster data.
- Couples with: Visualisation, figures and maps; Data and datasets; Real-time and streaming data; Hazards and disaster risk reduction.
Summary
- Version1.1.0 (OGC Community Standard); core text CC BY 4.0
- Year2025
- Accessopen
- Relationadopt
- Verifiedyes: name, body, version and year confirmed at the source
- DomainGeospatial and Earth observation
- Updateslisted for reference
The relation is shown as recorded in the registry.
- Operations
- 8
- in the OGC track
- Clause map
- 6
- parts, numbers and titles
- Siblings
- 12
- entries in geospatial and earth observation
- Data sources
- 7
- listed for reference
How OGC develops a standard such as STAC
The stages of the body’s own process document, step by step: the actor, the decision rule and the record each operation leaves. OGC Technical Committee Policies and Procedures.
Process explorer · NXS · Process
OGC standards track
8 steps·3 stages·2 gates
NXS · Process
OGC standards track
Umjikelezo wempilo wezinga · Indlela ye-NS-13 · Imijelo yeminikelo · Indlela ye-IETF · Indlela ye-W3C · Indlela ye-OGC · Indlela ye-OASIS · Izigaba ze-ISO ne-IEC · Ukuhambisana · Umjikelezo werekhodi · Ukuqondisa · Ukuqapha.
A chartered working group drafts, the Architecture Board reviews, public comment follows, and the Technical Committee votes; community standards take a shorter path.
01 Standards working group
- 01SWG charterStart · OGC members proposing the groupThe charter states scope and deliverables; the group works under the Technical Committee policies.
- 02Community submissionStart · a community, outside an OGC working groupThe STAC community’s specification is published by OGC as a Community Standard through this path.
- 05DraftRecord · the working groupThe group drafts the candidate standard and its conformance classes.
02 Technical Committee
- 03OAB reviewGate · the OGC Architecture BoardThe Architecture Board checks consistency with the OGC baseline.
- 04Public commentGate · anyoneComments received are dispositioned by the working group before the vote.
- 06TC voteDecision · OGC voting membersThe Technical Committee votes on the candidate standard or the community standard.
03 OGC publication
- 07PublicationOutcome · OGC staffThe standard is published with a document number on the OGC standards page.
- 08Community standardRecord · OGCThe community keeps maintaining the specification; OGC publishes the snapshot it approved.
OGC Technical Committee Policies and Procedures · OGC standardsAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Standards working group | SWG charter (start). The charter states scope and deliverables; the group works under the Technical Committee policies. | OGC members proposing the group | charter approved by the Technical Committee | a chartered standards working group |
| 02 | Standards working group | Draft (record). The group drafts the candidate standard and its conformance classes. | the working group | consensus of the working group | a candidate standard |
| 03 | Standards working group | Community submission (start). The STAC community’s specification is published by OGC as a Community Standard through this path. | a community, outside an OGC working group | a community standard is submitted as is, with its usage justification | a submission with a justification |
| 04 | Technical Committee | OAB review (gate). The Architecture Board checks consistency with the OGC baseline. | the OGC Architecture Board | architecture and consistency review before public comment | review comments |
| 05 | Technical Committee | Public comment (gate). Comments received are dispositioned by the working group before the vote. | anyone | a public comment period announced by OGC | comments and dispositions |
| 06 | Technical Committee | TC vote (decision). The Technical Committee votes on the candidate standard or the community standard. | OGC voting members | approval by the Technical Committee electronic vote | the vote result |
| 07 | OGC publication | Publication (end). The standard is published with a document number on the OGC standards page. | OGC staff | publication after the vote and the Planning Committee’s confirmation | the published standard with its document number |
| 08 | OGC publication | Community standard (record). The community keeps maintaining the specification; OGC publishes the snapshot it approved. | OGC | published as the community maintains it; the body does not develop it | a Community Standard |
Table.A standards working group is chartered and drafts; the Architecture Board reviews; the draft goes to public comment; the Technical Committee votes and OGC publishes. A community standard follows a shorter path: a submission with a justification, a vote and publication without an OGC working group. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: OGC Technical Committee Policies and Procedures · OGC standards.
Public structure of the document
Part numbers and titles, linked to the body’s own document; the machine-readable artefact published by the body is linked at the source.
- Parts6
- Named sub-parts20
- Machine artefactSTAC Item JSON Schema (v1.1.0)
- Text reproducednone
Numbers and titles only; every part opens the body’s own document.
Obligations that a Nexus Standard adopts or profiles are written as Nexus clauses (NS-10) citing the source by identifier and clause number (NS-14).
STAC among the standards of geospatial and earth observation
The registry relation is adopt: The Nexus Standards use the external standard as it is for a function. Evidence: Validation of values against the external scheme.
The crosswalk as a table: 31 external standards by domain
| Domain | External standard | Issuing body | Relation |
|---|---|---|---|
| Isimo sezulu | GHG Protocol Corporate Accounting and Reporting Standard | World Resources Institute and WBCSD (GHG Protocol) | cite |
| Isimo sezulu | GHG Protocol Corporate Value Chain (Scope 3) Accounting… | GHG Protocol | cite |
| Isimo sezulu | GHG Protocol Scope 2 Guidance | GHG Protocol | cite |
| Isimo sezulu | GOOS Essential Ocean Variables | IOC-UNESCO Global Ocean Observing System | adopt |
| Isimo sezulu | IFRS S2 Climate-related Disclosures | International Sustainability Standards Board (IFRS Foundation) | crosswalk |
| Isimo sezulu | INFORM Climate Change Risk Index – Concept and Methodology | European Commission Joint Research Centre | cite |
| Isimo sezulu | IPCC AR6 Working Group II – risk framing (hazard… | Intergovernmental Panel on Climate Change | adopt |
| Isimo sezulu | ISO 14090:2019 Adaptation to climate change – Principles… | ISO/TC 207/SC 7 | crosswalk |
| Isimo sezulu | ISO 14091:2021 Adaptation to climate change – Guidelines… | ISO/TC 207/SC 7 | crosswalk |
| Isimo sezulu | NGFS long-term climate macro-financial scenarios | Network for Greening the Financial System | cite |
| Isimo sezulu | SBTi Corporate Net-Zero Standard | Science Based Targets initiative | cite |
| Isimo sezulu | UAE Framework for Global Climate Resilience (Global Goal… | UNFCCC | cite |
| Geospatial and Earth observation | CCSDS space data system standards | Consultative Committee for Space Data Systems | cite |
| Geospatial and Earth observation | International Committee on Global Navigation Satellite… | UN Office for Outer Space Affairs | cite |
| Geospatial and Earth observation | ISO 19115-1:2014 Geographic information – Metadata – Part… | ISO/TC 211 | crosswalk |
| Geospatial and Earth observation | ISO 19157-1:2023 Geographic information – Data quality… | ISO/TC 211 | crosswalk |
| Geospatial and Earth observation | OGC API – Features – Part 1: Core | Open Geospatial Consortium | adopt |
| Geospatial and Earth observation | OGC API – Records – Part 1: Core | Open Geospatial Consortium | crosswalk |
| Geospatial and Earth observation | OGC GeoPackage Encoding Standard | Open Geospatial Consortium | cite |
| Geospatial and Earth observation | OGC GeoSPARQL – A Geographic Query Language for RDF Data | OGC | adopt |
| Geospatial and Earth observation | OGC SensorML encoding standard | OGC | adopt |
| Geospatial and Earth observation | OGC SensorThings API Part 1: Sensing | Open Geospatial Consortium | crosswalk |
| Geospatial and Earth observation | RFC 7946 The GeoJSON Format | IETF | adopt |
| Geospatial and Earth observation | SpatioTemporal Asset Catalog (STAC) specification | STAC community; OGC Community Standard 25-004 | adopt |
| Geospatial and Earth observation | UN-GGIM Integrated Geospatial Information Framework (IGIF) | UN Committee of Experts on Global Geospatial Information Management | cite |
| Nature-related disclosure and ecosystems | IUCN Global Ecosystem Typology | IUCN | adopt |
| Nature-related disclosure and ecosystems | IUCN Red List Categories and Criteria | IUCN | adopt |
| Nature-related disclosure and ecosystems | Kunming-Montreal Global Biodiversity Framework | Convention on Biological Diversity | cite |
| Nature-related disclosure and ecosystems | Recommendations of the Taskforce on Nature-related… | TNFD | crosswalk |
| Nature-related disclosure and ecosystems | System of Environmental-Economic Accounting – Ecosystem… | UN Statistical Commission | crosswalk |
| Nature-related disclosure and ecosystems | UNCCD Scientific Conceptual Framework for Land Degradation… | UN Convention to Combat Desertification | cite |
Nexus Standards in the graph: NS-3b, NS-5. A relation is a register entry, never a compliance claim.
2 Nexus Standards · 3 domains · 31 external standards · 23 issuing bodies · 0 implementing repositories. Relations (adopt, profile, crosswalk, cite) are as recorded in the register; names and standards remain with their stewards.
Crosswalk graph59 nodes and 68 links: this standard, the entries in the area’s principal domains, their bodies, the Nexus Standards the area lists and their implementers. Relations are shown as recorded in the registry.
Implementations, listed as submitted
Implementations and validators in alphabetical order; the implementers of the area’s Nexus Standards with their implementation status; and the entries of the open-standards stack that name this standard. Listings are not a ranking.
| Ukuqalisa | By | Yini |
|---|---|---|
| PySTAC | stac-utils | Python library for reading, writing and validating STAC |
| STAC Browser | Radiant Earth | web interface for browsing static and dynamic catalogues |
stac-validator | stac-utils | command-line and library validator |
| Test suite or validator | What it checks |
|---|---|
stac-validator | validates catalogues, collections and items against the published schemas |
| STAC JSON Schemas | the schemas the community publishes per version |
| Stack entry | Indima | Export |
|---|---|---|
| SpatioTemporal Asset Catalog (STAC) 1.1 (1.0 compatible) | spatio-temporal assets (earth observation and risk record products) | stac Item and Collection (NS-3b section 1; extent only as stated) |
NoteThe outline, participation channels, implementations, test suites, schema and data feeds on this page were compiled from the body’s public pages on 16 October 2026; all other information is taken from the registry entry.
Participation in STAC
The participation channels of the body and the requirements of each, followed by the general path from a comment at the body to a registry change in the Nexus Standards.
| Channel | Yini | What it requires | Link |
|---|---|---|---|
| Issue tracker | radiantearth/stac-spec issues: errata, proposals, questions | a GitHub account | Open the issue tracker page |
| Change requests | proposed text changes, reviewed by the maintainers | a GitHub account; the repository’s contribution guide | Open the change requests page |
| Extensions | community extensions, each in its own repository | a GitHub account | Open the extensions page |
| Publishing body | OGC page of the STAC Community Standard (OGC 25-004) | OGC membership for the Technical Committee; the page is public | Open the publishing body page |
Process explorer · NXS · Process
Contributing through a standards body
11 steps·3 stages·1 gate
NXS · Process
Contributing through a standards body
A contributor joins a body’s channel under its rules, files issues, reviews, proposes and tests, and Nexus Standards cites the outcome through a change proposal.
01 Contributor
- 01Identify the bodyStart · the contributorEach standard package links to the issuing body, its working group or technical committee and its process document.
- 02Read IPR and participation rulesStep · the contributorParticipation rules differ by body, from no membership at the IETF to membership at OASIS.
- 06Propose textStep · the contributor, in the body’s channelWording goes to the body’s own channel. In Nexus Standards, the obligation becomes a clause (NS-10) citing the source clause.
- 07Implement and testExercise · the contributorThe contributor runs the body’s test suite or validator, where the body publishes one.
02 The standards body
- 03Join a channelStep · the body’s working group or committeeMailing lists and their archives, issue trackers and public comment lists are listed per package with what each requires.
- 04File an issueRecord · the contributor, in the body’s trackerAn erratum, a question or a proposal becomes an issue in the body’s tracker; the Nexus Standards cite it by link.
- 05Public reviewGate · the body, under its processPublic reviews and last calls are the body’s own stages. The monitoring console shows their dates once the body’s feed exists.
- 08Implementation reportRecord · the body or the working groupImplementations are listed as submitted, in alphabetical order.
03 Nexus Standards
- 09Cite the outcomeStep · Nexus Standards editorsThe outcome at the body becomes a register entry: a corrected version, a new crosswalk entry or a clause that cites the source.
- 10Change proposalRecord · any person, with identity recordedA change proposal is a change request to the canonical repository, with a public proposal record. Editors decide with reasons.
- 11Register changeOutcome · editors, with reasons on recordThe register entry is amended and the package page is regenerated from it.
OpenStand principles (RFC 6852) · NS-13: development process · NS-14: crosswalk and conformance claimsAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Contributor | Identify the body (start). Each standard package links to the issuing body, its working group or technical committee and its process document. | the contributor | the register names the body and links to its own page | the body’s page, linked from the package |
| 02 | Contributor | Read IPR and participation rules (step). Participation rules differ: an IETF working group requires no membership; an OASIS technical committee requires membership; W3C groups have community and member forms. | the contributor | membership, patent policy and contributor agreements are set by the body and read at the source | the requirements of the channel |
| 03 | The standards body | Join a channel (step). Mailing lists and their archives, issue trackers and public comment lists are listed per package with what each requires. | the body’s working group or committee | the channel belongs to the body and follows its process document | a list subscription, an issue account, a membership |
| 04 | The standards body | File an issue (record). An erratum, a question or a proposal becomes an issue in the body’s tracker; the Nexus Standards cite it by link. | the contributor, in the body’s tracker | an issue is the body’s record, cited by URL | an issue with a stable link |
| 05 | The standards body | Public review (gate). Public reviews and last calls are the body’s own stages. The monitoring console shows their opening and closing dates once the body’s feed is available. | the body, under its process | the body decides under its own rules; the Nexus Standards record the public outcome | comment dispositions by the body |
| 06 | Contributor | Propose text (step). Wording is submitted to the body’s own channel. In the Nexus Standards, the same obligation is expressed as a clause (NS-10) that cites the source by clause number. | the contributor, in the body’s channel | text is proposed through the body’s own channel; the body’s text remains with the body | a change request, an Internet-Draft or a comment with wording |
| 07 | Contributor | Implement and test (exercise). The contributor runs the body’s test suite or validator, where the body publishes one. | the contributor | a passing run is evidence of implementation | a test run with the suite version and time |
| 08 | The standards body | Implementation report (record). Implementations are listed as submitted, in alphabetical order. | the body or the working group | listed as the body publishes it, without ranking | the report, linked |
| 09 | Nexus Standards | Cite the outcome (step). The outcome at the body becomes a register entry: a corrected version, a new crosswalk entry or a clause that cites the source. | Nexus Standards editors | cited by identifier, clause number and URL (NS-14); a recorded relation does not imply equivalence | a crosswalk entry or a clause citing the source |
| 10 | Nexus Standards | Change proposal (record). A change proposal is a change request to the canonical repository, with a proposal record in the public change record. Editors decide with written reasons. | any person, with identity recorded | every change is submitted as a change proposal under NS-13 | a change proposal with a UNI |
| 11 | Nexus Standards | Register change (end). The register entry is amended and the package page is regenerated from it. | editors, with reasons on record | accepted, rejected or withdrawn in writing; the history is retained | the amended register entry and its history |
Table.A contributor identifies the standards body, reads its participation and intellectual property rules, joins a channel, files an issue, takes part in the public review, proposes text, and implements and tests; the body publishes the implementation report. The Nexus Standards cite the outcome through a change proposal that becomes a register correction, a crosswalk entry or a clause. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: OpenStand principles (RFC 6852) · NS-13: development process · NS-14: crosswalk and conformance claims.
Tools and their availability
Run the test suite in the browser
A browser-based test run on worked examples is in progress. In the meantime, stac-validator, published by the body, can be run at the source.
AvailableOpen the schema
STAC Item JSON Schema (v1.1.0), at the body’s own address.
Available · composed in the browserDownload the profile
The composer opens with this standard and the area’s Nexus Standards selected, and produces YAML or JSON with citations and the licence line.
PlannedOpen in an integrated application
An integration point on this page is reserved for compatible applications and is not yet active.
A passing test run constitutes implementation evidence.
Latest releases from the body
Data sources are listed for reference; live data is displayed once licence review is complete. The latest version of the standard recorded in the registry is 1.1.0 (OGC Community Standard); core text CC BY 4.0 (2025). Latest at STAC community.
After licence review, data are delivered, in order of preference, through the governed data service, the site integration, a direct browser read of an open endpoint, or a build-time snapshot with its timestamp; the age of the data is always shown. Monitoring console: worked example.
| Data source | Registry | Format | Browser read | Delivery | Cadence |
|---|---|---|---|---|---|
github.stac-spec.releases | external-apis | atom | none | governed data service, site integration, build-time snapshot | hourly |
github.api.stac-spec.releases | external-apis | json | vulekile | governed data service, browser-direct read, build-time snapshot | hourly |
github.stac-spec.issues | external-apis | json | vulekile | governed data service, browser-direct read | hourly |
stac.schemas | data-sources | json | vulekile | browser-direct read, build-time snapshot | on release |
ogc.standards.stac.page | data-sources | html | unknown | build-time snapshot | weekly |
ogc.news.feed | data-sources | rss | unknown | governed data service, build-time snapshot | daily |
github.api.releases.generic | external-apis | json | vulekile | governed data service, browser-direct read, build-time snapshot | hourly, within the unauthenticated rate limit |
7 data sources listed.
Questions and answers.
Do the standards reproduce STAC?
Where do the updates come from?
Is the relation a conformance statement?
Around geospatial and Earth observation.
Building on STAC
Relations to this standard are recorded in the registry. Changes are submitted as proposals under NS-13 and may be prepared through the working groups and the National Working Groups of participating countries.
Isimo nokusetshenziswa. Ama-Nexus Standards angamazinga ahlongozwayo athuthukiswe ngenqubo evulekile ngaphansi kwe-NS-13 futhi ashicilelwe ukuze asetshenziswe ngokuzithandela; akusona isitifiketi, ukugunyazwa noma imvume yomlawuli, futhi ukwamukela kuhlala kuyisinqumo se-Global Standards Council futhi, ezweni ngalinye, se-National Standards Council yalo. I-UNI (Unique Nexus Identifier) ihlonza into; ayiyiqinisekisi. Amagama ezinhlaka zamazinga namazinga azo angawabaphathi bawo futhi asetshenziswa kuphela ukuhlonza amadokhumenti; awukho umbhalo wezinga langaphandle okhiqizwe kabusha lapha. I-Nexus Standards ayihlangene, ayesekwa futhi ayiqinisekiswanga yinoma iyiphi inhlangano yamazinga eshiwo lapha.
Amalayisense: i-CC BY 4.0 embhalweni wezindinganiso, amarejista, amaskimu nedatha; i-Apache-2.0 kukhodi yereferensi. Izindinganiso zangaphandle zicashunwa ngegama, inombolo nesixhumanisi ngaphansi kwamalayisense azo. Idatha, amalabhulali namafonti abantu besithathu agcina amalayisense awo: bheka Izaziso zabantu besithathu.