You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When searching, if the fields parameter causes a field used in the sortby parameter to be excluded from the results, it seems that the server does not include the next link for pagination.
As an example using earth search, here is a request that excludes the field used for sorting:
{"type":"FeatureCollection","stac_version":"1.0.0","stac_extensions":[],"context":{"limit":1,"matched":19906000,"returned":1},"numberMatched":19906000,"numberReturned":1,"features":[{"stac_version":"1.0.0","bbox":[-100.889805,17.211145,-100.481581,18.083373],"geometry":{"coordinates":[[[-100.88980499375167,18.079807152724634],[-100.88127718540649,17.261739081673692],[-100.69294676442333,17.211145110345363],[-100.48158122778172,18.083373358751057],[-100.88980499375167,18.079807152724634]]],"type":"Polygon"},"id":"S2A_T14QLE_20190430T171850_L2A","collection":"sentinel-2-c1-l2a","type":"Feature","properties":{"datetime":"2019-04-30T17:28:58.911000Z","updated":"2024-10-02T18:34:48.587Z"}}],"links":[{"rel":"next","title":"Next page of Items","method":"POST","type":"application/geo+json","href":"https://earth-search.aws.element84.com/v1/search","merge":false,"body":{"sortby":[{"field":"properties.updated","direction":"desc"}],"fields":{"exclude":["links","assets"],"include":["properties.updated"]},"collections":["sentinel-2-c1-l2a"],"limit":1,"next":"2024-10-02T18:34:48.587Z"}},{"rel":"root","type":"application/json","href":"https://earth-search.aws.element84.com/v1"}]}
It is easy to workaround by making sure the sorting fields are included, but it seems like a hidden pitfall since a client may simply stop iterating with no indication that the search results are incomplete.
The text was updated successfully, but these errors were encountered:
When searching, if the
fields
parameter causes a field used in thesortby
parameter to be excluded from the results, it seems that the server does not include thenext
link for pagination.As an example using earth search, here is a request that excludes the field used for sorting:
which gives
If the
properties.updated
field is specificallyinclude
d, then thenext
link is included in the response.giving
It is easy to workaround by making sure the sorting fields are included, but it seems like a hidden pitfall since a client may simply stop iterating with no indication that the search results are incomplete.
The text was updated successfully, but these errors were encountered: