OGC API - Features

Why?

Main reasons for using OGC API - Features.

Interoperable

Ensure that your application can read data from existing and new sources without changing how you communicate with them. Ensure that the data you share can be accessed by different clients, without having to share details of your implementation.

Based on Best Practices

This API is based on the technologies and vocabularies that make up the web today, such as REST, OpenAPI, JSON and HTML. This should ensure a smooth learning curve for any web developer, even if they are not familiar with GIS.

Supported on Existing Products

You can start using the OGC API - Features specification today, by tapping into one of the existing server or client implementations.

Overview

OGC API - Features provides access to collections of geospatial data.

Get collections

Lists the collections of data on the server that can be queried, 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 items

Requests all the data in a given collection. 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.
Get feature

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'.

If you are interested in finding out how-to use other coordinate reference systems, you can read this . You can find here links for different parts of the spec and explore it using Swagger .

See it In Action

This is a list of datasets, served by implementations of OGC API - Features. Please get in touch , if you would like to add your dataset to the list.

Vineyards in Rhineland-Palatinate, Germany

Powered by Ldproxy

Have you ever wondered where the wine that you are drinking comes from? If the wine comes from the wine-growing regions Mosel, Nahe, Rheinhessen, Pfalz, Ahr, or Mittelrhein you can find this information in this API.

Portuguese Points of Interest

Powered by Pygeoapi

Portuguese Points of Interest obtained from OpenStreetMap. Dataset includes Madeira and Azores islands. Uses GeoPackage backend via OGR provider.

Zaatari Refugee Camp مخيم الزعتري

Powered by CubeWerx

Zaatari is a refugee camp in Jordan, located 10 kilometres east of Mafraq, which has gradually evolved into a permanent settlement; it is the world’s largest camp for Syrian refugees.

OS NGD API – Features

Powered by The OS Data Hub

Easy online access to the OS National Geographic Database, providing a rich and consistent information about the real world.

Ottawa OpenStreetMap roads

Powered by GNOSIS

OpenStreetMap (OSM) is a free, open geographic database updated and maintained by a community of volunteers via open collaboration. This dataset is an OpenStreetMap extract that contains the roads of Ottawa, Canada.

Geographic Objects from the National Cartographic System of Spain

Powered by pygeoapi

Includes collections such as Hydrography, Transport Networks, CartoCiudad postal addresses and the Information System on Land Occupation of Spain 2014 (SIOSE).

Aids to Navigation - List of Lights, Buoys and Fog Signals

Powered by pygeoapi

The Aids to Navigation feature collection contains updated information regarding maritime visual and sound signalling existing on the coast and in the interior of ports in Portugal.

Key Register Large-scale Topography (BGT), Netherlands

Powered by GoKoala

Are you interested in large-scale topographic data of the Netherlands? In the Key Register Large-scale Topography (BGT) you can find all about building types, address labels, road segments (such as cycle paths, lanes, driveways, and shoulders), as well as topographic boundaries (such as fences and walls), terrain types, and water. You can access this data directly or use the landing page.

Use it

Do you want to start using OGC API - Features? Before starting to implement the spec, please take a look at the existing implementations.

Servers by Technology
Java	Ldproxy ^*	/
	Geoserver	/
	Deegree ^*	/
Python	pygeoapi ^*	/
Python	GeoPortal
JavaScript	Sofp	/
C/C++	QGIS Server	/
C/C++	GNOSIS Map Server ^*

Clients by Technology
Python	OWSLib	/
Python	Pygdal	Check GDAL's documentation .
JavaScript	ogcapi-js	/
C/C++	GDAL	/
Integration framework	Apache Camel	/

^* Certified compliant product.

Who is behind OGC API - Features?

OGC API Features is developed through a member-driven consensus process, which creates royalty free, publicly available, open geospatial Standards. The Open Geospatial Consortium (OGC) is the organisation which drives this process. It is supported by an active community of members, with involvement from a large range of organizations, as well as smaller ones. Join OGC today!

The logos above are a small subset of all OGC members. They are either strategic/principal members, and/or organisations who implement products certified for OGC API - Features.

Get Started

Here is something to get you started.

Complete an online training

If you are familiar with web services and APIs, and want to have an overview of the OGC API - Features Standard, this training is for you.
Follow a tutorial

Implement a complete pipeline to make your data available with OGC API - Features, using a stack of free and open source software. A video version is available here.
Get
Involved!

Get Involved

Tell us what’s working well, what you want to see added or improved, and find out about new updates.

Stack Overflow

Engage with your peers and ask questions about OGC API - Features using the tag 'OGC API - Features'

Discord

Chat with other OGC API - Features users in the OGC Community channel.

GitHub

Found a bug, or want to give us constructive feedback?