Public comment requested: OGC API - Common - Part 2: Geospatial Data
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.
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.
The OGC API - Common - Part 2 Standard does not specify the nature of the geospatial data that make up a collection. Rather, it provides a basic capability that should be applicable to any geospatial resource type. Additional OGC Web API standards extend this foundation to define resource-specific capabilities.
In parallel to this public review, the OGC Naming Authority is assessing the naming conventions to be used in the Requirements Modules defined in the candidate Standard. These conventions are important in the continued modularization of the OGC APIs, so careful review by experts is welcomed.
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template