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
DataCube.save_result returns a DataCube, while it technically should return true (wrapped in _ProcessGraphAbstraction, to allow calling .download(), .create_job, ...)
The text was updated successfully, but these errors were encountered:
@soxofaan as far as I understand, the return value of save_result mentioned is what the process should return when executed in the back-end, and not something that the client should take care of. @m-mohr do I understand it correctly?
This ticket is purely about the python client side:
The Python methodDataCube.save_result currently returns a (new) DataCube instance, which allow the user to call things like aggregate_spatial or reduce_dimension on that:
which makes no sense (because the output of the save_resultopenEO process is a boolean), so the client should not allow that.
Instead, the DataCube.save_result should return something that still supports .download(), .execute_batch() and alike, but not allow all the data processing methods like aggregate_spatial, ...
related to #401, Open-EO/openeo-processes#334, Open-EO/openeo-processes#401
DataCube.save_result
returns a DataCube, while it technically should returntrue
(wrapped in_ProcessGraphAbstraction
, to allow calling.download()
,.create_job
, ...)The text was updated successfully, but these errors were encountered: