pygeoapi is an OGC API Reference Implementation. Implemented in Python, pygeoapi supports numerous OGC APIs via a core agnostic API, different web frameworks (Flask, Starlette, Django) and a fully integrated OpenAPI capability. Lightweight, easy to deploy and cloud-ready, pygeoapi's architecture facilitates publishing datasets and processes from multiple sources. The project also provides an extensible plugin framework, enabling developers to implement custom data adapters, filters and processes to meet their specific requirements and workflows. pygeoapi also supports the STAC specification in support of static data publishing.

pygeoapi has a significant install base around the world, with numerous projects in academia, government and industry deployments. The project is also an OGC API Reference Implementation, lowering the barrier to publishing geospatial data for all users.

This presentation will provide an update on the current status, latest developments in the project, including new core features and plugins. In addition, the presentation will highlight key projects using pygeoapi for geospatial data discovery, access and visualization.

SDIs have gone a long way since the times of OGC Web Services (e.g.: WMS, WFS, etc). Today, they are supported by a breed of modern OGC standards (e.g.: OGCAPI), which embrace mainstream web technologies, such as REST, JSON and OpenAPI. These standards are already implemented by a variety of servers and clients, including FOSS. How did this technological modernization impact the experience of end users?
In this talk, we’ll share the experience from a research project, which included a variety of stakeholders that had the requirement of having to produce and share geospatial data among them. An SDI was assembled, using a mix of modern and more established standards, implemented through a stack of FOSS4G software.
We would like to discuss some lessons learned from this project, including the need to identify strategies that can foster the adoption of the SDI by the stakeholders. As Brenda Laurel, an independent scholar, stated: “Design isn’t finished until somebody is using it.”

Tiled maps are the backbone of most web applications that show geospatial information. Before OGC API - Tiles was approved, last year, there was not really an interoperable way of creating these maps using a resource oriented architecture and JSON encodings.
OGC API - Tiles puts some formality to what people have been doing for years, with ‘xyz’ tilesets, but it also enables the clients to create a better user experience, by providing metadata, such as title, description or available zoom levels.
In this talk we’ll provide an overview of this standard, and discuss its advantages, when compared to other standards/specifications, like WMTS or TileJSON. We’ll illustrate the benefits of interoperability, with an example that uses FOSS4G software implementing OGC API - Tiles.
Finally, we’ll point out some resources, available to anyone who wishes to develop and validate an OGC API - Tiles implementation.

OGC APIs are a family of modern standards, which bring interoperability to anyone who wants to share geospatial data, using mainstream web technologies (e.g: REST, JSON, HTML). Some of these APIs come to replace and extend the legacy OGC Web Services (OWS), like WFS or WMS.
In this talk, we’ll highlight the state of OGC APIs and their current roadmap. We’ll also look at the adoption of these APIs within OSGeo projects and discuss compliance and certification. Finally, we will point out some resources, available to anyone who wants to develop and validate OGC API implementations.