Add governed VMM flood hazard scenarios

2026-07-15 22:14:12 +02:00
parent 6238b252a9
commit 501f824257
38 changed files with 2059 additions and 18 deletions
@@ -8737,3 +8737,51 @@ Known limitations:
 Next:
 - Audit P5 official bathymetry and water-depth sources before enabling any
  water depth or volume metric. Keep DHMV as height/relief input only.
+
+## Sprint 208 - Governed VMM flood-hazard scenarios (2026-07-15)
+
+Implemented:
+- Audited official Vlaamse water-depth/bathymetry sources. Public coastal and
+  North Sea bathymetry does not cover Mol; Waterinfo is station-based and GRB
+  water geometry is two-dimensional. Permanent waterbody volume therefore
+  remains unavailable.
+- Added a fixed VMM OGRK registry for twelve water-depth scenarios: fluvial and
+  pluvial, current climate and climate projection 2050, each at T10/T100/T1000.
+- Added bounded WCS 1.1 retrieval, 10 km tiling, multipart GeoTIFF extraction,
+  georeferenced mosaicking, exact persisted-Area clipping and conversion from
+  positive source centimetres to normalized metres.
+- Persisted scenario, probability, units, bounds, request URLs and response,
+  coverage and normalized checksums through the existing Job, Dataset and
+  DatasetVersion architecture. No migration or direct raster DB write exists.
+- Added exact raster selection metrics for mapped inundated area/share,
+  mean/P90/maximum modeled depth and a maximum-depth area integral. The API,
+  UI and Ollama context all prohibit interpreting that integral as actual,
+  permanent or concurrent water volume.
+- Added an `Overstroming` map theme, explicit scenario selector, transparent
+  MapLibre overlay, source-inventory presentation and full-Mol operator.
+- Added Docker/Unraid configuration, packaging and focused backend/frontend/AI
+  contracts without a new dependency.
+
+Validation evidence before live deployment:
+- Official WCS capabilities and DescribeCoverage confirmed EPSG:31370, 2 m
+  GridOffsets, Float32 values, null value 0 and `image/tiff` multipart output.
+- A live bounded VMM request returned valid georeferenced data; official
+  catalog metadata confirms depth is expressed in centimetres between modeled
+  water surface and terrain.
+- Synthetic GIS fixtures confirmed 200 positive 5 m cells at 1 m depth produce
+  0.5 ha mapped area and exactly 5,000 m3 maximum-depth area integral.
+- Focused flood-hazard and Ollama tests passed; frontend typecheck and build
+  passed. Full readiness and Tower provisioning follow in this same pass.
+
+Known limitations:
+- The scenario raster represents modeled local maximum depth at 1:100,000
+  application scale, not a measurement of a current flood event.
+- No public municipality-wide inland bathymetry was identified. Waterbody
+  bottom elevation, uncertainty and permanent content remain open.
+- Scenario alternatives are not observations in time and are intentionally not
+  exposed as a historical temporal series.
+
+Next:
+- Complete live twelve-scenario Mol provisioning and browser validation. After
+  that, treat permanent inland bathymetry as an external-data prerequisite,
+  not as a value derivable from DHMV or the flood-hazard maps.