Export run-scoped spatial and tabular datasets using reusable profiles.
Overview
Features Export lets you build a repeatable export request, save/share it as profile text, and rerun it against the current run. The UI is profile-based: every setting in the form maps to a profile request payload.
Profile-Based Workflow
Choose a preset profile or paste profile YAML/JSON text.
Review/update format, units, CRS, layer selections, temporal settings, and selectors.
Export and download the generated ZIP artifact.
Built-in preset profiles
Profile key
UI label
Purpose
post_wepp
Post Wepp
Baseline spatial export for watershed/landuse/soils/WEPP summary layers.
Shown when Omni datasets are selected; scenario and contrast modes are mutually exclusive.
Omni quick actions
Select All, Unselect All
Bulk selection for scenarios or contrasts.
Temporal (conditional controls)
Control
Options
Description
Event selector
By date, By return period
Shown when any selected dataset is in event mode.
Dates
Comma-separated YYYY-MM-DD
Used when Event selector = By date.
Return periods
Comma-separated numeric years
Used when Event selector = By return period.
SWAT Options (conditional controls)
Control
Options
Description
SWAT run
latest or discovered run IDs
Chooses SWAT output run source.
Table filter mode
All tables, Include selected tables, Exclude selected tables
Controls SWAT table filtering behavior.
SWAT tables
Dynamic checklist from run catalog
Table names discovered from swat/outputs/run_*/interchange/*.
Exportable Datasets
The catalog currently exposes 27 dataset layer IDs. Availability of any dataset depends on run outputs and module state.
Channel summary note:
wepp.summary.channels resolves its internal source join on wepp_id so loss_pw0.chn.parquet metrics align with watershed/channels.parquet attributes before the consolidated channel carrier retargets to the geometry-facing channel identity.