Skip to content
StandardsGeospatial and Earth observationOpen standard package
STAC · adopt

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).

Geospatial and Earth observation
What this area is built from, with the open standards it names marked: they are cited or crosswalked, never copied.Source: the Nexus Standards registry: the area record.
  • 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.
01கண்ணோட்டம்

Summary

Registry entrythe external standards register · stac
  1. Version1.1.0 (OGC Community Standard); core text CC BY 4.0
  2. ஆண்டு2025
  3. அணுகல்திறந்துள்ளது
  4. Relationadopt
  5. Verifiedyes: name, body, version and year confirmed at the source
  6. DomainGeospatial and Earth observation
  7. 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
02செயல்முறை

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 steps3 stages2 gates

NXS · Process

OGC standards track

தரநிலை வாழ்க்கைச் சுழற்சி · NS-13 தடம் · பங்களிப்பு வழிகள் · IETF தடம் · W3C தடம் · OGC தடம் · OASIS தடம் · ISO மற்றும் IEC நிலைகள் · இணக்கம் · பதிவு வாழ்க்கைச் சுழற்சி · வழிப்படுத்தல் · கண்காணிப்பு.

A chartered working group drafts, the Architecture Board reviews, public comment follows, and the Technical Committee votes; community standards take a shorter path.

  1. 01 Standards working group

    1. 01SWG charterStart · OGC members proposing the groupThe charter states scope and deliverables; the group works under the Technical Committee policies.
    2. 02Community submissionStart · a community, outside an OGC working groupThe STAC community’s specification is published by OGC as a Community Standard through this path.
    3. 05DraftRecord · the working groupThe group drafts the candidate standard and its conformance classes.
  2. 02 Technical Committee

    1. 03OAB reviewGate · the OGC Architecture BoardThe Architecture Board checks consistency with the OGC baseline.
    2. 04Public commentGate · anyoneComments received are dispositioned by the working group before the vote.
    3. 06TC voteDecision · OGC voting membersThe Technical Committee votes on the candidate standard or the community standard.
  3. 03 OGC publication

    1. 07PublicationOutcome · OGC staffThe standard is published with a document number on the OGC standards page.
    2. 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
Process · OGC track8 operations
படிPhaseசெயல்பாடுWhoDecision ruleபதிவு
01Standards working groupSWG charter (start). The charter states scope and deliverables; the group works under the Technical Committee policies.OGC members proposing the groupcharter approved by the Technical Committeea chartered standards working group
02Standards working groupDraft (record). The group drafts the candidate standard and its conformance classes.the working groupconsensus of the working groupa candidate standard
03Standards working groupCommunity submission (start). The STAC community’s specification is published by OGC as a Community Standard through this path.a community, outside an OGC working groupa community standard is submitted as is, with its usage justificationa submission with a justification
04Technical CommitteeOAB review (gate). The Architecture Board checks consistency with the OGC baseline.the OGC Architecture Boardarchitecture and consistency review before public commentreview comments
05Technical CommitteePublic comment (gate). Comments received are dispositioned by the working group before the vote.anyonea public comment period announced by OGCcomments and dispositions
06Technical CommitteeTC vote (decision). The Technical Committee votes on the candidate standard or the community standard.OGC voting membersapproval by the Technical Committee electronic votethe vote result
07OGC publicationPublication (end). The standard is published with a document number on the OGC standards page.OGC staffpublication after the vote and the Planning Committee’s confirmationthe published standard with its document number
08OGC publicationCommunity standard (record). The community keeps maintaining the specification; OGC publishes the snapshot it approved.OGCpublished as the community maintains it; the body does not develop ita 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.

Compare with the Nexus track and other standards bodies.

03Clause map

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.

Clause map · the document’s public structure, navigableFrom the registry
Clause map6 parts
  1. Parts6
  2. Named sub-parts20
  3. 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).

04குறுக்கு இணைப்பு

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.

Crosswalk graph · geospatial and earth observation, around this standardNexus Standards registry
SpatioTemporal Asset Catalog (STAC) specification: crosswalk59 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 68 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 31 external standards by domain
களம்External standardIssuing bodyRelation
காலநிலைGHG Protocol Corporate Accounting and Reporting StandardWorld Resources Institute and WBCSD (GHG Protocol)cite
காலநிலைGHG Protocol Corporate Value Chain (Scope 3) Accounting…GHG Protocolcite
காலநிலைGHG Protocol Scope 2 GuidanceGHG Protocolcite
காலநிலைGOOS Essential Ocean VariablesIOC-UNESCO Global Ocean Observing Systemadopt
காலநிலைIFRS S2 Climate-related DisclosuresInternational Sustainability Standards Board (IFRS Foundation)crosswalk
காலநிலைINFORM Climate Change Risk Index – Concept and MethodologyEuropean Commission Joint Research Centrecite
காலநிலைIPCC AR6 Working Group II – risk framing (hazard…Intergovernmental Panel on Climate Changeadopt
காலநிலைISO 14090:2019 Adaptation to climate change – Principles…ISO/TC 207/SC 7crosswalk
காலநிலைISO 14091:2021 Adaptation to climate change – Guidelines…ISO/TC 207/SC 7crosswalk
காலநிலைNGFS long-term climate macro-financial scenariosNetwork for Greening the Financial Systemcite
காலநிலைSBTi Corporate Net-Zero StandardScience Based Targets initiativecite
காலநிலைUAE Framework for Global Climate Resilience (Global Goal…UNFCCCcite
Geospatial and Earth observationCCSDS space data system standardsConsultative Committee for Space Data Systemscite
Geospatial and Earth observationInternational Committee on Global Navigation Satellite…UN Office for Outer Space Affairscite
Geospatial and Earth observationISO 19115-1:2014 Geographic information – Metadata – Part…ISO/TC 211crosswalk
Geospatial and Earth observationISO 19157-1:2023 Geographic information – Data quality…ISO/TC 211crosswalk
Geospatial and Earth observationOGC API – Features – Part 1: CoreOpen Geospatial Consortiumadopt
Geospatial and Earth observationOGC API – Records – Part 1: CoreOpen Geospatial Consortiumcrosswalk
Geospatial and Earth observationOGC GeoPackage Encoding StandardOpen Geospatial Consortiumcite
Geospatial and Earth observationOGC GeoSPARQL – A Geographic Query Language for RDF DataOGCadopt
Geospatial and Earth observationOGC SensorML encoding standardOGCadopt
Geospatial and Earth observationOGC SensorThings API Part 1: SensingOpen Geospatial Consortiumcrosswalk
Geospatial and Earth observationRFC 7946 The GeoJSON FormatIETFadopt
Geospatial and Earth observationSpatioTemporal Asset Catalog (STAC) specificationSTAC community; OGC Community Standard 25-004adopt
Geospatial and Earth observationUN-GGIM Integrated Geospatial Information Framework (IGIF)UN Committee of Experts on Global Geospatial Information Managementcite
Nature-related disclosure and ecosystemsIUCN Global Ecosystem TypologyIUCNadopt
Nature-related disclosure and ecosystemsIUCN Red List Categories and CriteriaIUCNadopt
Nature-related disclosure and ecosystemsKunming-Montreal Global Biodiversity Frameworkஉயிரியல் பன்முகத்தன்மை குறித்த உடன்படிக்கைcite
Nature-related disclosure and ecosystemsRecommendations of the Taskforce on Nature-related…TNFDcrosswalk
Nature-related disclosure and ecosystemsSystem of Environmental-Economic Accounting – Ecosystem…UN Statistical Commissioncrosswalk
Nature-related disclosure and ecosystemsUNCCD Scientific Conceptual Framework for Land Degradation…UN Convention to Combat Desertificationcite

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.

05Adoption

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.

Adoption · STACCompiled from public sources
செயல்படுத்தல்Byஇது என்ன
PySTACstac-utilsPython library for reading, writing and validating STAC
STAC BrowserRadiant Earthweb interface for browsing static and dynamic catalogues
stac-validatorstac-utilscommand-line and library validator
Test suite or validatorWhat it checks
stac-validatorvalidates catalogues, collections and items against the published schemas
STAC JSON Schemasthe schemas the community publishes per version
Stack entryபங்குஏற்றுமதி
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.

06பங்களிக்கவும்

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இது என்னWhat it requiresஇணைப்பு
Issue trackerradiantearth/stac-spec issues: errata, proposals, questionsa GitHub accountOpen the issue tracker page
Change requestsproposed text changes, reviewed by the maintainersa GitHub account; the repository’s contribution guideOpen the change requests page
Extensionscommunity extensions, each in its own repositorya GitHub accountOpen the extensions page
Publishing bodyOGC page of the STAC Community Standard (OGC 25-004)OGC membership for the Technical Committee; the page is publicOpen the publishing body page

Process explorer · NXS · Process

Contributing through a standards body

11 steps3 stages1 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.

  1. 01 Contributor

    1. 01Identify the bodyStart · the contributorEach standard package links to the issuing body, its working group or technical committee and its process document.
    2. 02Read IPR and participation rulesStep · the contributorParticipation rules differ by body, from no membership at the IETF to membership at OASIS.
    3. 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.
    4. 07Implement and testExercise · the contributorThe contributor runs the body’s test suite or validator, where the body publishes one.
  2. 02 The standards body

    1. 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.
    2. 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.
    3. 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.
    4. 08Implementation reportRecord · the body or the working groupImplementations are listed as submitted, in alphabetical order.
  3. 03 Nexus Standards

    1. 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.
    2. 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.
    3. 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
Process · from a comment at the body to a register change11 operations
படிPhaseசெயல்பாடுWhoDecision ruleபதிவு
01ContributorIdentify the body (start). Each standard package links to the issuing body, its working group or technical committee and its process document.the contributorthe register names the body and links to its own pagethe body’s page, linked from the package
02ContributorRead 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 contributormembership, patent policy and contributor agreements are set by the body and read at the sourcethe requirements of the channel
03The standards bodyJoin 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 committeethe channel belongs to the body and follows its process documenta list subscription, an issue account, a membership
04The standards bodyFile 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 trackeran issue is the body’s record, cited by URLan issue with a stable link
05The standards bodyPublic 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 processthe body decides under its own rules; the Nexus Standards record the public outcomecomment dispositions by the body
06ContributorPropose 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 channeltext is proposed through the body’s own channel; the body’s text remains with the bodya change request, an Internet-Draft or a comment with wording
07ContributorImplement and test (exercise). The contributor runs the body’s test suite or validator, where the body publishes one.the contributora passing run is evidence of implementationa test run with the suite version and time
08The standards bodyImplementation report (record). Implementations are listed as submitted, in alphabetical order.the body or the working grouplisted as the body publishes it, without rankingthe report, linked
09Nexus StandardsCite 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 editorscited by identifier, clause number and URL (NS-14); a recorded relation does not imply equivalencea crosswalk entry or a clause citing the source
10Nexus StandardsChange 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 recordedevery change is submitted as a change proposal under NS-13a change proposal with a UNI
11Nexus StandardsRegister change (end). The register entry is amended and the package page is regenerated from it.editors, with reasons on recordaccepted, rejected or withdrawn in writing; the history is retainedthe 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.

08Updates

Latest releases from the body

Updates · listed for reference

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பதிவேடுவடிவம்Browser readDeliveryCadence
github.stac-spec.releasesexternal-apisatomnonegoverned data service, site integration, build-time snapshothourly
github.api.stac-spec.releasesexternal-apisjsonதிறந்துள்ளதுgoverned data service, browser-direct read, build-time snapshothourly
github.stac-spec.issuesexternal-apisjsonதிறந்துள்ளதுgoverned data service, browser-direct readhourly
stac.schemasdata-sourcesjsonதிறந்துள்ளதுbrowser-direct read, build-time snapshoton release
ogc.standards.stac.pagedata-sourceshtmlunknownbuild-time snapshotweekly
ogc.news.feeddata-sourcesrssunknowngoverned data service, build-time snapshotdaily
github.api.releases.genericexternal-apisjsonதிறந்துள்ளதுgoverned data service, browser-direct read, build-time snapshothourly, within the unauthenticated rate limit

7 data sources listed.

09கேள்விகள்

கேள்விகளும் பதில்களும்.

Do the standards reproduce STAC?
No. The page names and links the document, lists its part numbers and titles, and cites it by identifier and clause number; the text remains with the body.
Where do the updates come from?
From the body’s own channels, once licence review of the data source is complete; until then, the page shows the latest version recorded in the registry.
Is the relation a conformance statement?
No. A relation is a registry entry. Conformance is shown clause by clause through attestations under NS-11.
தரநிலைகள்

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.

நிலையும் பயன்பாடும். Nexus Standards என்பவை NS-13-இன் கீழ் திறந்த செயல்முறையின் மூலம் உருவாக்கப்பட்டு, தன்னார்வப் பயன்பாட்டுக்காக வெளியிடப்பட்ட முன்மொழியப்பட்ட தரநிலைகள்; அவை சான்றளிப்போ, அங்கீகாரமோ, ஒழுங்குமுறை ஒப்புதலோ அல்ல; ஏற்பு உலகளாவிய தரநிலை மன்றத்தின் முடிவாகவும், ஒவ்வொரு நாட்டிலும் அதன் தேசியத் தரநிலை மன்றத்தின் முடிவாகவும் இருக்கிறது. ஒரு UNI (Unique Nexus Identifier) ஒரு கலைப்பொருளை அடையாளம் காண்கிறது; அதைச் சான்றளிப்பதில்லை. தரநிலை அமைப்புகளின் பெயர்களும் அவற்றின் தரநிலைகளும் அவற்றின் பொறுப்பாளர்களுக்கு உரியவை, ஆவணங்களை அடையாளம் காண மட்டுமே பயன்படுத்தப்படுகின்றன; எந்த வெளிப்புறத் தரநிலையின் உரையும் இங்கே மீண்டும் வழங்கப்படவில்லை. Nexus Standards இங்கே பெயரிடப்பட்ட எந்தத் தரநிலை அமைப்புடனும் இணைக்கப்படவில்லை, அவற்றால் ஆதரிக்கப்படவோ சான்றளிக்கப்படவோ இல்லை.

உரிமங்கள்: தரநிலை உரை, பதிவேடுகள், திட்டவரைவுகள் மற்றும் தரவுக்கு CC BY 4.0; குறிப்புக் குறியீட்டுக்கு Apache-2.0. வெளிப்புறத் தரநிலைகள் அவற்றின் சொந்த உரிமங்களின் கீழ் பெயர், எண் மற்றும் இணைப்பால் மேற்கோள் காட்டப்படுகின்றன. மூன்றாம் தரப்புத் தரவு, நூலகங்கள் மற்றும் எழுத்துருக்கள் அவற்றின் சொந்த உரிமங்களைத் தக்க வைக்கின்றன: மூன்றாம் தரப்பு அறிவிப்புகளைப் பாருங்கள்.