Closed emmanuelmathot closed 1 year ago
I think merge
is preferred, since it's a bit easier to handle on the client side -- the client usually only needs to add the extra paging parameter (e.g., next=xkjlajdsfjaskdf
) instead of reconstructing the entire query.
For the Item Search response from /search, there is no requirement for a self
link, so there are no formal requirements for it. Planetary Computer only returns the base url (/search
) without the merge and body parameters. OAFeat does require it for /items, but that endpoint only supports GET.
The easiest and most correct way would probably be to also add merge:true
, so it actually means "make the same request"
{
"rel": "self",
"href": "https://stac-api.example.com/search",
"type": "application/geo+json",
"method": "POST",
"merge": true
}
In case of a query with POST method and body parameters (e.g. OGC API Feature and Item-search).
What is the recommendation for the
self
andnext
links?Complete query:
or simplified implying the reuse of previous parameters: