Watershed Data Overview#

Note

This page and its static assets are auto-generated by python -m tools.doc_gallery. The Sphinx build only reads committed PNG and JSON artifacts.

This pair of figures documents the pre-solver side of HydroModPy. It shows how one watershed is contextualized before any flow run: local framing, DEM, and overlay-ready geographic inputs.

See also

Read the Data Overview walkthrough if you want the parameter mapping, a recommended reading order, and the first modifications to try.

Case Setup#

  • Launcher family: data-overview, so the workflow stops after setup, domain assembly, and data loading.

  • Primary editable file: examples/projects/04_data_overview/project.toml.

  • Committed figures are mirrored under examples/projects/09_capability_gallery/geographic/ so the doc build stays reproducible without a local results_stable checkout.

What It Shows#

  • How a watershed can be documented before any groundwater solve, using only setup and data loading.

  • How HydroModPy distinguishes a local watershed view from a broader DEM-oriented overview.

  • How versioned example outputs can feed static documentation without executing notebooks during the build.

How To Read It#

  • Read the DEM-oriented figure first to understand the broader terrain setting and outlet placement.

  • Read the local overview second to inspect which basin-scale overlays are available before any meshing or solving happens.

  • If the basin outline looks wrong, check outlet coordinates and snap distance before changing downstream modelling options.

Next Steps#

Reproduce#

Run the underlying example or validation case with:

python -m hydromodpy run examples/projects/04_data_overview/project.toml

Refresh the committed gallery artifacts with:

python -m tools.doc_gallery

Case Parameters#

Selected Parameters#

Field

Meaning

Value

Source

[geographic.catchment] catch_def

Watershed extraction mode used to derive the basin from the outlet definition.

from_outlet_coord

examples/projects/04_data_overview/project.toml

[geographic.catchment] x_outlet

Projected x coordinate of the outlet used by watershed extraction.

127348

examples/projects/04_data_overview/project.toml

[geographic.catchment] y_outlet

Projected y coordinate of the outlet used by watershed extraction.

6.8358e+06

examples/projects/04_data_overview/project.toml

[geographic.catchment] snap_dist

Maximum snapping distance used to align the requested outlet with the drainage network.

150 m

examples/projects/04_data_overview/project.toml

[geographic.catchment] buff_area

Extra area kept around the watershed to preserve regional context in overview figures.

20%

examples/projects/04_data_overview/project.toml

[domain] zone_ids

Domain layers kept on the spatial support before any meshing or solving stage.

geology

examples/projects/04_data_overview/project.toml

[domain.depth_model] thickness

Constant basin thickness assigned by the depth model when that mode is selected.

50.0 m

examples/projects/04_data_overview/project.toml

[data] types

Families of data loaded during the data-overview workflow.

geology, hydrography, hydrometry, intermittency, oceanic

examples/projects/04_data_overview/project.toml

[data] inference_mode

Policy controlling how strictly the data-loading stage resolves requested layers.

strict

examples/projects/04_data_overview/project.toml

Loaded Data Families#

Field

Meaning

Value

Source

[data] types

Ordered list of data families requested by the overview case.

geology, hydrography, hydrometry, intermittency, oceanic

examples/projects/04_data_overview/project.toml

[data.geology.sources]

Configured providers used to load the geology family in this case.

brgm_1m

examples/projects/04_data_overview/project.toml

[data.hydrography.sources]

Configured providers used to load the hydrography family in this case.

custom

examples/projects/04_data_overview/project.toml

[data.hydrometry.sources]

Configured providers used to load the hydrometry family in this case.

hubeau

examples/projects/04_data_overview/project.toml

[data.intermittency.sources]

Configured providers used to load the intermittency family in this case.

hubeau

examples/projects/04_data_overview/project.toml

[data.oceanic.sources]

Configured providers used to load the oceanic family in this case.

shom

examples/projects/04_data_overview/project.toml

Hydrography Source Options#

Field

Meaning

Value

Source

[[data.hydrography.sources]] source

Hydrography provider used for the displayed river network.

custom

examples/projects/04_data_overview/project.toml

[[data.hydrography.sources]] rasterize_field

Attribute used when rasterizing the clipped vector network to the watershed grid.

FID

examples/projects/04_data_overview/project.toml

Overview Panels#

Field

Meaning

Value

Source

[overview] name

Title injected into the generated overview panels.

Watershed Data Overview

examples/projects/04_data_overview/project.toml

[overview.panels] enabled

Panel toggles enabled for this overview run.

map_dem, map_geology, map_hydrography, stats_card, timeseries_discharge, timeseries_intermittency, station_inventory

examples/projects/04_data_overview/project.toml

[overview.panels] map_dem

Whether the map_dem panel is rendered for this overview case.

true

examples/projects/04_data_overview/project.toml

[overview.panels] map_geology

Whether the map_geology panel is rendered for this overview case.

true

examples/projects/04_data_overview/project.toml

[overview.panels] map_hydrography

Whether the map_hydrography panel is rendered for this overview case.

true

examples/projects/04_data_overview/project.toml

[overview.panels] stats_card

Whether the stats_card panel is rendered for this overview case.

true

examples/projects/04_data_overview/project.toml

Observation Windows#

Field

Meaning

Value

Source

[data.hydrometry] date_start

Start date used when querying hydrometry observations for this case.

2019-01-01

examples/projects/04_data_overview/project.toml

[data.hydrometry] date_end

End date used when querying hydrometry observations for this case.

2025-12-31

examples/projects/04_data_overview/project.toml

[data.intermittency] date_start

Start date used when querying intermittency observations for this case.

2019-01-01

examples/projects/04_data_overview/project.toml

[data.intermittency] date_end

End date used when querying intermittency observations for this case.

2025-12-31

examples/projects/04_data_overview/project.toml

[data.oceanic] date_start

Start date used when querying oceanic observations for this case.

2003-01-01

examples/projects/04_data_overview/project.toml

[data.oceanic] date_end

End date used when querying oceanic observations for this case.

2003-01-30

examples/projects/04_data_overview/project.toml

Source Pointers#

  • tools/doc_gallery/manifests/geographic_cases.json

  • examples/projects/04_data_overview/project.toml

  • examples/projects/09_capability_gallery/geographic/README.md

  • examples/projects/09_capability_gallery/geographic/watershed_overview/geographic_watershed_dem.png

  • examples/projects/09_capability_gallery/geographic/watershed_overview/geographic_watershed_local.png

Artifacts#

  • docs/source/_static/capability_gallery/geographic/geographic_watershed_dem.png

  • docs/source/_static/capability_gallery/geographic/geographic_watershed_local.png

  • docs/source/_static/capability_gallery/geographic/geographic_watershed_overview_summary.json stores the displayed metrics plus source hashes used by python -m tools.doc_gallery --check.