We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

OGC APIs and the evolution of OGC standards - an update

Formal Metadata

Title
OGC APIs and the evolution of OGC standards - an update
Title of Series
Number of Parts
8
Author
Contributors
License
CC Attribution - NonCommercial - NoDerivatives 4.0 International:
You are free to use, copy, distribute and transmit the work or content in unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
State-of-play of the OGC API development. The work has been progressing, to develop various OGC API standards that support a variety of resources. API technologies are in focus of standardization discussions within the geospatial community. Discussions and initiatives in the OGC reached a milestone in 2018: the release of the first of the OGC API standards. Since then work has been progressing to develop additional OGC API standards supporting a variety of resources. OGC members & staff investigated the potential value that OpenAPI could offer to geospatial services. Existing web service standards were effectively web APIs, modernizing their means of getting content to the web required a fairly fundamental change in the underlying design. The first OGC API standard approved & published was Part 1 of the OGC API – Features standard. The pattern “OGC API [resource]” was coined and led to initiatives to define and test draft OGC APIs for Coverages, Maps, Tiles, Styles & Processes. Outputs will support the evolution of a solid, common core and the advancement of a new generation of OGC standards leveraging modern Web API approaches