Thank you for the explanation.
Unfortunately, we do not have an existed example code that fits to your workflow. That’s why we’re trying to understand what you’re trying to achieve, so we can help you come up with a workflow that fits the most.
In general, Batch API can only take geometries (either bounding box, polygon, or multipolygon) as an input. The advantage of Batch API is that you can have a really large area in country- or even continent-level (e.g., Europe). Then the API fetch the data within the selected time range (it is also possible to select the interested scenes by timestamps or some other metadata) and process the data as you wish (calculate indices for example). It should be noted that the output of Batch API is in UTM tiles and UTM coordinate reference system, so using Batch API requires some post-processing to convert the result to original tiling if sticking to the original tiling is a must in your workflow.
Let’s say it is acceptable for you to have features in UTM tiling grids, a workflow could be the following:
- Get the geometry of the tiles in your list. Here’s a useful resource of S2 tiles.
- Put all geometries together as a multipolygon.
- Use the multipolygon as an input of Batch API and calculate all the features you need.
- Apply some post processing to make the output fit to your ML model.
Let me know If the above workflow sounds good to you, and we can have further discussion.