Tom Kralidis
Tom Kralidis
To add, it would be valuable to have pygeoapi.models.pydantic that covers the try/except in one place and have the rest of code import from pygeoapi.models.pydantic
Closing given https://github.com/geopython/pygeoapi/issues/1664#issuecomment-2192417748
@gespau thanks for opening this issue. Can you provide some details on the requirement to login to any of the containers? Are there workflows or steps that we should consider...
PR updated. Note that upgrading `Dockerfile` to `python:3.10-slim-buster` and adding `apt upgrade` passes the trivy image scan.
Thanks @ricardogsilva. For a broader effort, the best place for this work to take place would be in OSGeo. In the [OSGeo Standards Committee](https://wiki.osgeo.org/wiki/Standards_Committee) we have often discussed the need...
Bumping this issue for status (cc @ricardogsilva)
2025-07-01 - Zarr: @tomkralidis - GeoParquet: @justb4
Keeping mind the pygeoapi focus on OGC API standards, note that Pub/Sub support is coming via the forthcoming OGC API - Pub/Sub efforts. This will essentially allow pygeoapi to publish/subscribe...
Sure. I don't have an overview/picture of the workflow, but in OGC API - Pub/Sub, pygeoapi would basically publish messages to a Pub/Sub broker (MQTT, AMQP, WebSockets, Kafka, etc.) that...
2025-11-05 - validate documentation for options on proxying 9001/3000.