eoAPI with external STAC API?

[j08lue]

ESA EOEPCA wants to offer building blocks (to which eoapi-k8s contributes) in flexible configurations.

Some platforms may already have a STAC API and still want to use data access services (TiTiler, TiPg, TiTiler for multidimensional datasets) from eoAPI.

Or they only have little STAC data and do not need the full power of PgSTAC and rely on PyCSW's STAC API instead.

Should eoAPI-k8s offer a configuration / helm chart for "bring your own STAC API"?

[j08lue]

The configuration with an external STAC API would be quite different:

• PgSTAC would not be needed
• Instead of TiTiler-PgSTAC, platforms would need to use TiTiler-STACAPI
• Postgres db only needed if TiPg is activated

Some functionality would disappear, like dynamic mosaics based on STAC queries.

[vincentsarago]

I hear this request more and more and for now I'm not sure what's the best approach

Ideally, titiler-pgstac would be able to connect to any stac-api / stac-geoparquet but there are also custom parts specific to pgstac (search) which would be difficult to accommodate with non-pgstac backend

[kalxas]

Perhaps an option to install titiler-stacapi as part of the helm chart would be enough?