Skip to content
An open standard for querying geospatial information on the web.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
core Fixed typo Oct 29, 2019
extensions add link to abstract spec Nov 25, 2019
placeholder-additional-conformance-class The minItems and maxItems are for validating arrays (not items) Mar 4, 2018
template req class URIs -> conf class URIs Jul 8, 2019
uml SWG name change, part 2 Sep 8, 2019
.gitignore Update .gitignore Dec 12, 2017
CHARTER.adoc add update date Dec 9, 2019 SWG name change, part 2 Sep 8, 2019
LICENSE add license Oct 10, 2017 Made the link to the actual spec more prominent Oct 22, 2019
asciidoctor.json Updates after submission of part 1 Jul 12, 2019 Updating the GeoServer entry, there's been some progress in the meantime Nov 21, 2019 WFS 3.0 -> OGC API - Features, first edits Apr 25, 2019

OGC API - Features

This GitHub repository contains OGC's standard for querying geospatial information on the web, "OGC API - Features". The latest version of the specification can be found at

OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. OpenAPI is used to define the reusable API building blocks with responses in JSON and HTML.

The OGC API family of standards is organized by resource type. OGC API Features specifies the fundamental API building blocks for interacting with features. The spatial data community uses the term 'feature' for things in the real world that are of interest.

If you are unfamiliar with the term 'feature', the explanations on Spatial Things, Features and Geometry in the W3C/OGC Spatial Data on the Web Best Practice document provide more detail.


OGC API Features provides access to collections of geospatial data.

GET /collections

Lists the collections of data on the server that can be queried (section 7.13), and each describes basic information about the geospatial data collection, like its id and description, as well as the spatial and temporal extents of all the data contained.

GET /collections/buildings/items?bbox=160.6,-55.95,-170,-25.89

Requests all the data in the collection "buildings" that is in the New Zealand economic zone. The response format (typically HTML or a GeoJSON feature collection, but GML is supported, too, and extensions can easily supply others) is determined using HTTP content negotiation.

Data is returned in pageable chunks, with each response containing a next link as many collections are quite large. The core specification supports a few basic filters, in addition to the bbox filter above, with extensions providing more advanced options (section 7.15).

GET /collections/{collectionId}/items/{featureId}

Returns a single 'feature' - something in the real-world (a building, a stream, a county, etc.) that typically is described by a geometry plus other properties. This provides a stable, canonical URL to link to the 'thing' (section 7.16).

Using the standard

The standard is on the OGC website:

A PDF version is available, too.

Those who want to just see the endpoints and responses can explore examples of OpenAPI definitions.

The reference version of the OpenAPI components and XML schemas are published in the OGC schema repository.

Several implementations of the draft standard exist:


Join the mailing list or chat at

Most all work on the specification takes place in GitHub issues, so browse there to get a good idea of what is happening, as well as past decisions.

Additional parts of OGC API - Features

The OGC Features API SWG has identified the following extensions to Part 1 (Core) as the highest priority:

A joint sprint with STAC and the OGC API Catalogues SWG to advance richer query/filter capabilities is planned for November 5-7, 2019, in Arlington, VA.

Additional information

Open issues for Part 1 (Core) are documented in a GitHub project.

In parallel, Part 1 (Core) has also be submitted to ISO/TC 211 and is in the Draft International Standard (DIS) ballot.

Open issues for Part 2 (CRS) are documented in another GitHub project.

Additional links:


The contributor understands that any contributions, if accepted by the OGC Membership and ISO/TC 211, shall be incorporated into OGC and ISO/TC 211 OGC API standards documents and that all copyright and intellectual property shall be vested to the OGC.

The Features API Standards Working Group (SWG) is the group at OGC responsible for the stewardship of the standard, but is working to do as much work in public as possible.

You can’t perform that action at this time.