OGC API – Common – Part 2: Geospatial Data provides a common connection between the API landing page (defined by Part 1) and resource-specific details.
The Open Geospatial Consortium (OGC) is seeking public comment on the OGC API – Common – Part 2: Geospatial Data Candidate Standard. The purpose of OGC API – Common – Part 2: Geospatial Data is to provide a common connection between the API landing page and resource-specific details. Comments are due by January 5, 2022.
OGC APIs are OGC’s Building Blocks for Location, and are ushering in a new age for location information on the web by enabling a much simpler, consistent, and familiar way to share and access location information. Through the OGC APIs, the OGC community is improving how location information can be integrated: by any developer, with any other type of information, and into any type of application.
OGC API – Common serves as a foundation upon which all OGC APIs can be built. OGC API – Common – Part 1: Core defines the resources and access mechanisms which are useful for a client seeking to understand the offerings and capabilities of an API. OGC API – Common – Part 2: Geospatial Data builds on Part 1 by providing a common connection between the API landing page and geospatial data collections.
Geospatial data is rarely considered as a single entity. Feature Collections, Coverages, Data Sets, etc. are all aggregations of Spatial or Temporal ‘Things’. 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 Standard, then, is to provide a means of organizing these aggregate collections and to define operations for the discovery and selection of individual collections.
(more…)
OGC Seeks Public Comment on OGC API – Common – Part 2: Geospatial Data
Wednesday, December 8th, 2021OGC API – Common – Part 2: Geospatial Data provides a common connection between the API landing page (defined by Part 1) and resource-specific details.
The Open Geospatial Consortium (OGC) is seeking public comment on the OGC API – Common – Part 2: Geospatial Data Candidate Standard. The purpose of OGC API – Common – Part 2: Geospatial Data is to provide a common connection between the API landing page and resource-specific details. Comments are due by January 5, 2022.
OGC APIs are OGC’s Building Blocks for Location, and are ushering in a new age for location information on the web by enabling a much simpler, consistent, and familiar way to share and access location information. Through the OGC APIs, the OGC community is improving how location information can be integrated: by any developer, with any other type of information, and into any type of application.
OGC API – Common serves as a foundation upon which all OGC APIs can be built. OGC API – Common – Part 1: Core defines the resources and access mechanisms which are useful for a client seeking to understand the offerings and capabilities of an API. OGC API – Common – Part 2: Geospatial Data builds on Part 1 by providing a common connection between the API landing page and geospatial data collections.
Geospatial data is rarely considered as a single entity. Feature Collections, Coverages, Data Sets, etc. are all aggregations of Spatial or Temporal ‘Things’. 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 Standard, then, is to provide a means of organizing these aggregate collections and to define operations for the discovery and selection of individual collections.
(more…)
No Comments »