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
I think we can bypass Gdrive entirely using the same tilling system of SEPAL in combination with the thumbnail export method. Have a look in the TS documentation for the structure.
I think that this is something that has to be discussed. Although the tiling process can be useful when we do have not such complicated workflows... it might take so long in some other specific workflows, the user will have to wait longer and the sepal session can be killed...
Having a gdrive module would be useful in these cases, what do you think?
agreed :
what I envisioned was to have 3 downloading options :
download to sepal (bypassing Gdrive and direct download from the app)
download to Gdrive
download as an asset
(1) works without exiting the module and is super useful for a small amount of data or something you really want to monitor.
Well designed we could prepare all the data and then launch a downloading script (that would live in sepal-ui) running in an os.system like execution. Executing the export this way guarantees that it continues to work after the app is closed.
(2) and (3) would launch the task on GEE and in the task manager app we could retrieve all the specific information and manage the asset/files from there.
Lots of the computation performed with python in sepal implies an interaction between gee (and gdrive) and the sepal folder.
Do you think it could be useful to create standard drive_handler object ? (inspired by the one in pysmm and glad_alert)
with some standard method like
...
If some application requires specific implementation you can just create your custom drive_handler inheriting from this one
The text was updated successfully, but these errors were encountered: