Nancon Observation Identity Card#
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 case reuses the broader Nancon data-overview output set as a stable identity card for one observed basin. It keeps the workflow strictly pre-mesh and pre-solver, but shows more than framing alone: terrain, geology, hydrography, climate synthesis, station inventory, and one compact stats card for the loaded observations.
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 geographic setup, data loading, and overview rendering.
Primary editable file: examples/projects/05_nancon_data_overview/config_overview.toml.
The committed identity-card figures are mirrored under examples/projects/09_capability_gallery/geographic/ so the gallery no longer depends on one local results_stable tree.
What It Shows#
How one basin can be summarized as an observation identity card before any mesh or solver is involved.
How DEM, geology, hydrography, climate synthesis, and station inventory can live on one page without rerunning notebooks.
How committed data-overview outputs can document which observations are available, not only where the watershed sits.
How To Read It#
Start with the DEM and hydrography panels to understand the basin support and the main drainage backbone.
Use the station inventory and stats card next to judge whether the observation families are rich enough for later simulation or calibration work.
Read the climate synthesis last as a forcing-context panel rather than as a solver result.
Next Steps#
Open the observed-series companion page next when you want to inspect the actual hydrometry, piezometry, intermittency, and water-quality chronologies.
Move to the simulation walkthrough only once the observation inventory and basin support look coherent.
Reproduce#
Run the underlying example or validation case with:
python -m hydromodpy run examples/projects/05_nancon_data_overview/config_overview.toml
Refresh the committed gallery artifacts with:
python -m tools.doc_gallery
Case Parameters#
Selected Parameters#
Field |
Meaning |
Value |
Source |
|---|---|---|---|
|
Watershed extraction mode used to derive the basin from the outlet definition. |
from_outlet_coord |
|
|
Projected x coordinate of the outlet used by watershed extraction. |
389286 |
|
|
Projected y coordinate of the outlet used by watershed extraction. |
6.81652e+06 |
|
|
Maximum snapping distance used to align the requested outlet with the drainage network. |
150 |
|
|
Extra area kept around the watershed to preserve regional context in overview figures. |
20 |
|
|
Families of data loaded during the data-overview workflow. |
geology, hydrography, hydrometry, piezometry, intermittency, precipitation, etp, temperature, recharge, runoff, wind, humidity, radiation, soil_moisture, water_quality |
|
Loaded Data Families#
Field |
Meaning |
Value |
Source |
|---|---|---|---|
|
Ordered list of data families requested by the overview case. |
geology, hydrography, hydrometry, piezometry, intermittency, precipitation, etp, temperature, recharge, runoff, wind, humidity, radiation, soil_moisture, water_quality |
|
|
Configured providers used to load the dem family in this case. |
ign_geoplateforme_dem |
|
|
Configured providers used to load the geology family in this case. |
brgm_1m |
|
|
Configured providers used to load the hydrography family in this case. |
bdtopage |
|
|
Configured providers used to load the hydrometry family in this case. |
hubeau |
|
|
Configured providers used to load the intermittency family in this case. |
hubeau |
|
|
Configured providers used to load the piezometry family in this case. |
hubeau |
|
|
Configured providers used to load the precipitation family in this case. |
sim2 |
|
|
Configured providers used to load the etp family in this case. |
sim2 |
|
|
Configured providers used to load the temperature family in this case. |
sim2 |
|
|
Configured providers used to load the recharge family in this case. |
sim2 |
|
|
Configured providers used to load the runoff family in this case. |
sim2 |
|
|
Configured providers used to load the wind family in this case. |
sim2 |
|
|
Configured providers used to load the humidity family in this case. |
sim2 |
|
|
Configured providers used to load the radiation family in this case. |
sim2 |
|
|
Configured providers used to load the soil_moisture family in this case. |
sim2 |
|
|
Configured providers used to load the water_quality family in this case. |
hubeau |
|
Hydrography Source Options#
Field |
Meaning |
Value |
Source |
|---|---|---|---|
|
Hydrography provider used for the displayed river network. |
bdtopage |
|
Overview Panels#
Field |
Meaning |
Value |
Source |
|---|---|---|---|
|
Title injected into the generated overview panels. |
Nancon |
|
|
Panel toggles enabled for this overview run. |
map_dem, map_geology, map_hydrography, stats_card, timeseries_discharge, timeseries_piezometry, climatic_summary, station_inventory |
|
|
Whether the map_dem panel is rendered for this overview case. |
true |
|
|
Whether the map_geology panel is rendered for this overview case. |
true |
|
|
Whether the map_hydrography panel is rendered for this overview case. |
true |
|
|
Whether the stats_card panel is rendered for this overview case. |
true |
|
Source Pointers#
tools/doc_gallery/manifests/geographic_cases.jsonexamples/projects/05_nancon_data_overview/README.mdexamples/projects/05_nancon_data_overview/config_overview.tomlexamples/projects/09_capability_gallery/geographic/README.mdexamples/projects/09_capability_gallery/geographic/nancon_identity_card/geographic_nancon_identity_card_map_dem.pngexamples/projects/09_capability_gallery/geographic/nancon_identity_card/geographic_nancon_identity_card_map_geology.pngexamples/projects/09_capability_gallery/geographic/nancon_identity_card/geographic_nancon_identity_card_map_hydrography.pngexamples/projects/09_capability_gallery/geographic/nancon_identity_card/geographic_nancon_identity_card_climatic_summary.pngexamples/projects/09_capability_gallery/geographic/nancon_identity_card/geographic_nancon_identity_card_station_inventory.pngexamples/projects/09_capability_gallery/geographic/nancon_identity_card/geographic_nancon_identity_card_stats_card.png
Artifacts#
docs/source/_static/capability_gallery/geographic/geographic_nancon_identity_card_map_dem.pngdocs/source/_static/capability_gallery/geographic/geographic_nancon_identity_card_map_hydrography.pngdocs/source/_static/capability_gallery/geographic/geographic_nancon_identity_card_map_geology.pngdocs/source/_static/capability_gallery/geographic/geographic_nancon_identity_card_station_inventory.pngdocs/source/_static/capability_gallery/geographic/geographic_nancon_identity_card_stats_card.pngdocs/source/_static/capability_gallery/geographic/geographic_nancon_identity_card_climatic_summary.pngdocs/source/_static/capability_gallery/geographic/geographic_nancon_identity_card_summary.jsonstores the displayed metrics plus source hashes used bypython -m tools.doc_gallery --check.