GNIP-80: Integration of new OGC APIs

[francbartoli]

GNIP - Integration of new OGC APIs

Overview

The new generation of OGC APIs has landed, pygeoapi is already a reference implementation for some of them and its development is following as they are progressing. It is worth to leverage it as a backend component in GeoNode to start supporting them natively.

Proposed By

francbartoli - Francesco Bartoli

Assigned to Release

This proposal is for GeoNode .

State

• [x] Under Discussion
• [ ] In Progress
• [ ] Completed
• [ ] Rejected
• [ ] Deferred

Motivation

Details about the motivations. Why people should accept this proposal. What are the benefits compared to the current situation.

Proposal

Integration workplan

pygeoapi

• Add support for Django on top of core API ticket 586
  • use Django templates natively or still Jinja2 ones for HTML output?
  • use DRF and its tools/extensions (i.e.: drf-spectacular, etc.) for serialization of responses and the rendering of OpenAPI document

GeoNode

• Add pygeoapi as a backend component ticket 6706
  • Add pygeoapi routes next to the new v2 GeoNode REST API. New /v3 URLs location for OGC APIs machinery?
  • Possible approaches:
  • Metadata similar to pycsw integration with ResourceBase model
  • Direct Elasticsearch integration
  • For OGC API Features, Maps, Styles, Tiles, Coverages similar to GeoServer and QGIS Server
  • What about auth work in this case?

    Backwards Compatibility

Declare its Backwards Compatibility.

Future evolution

Explain which could be future evolutions.

Feedback

Update this section with relevant feedbacks, if any.

Voting

Project Steering Committee:

• Alessio Fabiani:
• Francesco Bartoli:
• Giovanni Allegri:
• Simone Dalmasso:
• Toni Schoenbuchner:
• Florian Hoedt: +1

Links

Remove unused links below.

• GitHub Discussion
• Linked Issue

[ridoo]

@giohappy are there any plans how OGC APIs will be handled in the future? Newer Geoserver supports them already. I guess this may also overlap with MapStore development.. for sure, g'old OGC XML based APIs will not disappear tomorrow. But maybe you have some ideas to share (perhaps integration vie remote services).

/cc @gannebamm /cc @matthesrieke

[giohappy]

@ridoo we haven't made any plan yet. We were waiting for the OGC API to stabilize, mainly as a standard.

Features, Tiles, and Processes standards are ready, and Geoserver has the OGC API Features community module ready (Tiles is almost ready, Processes yet to be done). I'd prefer to wait for it to become an official Extension though, which would require a bit of more work (==money).