An OGC API to geospatial data

OSGeo Community Project FOSS4G 2021 Buenos Aires

This presentation available at

Table of contents

  • Project overview
  • Core capabilities
  • New features
  • Selected featured projects
  • Roadmap
  • Support

Project overview

Say hello to pygeoapi

Project Overview

  • Geospatial data Web API framework via OGC API
  • REST/JSON/OpenAPI/Swagger
  • OGC Compliant
  • OSGeo Community Project
  • International team (Canada, Netherlands, Greece, Italy, New Zealand, United States)
    • Numerous core contributors
    • 21000 upstream contributors (dependencies)

Technical Overview

  • Core abstract API; web framework agnostic (default Flask)
  • YAML configuration (metadata, dataset connections)
  • Automated OpenAPI document generation and data binding
  • Robust plugin framework (data connections, formats, processing)
  • Easy deployment (pip install, Docker, conda, UbuntuGIS)
  • Minimal core dependencies

Provider plugin framework

  • Features (Elasticsearch, CSV, GeoJSON, OGR, MongoDB)
  • Coverages (xarray, rasterio)
  • Tiles (MinIO, ZXY directory tree)
  • Records (Elasticsearch, TinyDB)
  • Implement your own!

Processing framework

  • Expose Python workflow as processes
  • Process manager support for job control (TinyDB)
  • Implement your own!

Implementing your own Plugin

  • Develop / propose / maintain as core plugin
  • Develop / maintain in your own repository

  • Lower the barrier to data search
  • HTML encoding is annotated as to facilitate search engines
  • Google dataset search locates pygeoapi datasets

Linked Data - JSON-LD

  • JSON-LD provided as additional representation
  • Default out of the box functionality for most pygeoapi resources / endpoints
  • Additional configuration


Numerous deployment options

  • PyPI
  • UbuntuGIS
  • Docker
  • Conda
  • FreeBSD

Core Capabilities


OGC API - Features

OGC API - Coverages

OGC API - Records

OGC API - Tiles

OGC API - Processes

OGC API - Environmental Data Retrieval

SpatioTemporal Asset Catalog (STAC)

HTML templating

New Features

  • STAC (June 2020)
  • OGC API - Coverages (August 2020)
  • OGC API - Tiles (September 2020)
  • Custom HTML templates (September 2020)
  • OGC API - Records (February 2021)
  • OGC API - Environmental Data Retrieval (March 2021)
  • Multilingual support (June 2021)
  • Config / OpenAPI schema validation (July 2021)
  • CQL (July 2021)

Selected recent projects

Meteorological Service of Canada GeoMet platform

  • OGC web services platform of Canadian weather, climate and water data
  • Realtime weather/hydrometric data
  • Numerical weather prediction
  • Hydrometric and Climate archives
  • Raster drilling

COVID-19 Demo Server

  • Official data about the situation in the world, The Netherlands and Italy since the beginning
  • Several collections with cases per regions, provinces and municipalities
  • Powerful use of the OGR provider with remote ArcGIS services and CSV resources from Github
  • More info with several possible queries here

US Internet of Water (Duke University)

Modern Water Data Infrastructure

USGS Water Resources

Canada Open Disaster Risk Reduction Platform (OpenDRR)

Open Source platform to support disaster risk management, starting with earthquake risk reduction

In development


EuroDataCube / EOXHub

Sprint Participation

  • Participation at numerous code sprints (OGC / OSGeo / Apache)
  • Feature development
  • Interoperability testing


OGC API Support

Standard Status
OGC API - Common Implementing
OGC API - Features Compliant/Reference Implementation
OGC API - Coverages Implementing
OGC API - Tiles Implementing
OGC API - Processes Implementing
OGC API - Records Implementing
OGC API - Environmental Data Retrieval Implementing
OGC API - Maps In Development
OGC API - Styles Planned


  • API Refactor
  • Transactions
  • Admin UI
  • enhancements
  • Content negotiation (e.g. Response as GeoPackage, GML,...)
  • OSGeoLive

Django app

  • Django application project
    • django_app folder next to and
    • with routes
    • with the binding of pygeoapi core API into the process of Request/Response
    • with the pygeoapi configuration path
  • Add --django option to the cli command to serve the usual Django server
  • Make the Django app reusable
  • Challenges:
    • Use DRF serializers
    • Inject generated OpenAPI document into drf-spectacular
    • Inject Jinja2 templates or use Django templates natively

GeoNode integration

  • Next generation GeoNode API GNIP-51
  • New v2 GeoNode REST API has been merged into master: GNIP-79
  • Discussion needed to determine how GeoNode could use pygeoapi as a backend:
    • Metadata (Resource base model -- similar to pycsw GeoNode integration)
    • Direct Elasticsearch integration
    • For OGC API Features, Maps, Styles, Tiles, Coverages (similar to GeoServer and QGIS Server)
    • How would auth work in this case?


Need support for WFS3.0???

GeoCat can help you

GeoComvos ltd

Geobeyond Srl


Thank you!

@tomkralidis @JMendesDeJesus @justb4 @pvgenuchten @tzotsos @alpha-beta-soup @francbartoli