Skip to content

Instantly share code, notes, and snippets.

@jbants

jbants/stac_ogc_cs_letter.adoc

Created July 10, 2023 22:17
Show Gist options
  • Save jbants/88afecbb8017f5b73a4bedfe7b9c3f53 to your computer and use it in GitHub Desktop.
Save jbants/88afecbb8017f5b73a4bedfe7b9c3f53 to your computer and use it in GitHub Desktop.
Download ZIP
OGC Community Spec for the STAC API
Raw
stac_ogc_cs_letter.adoc

Open Geospatial Consortium

Submission Date: 2023-07-02

Approval Date:   <yyyy-mm-dd>

Internal reference number of this OGC® document:    YY-nnnrx

Category: OGC® Community Standard Work Item Justification

Authors:   STAC Project Steering Committee

STAC Community Standard

Copyright notice

Copyright © 2023 Open Geospatial Consortium

To obtain additional rights of use, visit http://www.opengeospatial.org/legal/

1. Introduction

This document provides a justification to the OGC Technical Committee (TC) for consideration of STAC as a Community standard. This justification, along with the submitted candidate Community standard, will form the basis for TC review and vote to approve the start of a Work Item as the first step in the Community standard process for this standard.

The submitters agree to abide by the TC Policies and Procedures and OGC Intellectual Property Rights Policy (http://www.opengeospatial.org/ogc/policies) during the processing of this submission.

Once approved, the Community standard Work Item defined by this document is valid for six (6) months.

2. Overview of proposed submission

The SpatioTemporal Asset Catalog (STAC) is an open specification designed to improve the discovery, accessibility, and interoperability of geospatial data. It consists of two efforts of work, a static implementation with no moving parts, and adynamic implementation that responds to user queiries.

STAC supports geospatial interoperability requirements by providing a common metadata framework to expose geospatial assets, such as satellite imagery and other spatiotemporal raster data. Interoperability eases the search process and allows users to find and use data in various formats and from multiple providers. The STAC specification evolved from different organizations' collaborative efforts to increase the interoperability of searching for and using satellite imagery. Its development was driven by the need to overcome the challenges associated with different tools, APIs, and data formats in geospatial technology. The primary use case for STAC is to simplify the process of finding and using geospatial assets. It is beneficial for data providers, developers, and data users. Providers can more easily expose their data to the world, developers have a standardized way to interact with geospatial data, and users can more easily find and ingest the data they need.

STAC is backed by various tools and resources that facilitate its use. These include a browser for STAC catalogs and a STAC compliant web API for searching and serving metadata for geospatial data​​. == Relationship to other OGC Standards

STAC implements and extends the OGC Features API and describes many datasets using the standard. STAC and OGC Features API evolved together and continually aligned based on new user feedback and new implementations.

In addition to the OGC Features API, the dynamic catalogs of STAC align well with the OGC Records API. Multiple development sprints have been completed with OGC members to ensure alignment between STAC and OGC.

3. Alignment with OGC Standards Baseline

The STAC standard fits well within the OGC API roadmap and aligns with the OGC Features API. STAC also attempts to align with OGC Records API

This specification enhances OGC operations and community involvement by describing geospatial data to newer, non-geospatial companies

4. Evidence of implementation

The following is a list of publically available implementations of the STAC specification

Microsoft Planetary Computer AWS Public Data Store Element84 Earthsearch Google Earth Engine USGS Astrogeology group

Date of most recent version:

Version 1.0.0 of the STAC Spec was released on May 25, 2021

Implementation description:

The implementations above exist as both static and dynamic STAC. However, this document refernces the static specification only - stac-spec. The core JSON documents and link structures are encoded in the file, and work as long as things are structured properly. A static catalog is crawled by search engines and active catalogs; it can not respond to queries. But it is incredibly reliable, as there are no moving parts, no clusters or databases to maintain. The goal of STAC is to expose as much asset metadata online as possible, so the static catalog offers a very low barrier to entry for anyone with geospatial assets to make their data searchable. The STAC standard fits well within the OGC API roadmap and aligns with the OGC Features API. STAC also attempts to align with OGC Records API

This specification enhances OGC operations and community involvement by describing geospatial data to newer, non-geospatial parties.

Implementation URL: https://www.stacspec.com

Is implementation complete?

  • ✓ Yes

  • ❏ No

If not, what portions of the proposed Community standard are implemented?

5. Public availability

Is the proposed Community standard currently publicly available?

  • ✓ Yes

  • ❏ No

6. Supporting OGC Members

Sparkgeo Element84 Planet Labs Microsoft WWU Münster EURAC

7. Intellectual Property Rights

Will the contributor retain intellectual property rights?

  • ❏ Yes

  • ✓ No

If yes, the contributor will be required to work with OGC staff to properly attribute the submitter’s intellectual property rights.

If no, the contributor will assign intellectual property rights to the OGC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment