Dynamically set STAC Catalog URL to allow a nested catalog solution to work

[james-hinton]

Background

We have a nested catalog solution for our STAC API, this has led to issues with third-party tools that are set up to deal with one catalog at a time.

Goals

I want to access nested STAC catalogs dynamically within a single titiler-stacapi deployment, without needing separate deployments for each catalog.

Partner and Stakeholders

We are part of the EO DataHub Project.

Team

Vincent has kindly said he can help me figure out a solution for this problem. As there is a way to dynamically set the URL of the catalog upon request which would allow us to work with nested catalogs.

• D @vincentsarago

Context and Links

So for example, we have our 'root' catalog here: https://test.eodatahub.org.uk/api/catalogue/stac/
But, we want to be enable our single deployment of titler-stacapi to be able to dynamically access a nested catalog that is here: https://test.eodatahub.org.uk/api/catalogue/stac/catalogs/supported-datasets/airbus, so that we can serve that data through WMTS.