Currently we read in all rasters associated with an item before warping them because the user can specify that tiles should be stored in combinations that span multiple raster files.
But this is memory-intensive for a data source like Sentinel-2 with many bands and large raw GeoTIFF files.
Instead I think we should drop support for this and instead only allow users to specify a subset of the bands available in the data source.
Then we can do the warping for each band separately, reducing memory usage for each process.
Currently we read in all rasters associated with an item before warping them because the user can specify that tiles should be stored in combinations that span multiple raster files.
But this is memory-intensive for a data source like Sentinel-2 with many bands and large raw GeoTIFF files.
Instead I think we should drop support for this and instead only allow users to specify a subset of the bands available in the data source.
Then we can do the warping for each band separately, reducing memory usage for each process.