Fork me on GitHub

Build interoperable geospatial solutions with OGC Standards

✓ Providing a consistent way for different systems to interoperate and share geospatial data.
✓ Enabling applications to more easily access and use geospatial data from a wide variety of sources.
✓ Made by developers, for developers.
LearnGet Started
curl -X 'GET' \
'https://demo.pygeoapi.io/master/collections/lakes/items?limit=10&skipGeometry=false&offset=0' \
-H 'accept: application/geo+json'

Testimonials

What Developers Say

Voices from the community on building with OGC Standards.

"So these OGC codesprints put the potential users together, so that we all try and make these APIs palatable for all. We won't make everybody happy, but we can try to make nobody hate the APIs."

— Ivan Sanchez Ortega, Freelance GIS+JS developer, OSGeo charter member

"Exciting times for international weather/climate/water data exchange, using open Standards and open source reference implementations."

— Tom Kralidis, OSGeo Board Member, key contributor of FOSS4G projects

"Using industry tools, you can take these specifications (OGC APIs) as is and easily generate service and client implementations…"

— Steve McDaniel, Software Scientist at Hexagon

"The next generation of OGC API Standards make it easy for data publishers to create modern, developer friendly APIs to access geospatial data…"

— Michael Gordon, Strategic Product Manager at Ordnance Survey

"The new OGC-APIs allow you to access the features of the SDI datasets of Spain (hydrography, land use and cover, transport networks…) in a simple and friendly way…"

— Aure Aragón Velasco, Technical Land Surveyor, Spanish SDI (IDEE IGN/CNIG)

"OGC Standards underpin the transfer of geospatial datasets, and the OGC APIs reflect the use of cloud-hosted computing alongside being easier to understand…"

— Samantha Lavender, EO Scientist and Director at Pixalytics

"In terms of data handling, the OGC API is easier because we can use it as if it were a REST API. It increases interoperability between GIS and non-GIS software. It allows for better data load management."

— João Filipe Gaspar, GIS Developer

IS

Get Started

Each Standard addresses a specific type of geospatial data or associated resources. Interfaces define how services can access the data, while encodings define the structure and organisation of data formats and messaging protocols. Browse the list bellow to find the one that matches your needs.

Interfaces

Interface Standards provide rules that determine the operations in a server–client architecture. For instance, web mapping applications, orWeb GIS, fit into this pattern, where an interface is used to request maps from a map service provider.

Published

OGC API – Tiles

Interface for tiles of geospatial information (e.g. vector data, maps, or coverages).

Published

OGC API – Features

Interface for feature data.

Published

OGC SensorThings API

Interface for spatially enabled IoT devices, data, and applications.

Published

OGC API – Maps

Interface for maps, customized using parameters (dimensions, background, CRS).

Published

OGC API – EDR

Interface for sampling data about the natural or built environment using a spatio-temporal query pattern.

Published

OGC API – Moving Features

Interface to access representations of Moving Features.

Published

OGC API – Processes

Interface for wrapping computational tasks into executable processes. Processes include well-defined algorithms that ingest vector and/or coverage data to produce new datasets.

Published

OGC API – Records

Interface for global grid systems and their associated data.

Published

OGC API – DGGS

Interface for global grid systems and their associated data.

Published

OGC API – Connected Systems

Interface for interacting with connected systems (sensors, drones, robots) and associated resources.

OGC API – Styles

Interface for styles used to render geospatial data.

OGC API – 3D GeoVolumes

Interface for 3D geospatial data.

OGC API – Coverages

Interface for accessing homogeneous collections of values located in space/time — a satellite image is an example.

OGC API – Routes

Interface to request routes independent of the underlying routing data set, engine, or algorithm.

OGC API – Joins

Interface to join data from input files with tabular data from other sources.

OWS

Looking for the previous generation of OGC Web Services (e.g.: WFS, WMTS, WMS)?

Encodings

Published

JSON-FG

OGC Features and Geometries JSON extends GeoJSON to overcome some of its limitations.

Published

Cloud Optimized GeoTIFF

For imagery and grid coverage data on the web — backwards compatible with GeoTIFF.

Published

GeoPackage

Store different types of geospatial information (vector data, attributes, metadata, styles) in a single container.

Published

CoverageJSON

Simple, efficient, machine- and human-readable JSON for publishing spatio-temporal data to the Web.

GeoParquet

Columnar geospatial format based on Apache Parquet, enabling interoperability between cloud data warehouses.

Learn

Level Up Your OGC Knowledge

OGC API Workshop

This workshop provides a combination of concepts, presentations, and exercises on OGC APIs in support of discovery, access, visualization, and processing — in support of FAIR data principles.

Visit workshop →

Location Innovation Academy

This learning platform offers different courses, mostly focused on Spatial Data Infrastructures.

Visit academy →

More Resources

You May Also Want to Check

Definitions Server

A web-accessible source of information about things ("Concepts") the OGC defines or that communities ask the OGC to host, such as technical terms from application schemas.

Explore →

Location Building Blocks

Maybe you don't need a complete OGC API, or you need to mix multiple OGC APIs. OGC APIs are developed in discrete building blocks you can mix & match to spatially enable your existing APIs.

Explore →

Compliance & Certification

The OGC Compliance program provides tools to test your implementation and confirm it's compliant to the Standard. Take your application further by applying for a compliance certification.

Explore →

Community

Join the Conversation

Connect with the developers building the future of open geospatial standards.

Code Sprints

Collaborative and inclusive events supporting the development of open geospatial Standards, and projects that implement those Standards.

Learn more →

Dev.to

#OGCAPI related content in a constructive and inclusive social network for software developers.

Read posts →

Discord

Chat with other developers and take an active part in the code sprints in the OGC Community channel.

Join server →

Blogs

A collection of community blog posts from developers working with OGC Standards.

Read blogs →

Agora

Ask questions and interact with other developers in the "Developers" space of Agora.

Visit Agora →

Who is behind the OGC Standards?

OGC Standards are 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!