pygeoapi abstract for Maps for the Web
pygeoapi - Towards a Python Web API for OGC Standard Maps
Recently, the proliferation of REST [1] as an architectural style as well as OpenAPI [2], W3C, and JSON has resulted in the OGC transforming its workflow in developing OGC API Features (OAFeat, formerly WFS 3) as a data access specification. OAFeat [3] implements the aforementioned standards to lower the barrier to implementation, especially for mass-market/non-geospatial developers. OAFeat is being actively developed in the open on GitHub. In addition, SpatioTemporal Asset Catalog (STAC)[6] is a community specification being developed in parallel to OAFeat. STAC intends to standardize how geospatial assets are exposed online and queried and is oriented for both static collections or dynamic catalogues of satellite imagery.
pygeoapi [7] is a reference server implementation compliant with the OGC API Features specification. Implemented in Python, pygeoapi supports many other OGC APIs via the Flask web framework and a fully integrated OpenAPI structure. Lightweight and easy to deploy, pygeoapi's architecture facilitates publishing datasets from multiple sources into a WFS 3.0 compliant server.
pygeoapi follows a clear separation structure with a view, provider/plugin and entry point module. The view approach allows for easy integration with other frameworks like Django. The provider abstracts connectivity to numerous data sources (CSV, SQLite3, GeoJSON, Elasticsearch) and provides extensibility to support additional formats.
This presentation will provide an overview of pygeoapi, current status and next steps as part of the evolution of the project.
- [1] https://en.wikipedia.org/wiki/Representational_state_transfer
- [2] https://openapis.org/
- [3] https://github.com/opengeospatial/ogcapi-features
- [4] https://github.com/opengeospatial/OGC-API-Tiles
- [5] https://github.com/opengeospatial/OGC-API-Maps
- [6] https://github.com/radiantearth/stac-spec
- [7] https://github.com/geopython/pygeoapi
TBD
