title

OGC API - Common - Part 2: Geospatial Data

Content-Type

text/html; charset=UTF-8

keywords

ogcdoc, OGC document, geographic information, spatial data, spatial things, dataset, distribution, API, json, html, OpenAPI, REST, Common

DC.subject

ogcdoc, OGC document, geographic information, spatial data, spatial things, dataset, distribution, API, json, html, OpenAPI, REST, Common

description

The OGC standards baseline has been extended to include Resource Oriented ArchitecturesResource Oriented Architectures and Web APIsWeb APIs. In the course of developing OGC Web API standards, some practices proved to be common across multiple OGC Web API standards. These common practices are documented in the OGC API - Common Multi-Part Standard. OGC API - Common standards serve as reusable building-blocks. Standards developers can use these building-blocks in the construction of OGC Web API Standards. The result is a modular suite of coherent API standards which can be adapted by a system designer for the unique requirements of their system. Spatial data is rarely considered as a single entity. Feature CollectionsFeature Collections, CoveragesCoverages, Data SetsData Sets. They are all aggregations of SpatialSpatial or TemporalTemporal Resources. It stands to reason that an OGC Web API would also expose its' holdings as aggregates of spatial resources. The purpose of the OGC API - Common - Part 2: Geospatial Data (API-GeoData) Standard is to provide a means of organizing these collections and to define operations for the discovery and selection of individual collections. OGC API-GeoData does not specify the nature of the geospatial data that make up a collection. Rather, the standard specifies a basic capability which should be applicable to any geospatial resource type. Additional OGC Web API standards extend this foundation to define resource-specific capabilities. This document defines the OGC API - Common - Part 2: Geospatial Data Standard. Suggested additions, changes and comments on this standard are welcome and encouraged. Such suggestions may be submitted as an issue on the OGC API - Common GitHub repositoryOGC API - Common GitHub repository.

DCTERMS.license

https://www.ogc.org/license

preconnect

https://fonts.gstatic.com

profile

http://dublincore.org/documents/2008/08/04/dc-html/

schema.DC

http://purl.org/dc/elements/1.1/

schema.DCTERMS

http://purl.org/dc/terms/