The OGC API family of standards are being developed to make it easy for anyone to provide geospatial data to the web. These standards build upon the legacy of the OGC Web Service standards (WMS, WFS, WCS, WPS, etc.), but define resource-centric APIs that take advantage of modern web development practices. This web page provides information on these standards in a consolidated location.
These standards are being constructed as "building blocks" that can be used to assemble novel APIs for web access to geospatial content. The building blocks are defined not only by the requirements of the specific standards, but also through interoperability prototyping and testing in OGC's Innovation Program.
The OGC API Roadmap highlights the current and planned standards efforts as well as related extensions to those standards and Innovation Program and other projects influencing and refining the process of standardization.
For more information on the OGC API standards, please contact Scott Simmons, Head of the OGC Standards Program.
The executable test suite for the OGC API - Features - Part 1: Core (OGC 17-069r3) is now available in the OGC Validation beta environment.
We require three early implementations to move the test to production. So far we have one passing the test: ldproxy
The data is available here: https://services.interactive-instruments.de/t15/daraa
Your implementation will then appear in the OGC database as an official early implementation and we will waive the license fee for the first year.
If you have any issues, please report them directly to the GitHub project page: https://github.com/opengeospatial/ets-ogcapi-features10/issues
Thank you and happy testing!
OGC continues to use special events, hackathons, and sprints to validate the OGC API draft candidate standards as those standards evolve. By including the broadest possible selection of stakeholders, OGC can be confident that when the standards are published, those standards have already withstood testing and suitability evaluation.
The following repositories contain the work-in-progress for OGC API standards. These efforts are at different levels of maturity, but anyone is free to browse the work and submit or comment upon issues.
OGC API - Features: Part 1 - Core is already publicly available. Part 2 - Coordinate Reference Systems by Reference will soon be released for public review.
OGC API - Common provides those elements shared by most or all of the OGC API standards to ensure consistency across the family. The candidate standard will soon be released for public review.
OGC API - Maps offers a modern approach to the OGC Web Map Service (WMS) standard for provision map and raster content.
OGC API - Records updates OGC’s Catalog Services for the Web by building on the simple access to content in OGC API - Features.
OGC API - Processes allows for processing tools to be called and combined from many sources and applied to data in other OGC API resources though a simple API.
OGC API - Coverages allows discovery, visualization and query of complex raster stacks and data cubes.
OGC API - Tiles provides extended functionality to other OGC API standards to deliver tiled data, such as Map Tiles.
The OGC Innovation Program provides a world-recognized process for users of geospatial technology to collaborate and share the advancement of technologies for future enterprise architectures.
If you have an idea for an initiative or simply have a question or comment, contact Ingo Simonis, Head of the OGC Innovation Program.
The OGC API standards rely heavily upon fundamental concepts expressed in OGC White Papers and research and testing performed in Innovation Program activities and documented in Engineering Reports. OGC members are also specifying best practices for the use of web APIs and often share that guidance. The documents below provide some background to OGC API efforts.
While the OGC API standards are being developed in concert around common core elements, some older OGC web service standards have been described using OpenAPI. Examples of these legacy enhancements are found below.