Implement STAC API - Children Specification

[m-mohr]

So don't do the merging of catalogs and collections if implemented.

Needs an implementation first.

[chiarch84]

I'm not sure if this is the correct place to post this, but it seemed to me to be the same issue.

I've got a STATIC STAC Browser up and running containing sub-catalogs, collections and items.
In the past months we've been storing all these jsons in Elasticsearch and are now returning them through STAC APIs.
We would like now to get rid of the STATIC catalog and attach the STAC browser directly to the APIs in order to have a dynamic catalogue.

We've got a big doubt though: where are we supposed to return the sub-catalogs??? I couldn't find an example of STAC browser based on APIs that was containg sub-catalogs.
Should I return sub-catalogs just as if they were collections? What API methos should I use to return collections in a sub-catalog?

Here I reported an image with the possible methods to be called in STAC APIs but I don't find anything concerning sub-catalogs.
In our case for example we have the root catalog containing 1 sub-catalog for eache INSPIRE Theme but in this list I don't find a way to return all the collections available in a specific subcatalog.

I would look for something like
/{subcatalog_id}/collections
But I dont' see it.

[m-mohr]

This sounds more like a general STAC question and is unrelated to STAC Browser. I'd recommend to post this question in Gitter, participate in the STAC meetings or work with a consultant to get your general architectural questions solved.

In short: Catalogs are not really a thing in APIs, you'd use Collections and Items only. You can also expose catalogs though child links in APIs, but you may loose the advantages of an API for them.

[chiarch84]

Thanks for the short hint. So you confirm me that there is no way to have a Dynamic STAC Browser with sub-catalogs? There can only be the root catalog with a long list of all available collections.

I was reading this https://github.com/radiantearth/stac-spec/blob/master/best-practices.md#dynamic-catalog-layout link concerning Best practices for dynamic cataloging and I wanted to follow the suggestions of creating different ways of browsing the catalog through sub-catalogs, but I didn't understand how this was supposed to be implemented if a /catalog API doesn't exist.
Sorry for posting it in the wrong place. I posted the issue directly on the STAC API spec project .

[m-mohr]

Moved to later due to the lack of implementations.