This extension is intended to augment the core ItemCollection object when the ItemCollection is the result of a search, for example, from calling the /search API endpoint.
This fragment may be bound to either or both of STAC API - Item Search (/search endpoint) or STAC API - Features (/collections/{collectionId}/items endpoint) by advertising the relevant conformance class.
Note: OGC API Features - Part 1 has its own way returning numberMatched and numberReturned at the top level, instead of in a context object. We are hoping to align, but until then, it is required to implement both when implementing STAC Features.
The default sort of query results should be stable, but may not be depending on the data store's sorting performance. It is recommended that the Sort API Extension be implemented in conjunction with this extension and that fields conducive to stable sorting have sorting enabled over them.
limit - The maximum number of results requested explicitly, the default limit used by the service implementation if no parameter was provided, or the maximum limit used by the service implementation if the limit parameter was larger. null if no limit was placed on the query that retrieved these results, which should be a rare case in practice.
{
"type": "FeatureCollection",
"features": [ ],
"context": {
"returned": 9,
"limit": 10,
"matched": 1092873
}
}
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4