Mukteshwar — dam consequence desk

Tier-1 screening — reviewed planning evidence; not a live warning. Decision values come from the accepted authority tables; maps provide spatial context.

Dam

Scenario

Regional contextSelected dam in Gujarat

Selected dam

Downstream model areaAccepted hydraulic study footprint

Planning context · not a live incident map. Administrative boundary: geoBoundaries/DataMeet · CC BY 2.5 IN. View published dam map → View operational map →

Operational map desk

Inspect the accepted flood surface and the screened evacuation network in one coordinate-aware workspace. Every mapped settlement boundary is clickable for its village statistics; routes expose their screening evidence. Switch basemaps, zoom, pan, or work full-screen.

Operational topographic basemap of the Mukteshwar downstream study area

N ↑ 10 km

Operational topo · exact accepted depth on hover

Accepted evidence

Flood surface

A light operational basemap keeps roads and settlements legible below the smoothed depth classes. Hover for the original accepted 60 m cell value.

Smoothed boundaries improve legibility only. Hover values come from the original accepted raster; no depth magnitude is interpolated for reporting.

Selected caseDesign-flood main-embankment overtopping breach

EPSG:32643Accepted projected coordinate system

0.05–8.76 mAccepted maximum-depth range

5 settlementsPopulation at risk 1,554

Selected-case planning note.

Route intelligence · deterministic screen

Accepted EAP route geometryDesign-flood main-embankment overtopping breach

163 routes shown

Select a settlement or route

Every settlement polygon and screened road corridor is selectable.

This is the shortest model-screened connection from the selected village to the mapped road network and an endpoint outside the modelled flood extent. It is not necessarily the fastest or safest route to a shelter or another settlement. Other local routes may exist and must be checked in the field during EAP planning. Settlements with no H3–H6 population at risk in the EAP-guiding scenario remain visible on the map but are intentionally outside the route-screening cohort.

Departure-time lensAt overtopping-breach initiation

−16 hovertopping-breach initiation+48 h

Two locations are tracked separately: the village boundary and the selected mapped-road segment. The planning screen uses whichever becomes wet first (≥0.05 m). Red routes are at or after that earlier time.

Select a route to compare estimated travel with its earliest modelled flood arrival.

“Modelled road water” is a deterministic scenario intersection, not a probability. The departure check is a planning calculation using the selected pace; routes and access tracks still require field verification.

Potential Consequence Index

Governed refreshed Potential Consequence Index (PCI) lower bound. Class boundaries are shown at 300 and 600; missing records are disclosed and the final score may be higher. Boundary position:

Warning time against exposure

Flood arrival relative to overtopping-breach initiation (x) against population at risk (y); dashed lines are the medians. Upper-left is the priority quadrant. Point size is total village population, colour is worst hazard class. Click a point to zoom to that village and open its information panel. Log population is the default so lower-PAR villages remain legible; exact PAR is unchanged in hover and tables.

Y-axis

Cumulative population at risk

How quickly population becomes at risk along the selected scenario timeline. Each step is a village reaching its arrival time; the interactive form of the EAP’s exposure curve. Hover for the village; click a point to zoom and open its information panel.

Hazard-class shares

A 100% composition view across the six CWC hazard classes for the twelve most exposed villages. PAR is printed at right; hover for exact counts and click to zoom and open village information.

Discharge along the flood path

Peak signed discharge at the current C1–C5 fixed downstream section cuts. Hover a section for its peak and event-relative time. This technical-review layer is shown only when its scenario HDF fingerprint matches the current DSS authority.

Evacuation routes

Maximum-depth screen locked to the EAP-guiding Design-flood main-embankment overtopping breach. The bands describe mapped-road intersection, not departure state or passability. Hover for exact counts.

Villages

Click a row to zoom to the village and open its flood-impact and evacuation information. Population split is across the six CWC hazard classes; PAR is classes H3–H6. The default order is PAR ↓; list position is not downstream sequence or flood-arrival order.