War Room: global references, scenarios and location evidence

Complete fullscreen workspace

Full screen expands the whole War Room iframe, with a persistent Close full screen control. Browser fullscreen is used where permitted; a top-layer full-window fallback preserves the same iframe, map and unsaved forms. All controls exposes original workflow, place/time, geography, saved-view, imagery, watch and drawing menus. Account permissions and replay/owner boundaries remain.

Independent dam catalogues

The source selector changes the catalogue and its map together. Catalogues overlap: their counts are source records, not unique world dams, and they are not joined by proximity.

• Global Dam Tracker (GDAT) v1: 35,140 published records, including 31,780 mapped dam locations; 3,360 records with null geometry are excluded from this spatial projection. Names, height/year, reservoir-volume variants, purpose and source flags remain qualified. Its catchment polygons are not used as reservoir or flood outlines. Zhang & Gu (2023), source and CC BY 4.0 licence.
• GeoDAR v1.1: 24,783 dam references and 21,515 reservoir outlines. Only 7,295 positive capacity references were present in qualification; other volumes remain missing, including withheld proprietary attributes. Many names/heights/status fields are absent. Original georeferencing and QA fields remain. Wang et al. (2022), source and CC BY 4.0 licence.
• GDW viewer extract: 41,145 river/barrier reference locations from the official public viewer. This 21-field extract differs from the 71-field scientific archive: 24,108 positive capacity values differed in qualification, and quality/status/height/shared-reservoir attributes are absent. It is independently labelled, with no assumption of scientific-archive equivalence. Underlying viewer revision is not established; HTTP Last-Modified is not an observation date. This product incorporates data from the GDW database © Global Dam Watch (2024), under CC BY 4.0. Publisher; viewer data.

No catalogue enumerates every small dam worldwide. Original source IDs, coordinates, units, date and missing-data meanings remain visible. A river/outlet reference is not a verified structure location or downstream toe.

Explicit dam scenarios

Every budget requires an explicitly entered or selected user volume assumption. Catalogue capacity is not current or established releasable storage. Consolidated, reported, maximum and minimum variants are separate; a missing consolidated value is not silently filled. GDW viewer values retain their own limitations.

Mean rate (m³/s) = assumed volume (million m³) × released fraction × 1,000,000 / (duration hours × 3,600). The sensitivity table varies the assumptions. This is mass balance, not a breach hydrograph.

Native local terrain-connected stage/storage screens require explicit downstream toe, valley extent and stage-rise assumptions. Their equations remain unchanged. No failure probability, engineered inundation, arrival time, velocity, casualties or evacuation-route prediction is supplied. Unshaded or outside-study locations are not established safe.

Reservoir geometry

GeoDAR outlines are linked only to their own GeoDAR IDs. Its WGS84 cylindrical equal-area geometry is transformed to longitude/latitude with an ellipsoidal inverse; source boundary and island rings remain separate lines. Original source resolution and positional uncertainty dominate numerical transform precision. Outlines are dated references, not current water extent or downstream flood footprints. Geometry outside viewer bounds is explicitly unavailable while record details remain accessible.

Terrain and connections

Approximately 1.34 million selected GeoNames references include peaks, hills, ridges, passes, scenic viewpoints, waterways, bridges/tunnels/junctions and selected medical facilities. These are named references, not verified tactical positions, territorial control, legal access, operational facilities or safe evacuation routes. Published elevation and coarse DEM estimates are distinct. Grid counts/centroids are display aggregates, not actual feature locations. GeoNames — CC BY 4.0.

Historical hazards and candidate places

NOAA sources include IBTrACS cyclone tracks since 1980, significant earthquakes, significant volcanic catalogue events and published tsunami coastal observations. Original source dates and flags remain; uncertain tsunami records are excluded from default assessments. Track gaps and antimeridian discontinuities are separated. Tracks and points are not impact footprints.

NASA EONET history is queried since 2000, subdividing date windows at response bounds and showing unresolved caps. Geometry dates are observation/report dates, not necessarily event onset. NASA COOLR uses the existing reviewed public landslide cache, admitting dated/mapped records only.

Candidate profiles report source-record proximity and coverage gaps within a user radius/year window. Radius is a query boundary, not a hazard boundary. Dam proximity is not downstream connectivity. Counts can overlap and reflect uneven reporting. No overall safe-location score is calculated: safety remains unestablished. Missing coverage, no matches and candidate/response bounds are distinguished.

Source clocks, exports and privacy

Scheduled collection retains original source clocks, bounded last-good responses and provider pause/backoff decisions. Captured-at is retrieval time. Separate source namespaces preserve dataset identities. Public API/MCP provide read-only references; native source pages and MCP scalar pages are separate. Private scenes, cases, sites, watches and shares retain their original permissions.

New candidate selections/comparisons are session-only unless explicitly exported or pinned through existing investigations. Exports retain source identities and assumptions. Owner, verification, replay and visibility transitions clear session planning state.

IBTrACS · NOAA hazards · NASA EONET · NASA landslides · Native terrain/radio/stage methods