We have GroupedCollectionExtractor which iterates through a set of AOIs and downloads all the items in a collection for that AOI. It'd be nice to build out a simpler version that just extracts the collection, and takes care to avoid regridding when possible, by not clipping the bounds either to the bounding box or the strict boundaries of a geometry. If we just export the image as is (possibly extracting its footprint to use as our boundary, if necessary), then we should be able to align the grid closely to the source, or skip a regridding.
This should then run an EEDLImage extract for each item in the collection. I'd personally love the following features, but some of them might need to wait:
We have
GroupedCollectionExtractorwhich iterates through a set of AOIs and downloads all the items in a collection for that AOI. It'd be nice to build out a simpler version that just extracts the collection, and takes care to avoid regridding when possible, by not clipping the bounds either to the bounding box or the strict boundaries of a geometry. If we just export the image as is (possibly extracting its footprint to use as our boundary, if necessary), then we should be able to align the grid closely to the source, or skip a regridding.This should then run an EEDLImage extract for each item in the collection. I'd personally love the following features, but some of them might need to wait:
GroupedCollectionExtractorin terms of running mosaicking and zonal stats - I anticipate that this may become a parent class ofGroupedCollectionExtractor, but they might have different entry points. They'll share a few core pieces of code, as well as most of the attribute definitions. Some thought and care here will help.