-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for STAC API collection-search extension #249
Comments
Yes, it would be great to support it in STAC Browser. There are two caveats:
|
Understood. For point (1), I shared a temporary endpoint by email... I understand the problem (2). |
We are interested in the collection-search too. I think the actual STAC browser is really missing a way to find what the user needs when there are more collections. The item search is not the same because it returns too many results. Let's say I want to see all DEM collections available in a catalog, I don't want to end up with a list of thousands of items, I would just want to end up in a smaller list of all DEM collections and then I can myself go deeper in exploring the items of the collections I'm interested into. |
@chiarch84 Could you provide an API implementation? Without an API implementation of said extension there won't be an implementation in STAC Browser, of course. |
Well, we can add an endpoint to our APIs following the basics specs defined in https://github.com/stac-api-extensions/collection-search So we could have the following inupt parameters: But then I don't know how you would be able to test it since our APIs are behind authentication. You might register to our website maybe. |
@chiarch84 There's an implementation of Collection Search (including free text search) in the collection-search branch (PR: #317). It would be great if you could test it against your implementation (please also note the recent changes in the collection search extension). |
Sorry for the late answer @m-mohr |
@m-mohr, is it foreseen to support the STAC collection-search extension proposed at https://github.com/stac-api-extensions/collection-search and in particular the retrieval of collection search parameters from a Queryables response advertised via rel=".../queryables" in the /collections response ? We are eager to test this with our latest server implementation.
The text was updated successfully, but these errors were encountered: