Skip to content

Support Earth Engine exports from SEPAL sandboxes through TaskManager - #454

Closed
dfguerrerom wants to merge 15 commits into
masterfrom
feat/pysepal-api-exports
Closed

dfguerrerom wants to merge 15 commits into
masterfrom
feat/pysepal-api-exports

Conversation

@dfguerrerom

@dfguerrerom dfguerrerom commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Closes #453.

Accept ee.export tasks from pysepal-api for image and table exports to assets, Drive, or the SEPAL workspace, reusing existing exporters and task progress, cancellation, and downloads; task rows retain export names alongside notebook/script/app origins from pysepal-api #8.

When a task is submitted, task-manager records where it lands for every destination: the asset id, the Drive folder Earth Engine writes to, or the workspace folder (~/ paths are read from the home folder). Invalid exports are refused at submission with a 400 and the reason. As in the GUI, a workspace export into a folder that already holds files, or that another unfinished task writes to, is refused. Export names are reduced to the characters and 100-character length Earth Engine accepts for task descriptions, while file name prefixes keep the user's text as a single path segment. Polygon masks are preserved for exports without scale/dimensions, asset exports without a crs keep Earth Engine's default projection (recipe asset exports still default to EPSG:4326), and public asset exports report their sharing step. Table formats accept Earth Engine's spellings, table max_vertices remains Drive-only, and ImageCollection assets require the tiled recipe workflow. A workspace image that arrives in tiles gets a VRT with its band names, as recipe exports do.

Validation: 2,053 shared, 1,715 GEE, 128 task and 137 task-manager unit tests and the full GUI suite (5,098 tests) pass; MySQL integration tests were not run locally.

Deploy the updated gee, task, task-manager, and gui images together.

@dfguerrerom dfguerrerom changed the title Support notebook Earth Engine exports through TaskManager Support Earth Engine exports from SEPAL sandboxes through TaskManager Oct 20, 2026
@dfguerrerom
dfguerrerom force-pushed the feat/pysepal-api-exports branch from 7e62af2 to 4da9d03 Compare October 23, 2026 08:42
@dfguerrerom
dfguerrerom changed the base branch from sepal-server to feat/recipe-folders October 23, 2026 08:42
@dfguerrerom
dfguerrerom added this pull request to stack #456 October 23, 2026 08:42
@dfguerrerom
dfguerrerom force-pushed the feat/pysepal-api-exports branch 2 times, most recently from 04f7543 to f24cdac Compare October 26, 2026 09:53
@dfguerrerom
dfguerrerom removed this pull request from stack #456 October 30, 2026 08:17
@dfguerrerom
dfguerrerom marked this pull request as draft October 30, 2026 12:42
@dfguerrerom
dfguerrerom changed the base branch from feat/recipe-folders to master November 4, 2026 10:13
@dfguerrerom
dfguerrerom force-pushed the feat/pysepal-api-exports branch 2 times, most recently from 5c4df9f to ad73e6b Compare November 4, 2026 14:18
@dfguerrerom
dfguerrerom force-pushed the feat/pysepal-api-exports branch from dfa1d94 to 708bee7 Compare November 10, 2026 13:03
@lpaolini
lpaolini deleted the feat/pysepal-api-exports branch November 18, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support Earth Engine exports from SEPAL sandboxes through TaskManager

1 participant