Hi,

Thanks for your question. Unfortunately, there is no inbuilt filtering functionality based on the overlap of your AOI with Sentinel-2 tiles. To quote from the documentation, the way the APIs have been designed and implemented means that the complexity of “tiles” is not accounted for when filtering out data such as Sentinel-2.

Even though satellite imagery data are often distributed in "tiles", we do not want users to be limited to these. Tiles are an artificially introduced entity to make data distribution easier to handle. However, users should not have to care about whether their AOI is on one tile or another, or perhaps on the border of two tiles. This is why Sentinel Hub API hides this complexity and simply makes the data available over chosen area of interest and temporal period of interest. Tiles are therefore automatically stitched together based on defined parameters (AOI, time period, cloud coverage, priority, etc., depending on the data type).

That said, if this is still something you wish to implement, you can extract the Sentinel-2 tile extent from a Catalog API request output, you could then calculate the overlap percentage based on this and your AOI using Python (or your language of choice). You could then tailor your Processing API requests to very specific time intervals so you only use the tiles that you are interested in. 

Alternatively, depending on your final output, if it boils down to a statistic, you could use Statistical API that does include an aggregationInterval parameter.

Thank you for the fast reply.

To confirm: we would not be able to use the tile IDs from the catalogue call to filter the processing call. Instead we would have to use the exact acquisition timestamps in our filter?

And on a side note: the python SDK does not expose all information provided by the catalogue API directly it seems (e.g. the cloud cover cannot be extracted directly from the CatalogSearchIterator). Is that a design choice or should we raise a feature request on that?

PS.: the textboxes on this Forum are very hard to use given that white-on-white is the default colour and the formatting is hard to apply

Yes exactly, the only workaround is to be highly specific with your time range. However, unless you are using a ORBIT or TILE, the evalscript will only be considering one sample anyway. By default, the mostRecent.

To filter out cloud cover for Sentinel-2 L2A you can use:

search_iterator = catalog.search(

  DataCollection.SENTINEL2_L2A,  

  bbox=bbox,

  time=('2025-07-07', '2025-08-07'),  

  filter={

    "eo:cloud_cover": {

        "<": 50

    }

},  

)

PS: Thanks for the feedback , we have recently revamped the website so bear with us as we iron out some UI issues!