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
To cut out the training sites for UC8, we need the ability to restrict the load_stac process to load only data within certain geometries. This should be possible with:
the intersects keyword on pystac_client.ItemSearch, to only get the relevant STAC items,
followed by loading into pydata/sparse arrays and concatenating them to construct a sparse data cube to keep memory usage low.
A bonus objective would be for load_stac to figure out dynamically when it's a good idea to load sparse, vs dense.
I did a prototype for this (but loading with opendatacube) that looked like this, should be helpful as inspiration here:
Sorry, I just realized that I misread this and thought of it as a requirement for UC8 only - where, for UC8, we now implemented something else and still load bounding boxes.
But in general, we should of course keep this issue.
To cut out the training sites for UC8, we need the ability to restrict the
load_stac
process to load only data within certain geometries. This should be possible with:intersects
keyword onpystac_client.ItemSearch
, to only get the relevant STAC items,A bonus objective would be for load_stac to figure out dynamically when it's a good idea to load sparse, vs dense.
I did a prototype for this (but loading with opendatacube) that looked like this, should be helpful as inspiration here:
The text was updated successfully, but these errors were encountered: