Collection Search: No separate endpoint

[m-mohr]

Collection Search is implemented on a separate endpoint (/collections-search) although it should simply extend the /collections endpoint. Thus, e.g. STAC Browser can't make use of it.

Also, there are two links in the landing page with relation type collections-search (GET and POST). This relation type is not defined in the Collection Search extension. It is already covered by the data relation type.

Please also note that the POST HTTP method is officially not defined in the collection search extension either (but it's also not forbidden to have it, just as a fyi.)

PS: Yes, this was not super clearly written out in the extension, I've clarified it in the spec.

[jonhealy1]

Hi. We do extend the /collections endpoint for GET collections search requests.

People have asked for POST /collections search but it interferes with the Transactions extension (POSTing a new collection). GET and POST /collections search has been added to the stac-fastapi parent library. To use POST /collections - for search - in our api, you have to disable the transaction extension.

/collections-search exists so that people can use POST on the collection search extension while having the transactions extension available at the same time. Note that the /collections-search route is disabled by default. The GET functionality was added just because. It can also just be used on the /collections endpoint which is set by default.

[jonhealy1]

stac-fastapi -> https://github.com/stac-utils/stac-fastapi/blob/main/stac_fastapi/extensions/stac_fastapi/extensions/core/collection_search/collection_search.py

[jonhealy1]

Reopen if needed. I think I fixed this @m-mohr

[m-mohr]

Thanks, I'll have a look!