A search endpoint provides the ability to query
STAC Collections
objects across collections.
It retrieves a group of Collection objects that match the provided parameters and provides them as
the GET /collections endpoint does.
The Collection Search endpoint by default doesn't provide any query parameters to filter and all additional behavior will be defined in Extensions. These extensions can be composed by an implementer to cover only the set of functionality the implementer requires.
This extension is based on OGC API - Common - Part 2: Geospatial Data and aligned to OGC API - Records - Part 1: Local Resource Catalogue and selectively implements a subset of their "requirements classes".
All functionality in OGC API - Records - Part 1: Local Resource Catalogue is only defined for the GET method (i.e. GET /collections).
Note: STAC may add behavior for POST /collections in the future, but due to a potential conflict
with the Transaction Extension, specific rules for content negotiation might be required.
Pagination for collections works exactly as it defined for Collections in general. See Collection Pagination for details.
http://www.opengis.net/spec/ogcapi-common-2/1.0/conf/simple-queryA basic set of query parameters MUST be implemented. These are aligned with the corresponding parameters in STAC API - Features and OGC API - Records:
bbox (intersection of the given bbox with any of the spatial extent provided in a STAC Collection at extent.spatial.bbox)datetime (intersection of the given datetime with any of the temporal extent provided in a STAC Collection at extent.temporal.interval)limithttps://api.stacspec.org/v1.0.0-rc.1/collection-search#free-textA basic free-text search parameter q based on OGC API - Records and the
STAC API - Free Text Search Extension can be added.
The specific set of text fields of a Collection to which the parameter is applied is left to the discretion of the implementation, but a recommendation is to at least consider title, description and keywords.
The search works case-insensitive and spaces have no special meaning. Any of the search terms must be present in the set of text fields (OR operaror).
GET requests, all search terms must be separated by a comma. For example, if you want to search for "Earth Observation" or "EO", your query parameter should be as follows: q=EO,Earth Observation.POST requests, an array of search terms must be provided, for example: {"q": ["EO", "Earth Observation"]}.https://api.stacspec.org/v1.0.0-rc.1/collection-search#filterThe filter extension for CQL support can be implemented, too.
See https://github.com/stac-api-extensions/filter for details.
It works as it does for Items, except that the queryables link for Collection Search is located in the response of GET /collections (property links).
The path/endpoint for Collection Search queryables can be freely chosen, but SHOULD NOT conflict with GET /queryables.
https://api.stacspec.org/v1.0.0-rc.1/collection-search#queryThe query extension for STACQL support can be implemented, too. It works as it does for Items. See https://github.com/stac-api-extensions/query for details.
https://api.stacspec.org/v1.0.0-rc.1/collection-search#sortThe sort extension can be implemented, too. It works as it does for Items. See https://github.com/stac-api-extensions/sort for details.
https://api.stacspec.org/v1.0.0-rc.1/collection-search#fieldsThe fields extension can be implemented, too. It works as it does for Items. See https://github.com/stac-api-extensions/fields for details.