Closed omad closed 3 years ago
Other potential area of concern is dealing with "lazy datasets", i.e. dask arrays. Potentially some kind of tiling might be required, essentially same thing ingest does. Once this feature is available people will want to apply it to entire DB, we will need to make it easy. Put actual "workflow" into GridWorkflow
class. Doesn't mean we have to address right away, but it will be requested next I can guarantee it.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Use Case
When experimenting with data loading from a Data Cube users need to be able to save the
xarray.Dataset
objects back into an Index, for use in future analysis.Product
may or may not already exist.Starting Point
@petewa has an initial implementation available in the
csiro/execution-engine
branch with an API that looks like:This is a good starting point for implementing a simple
save
function.In discussion with @Kirill888 there's a few additions and changes we would propose:
save()
function directly on theDatacube
object.create_product
is a separate step tosave
Potential Problems
Products
, which would become far more likely with users creating many more products. Will raise another issue about this, but it should be fixed before releasing asave
feature.