Add bounded terrain and flood analysis

2026-07-17 20:36:45 +02:00
parent 972c3f0e1b
commit 47cde21e17
12 changed files with 441 additions and 125 deletions
@@ -10200,3 +10200,25 @@ Final live acceptance:
  and labelled `coverage_scope=municipality`. The UI reports product reference
  years directly so an end-of-year UTC timestamp cannot roll 2025 into a
  misleading local `1 jan 2026` label.
+
+## Sprint 238 - Governed Flanders terrain and flood selection (2026-07-17)
+
+Implemented:
+- Replaced the policy-raster-specific map query field with a typed official
+  raster acquisition contract for `thematic_raster`, `dhmv` and
+  `flood_hazard`.
+- Added a single Flanders product hook that loads all three fixed backend
+  registries in parallel. The browser still uses only canonical GeoIntel API
+  routes and has no external WCS URL.
+- Added an end-user DTM/DSM selector and the full twelve-product VMM scenario
+  selector. Existing exact-area Datasets are reused; absent products are
+  acquired, persisted, analyzed and reflected back into the Dataset catalog.
+- Extended the all-theme selection run with terrain and flood hazard while
+  preserving area intersection and the no-whole-Flanders-raster guard.
+- Fixed the invalid default flood key spelling in the Pydantic request schema.
+
+Validation:
+- Focused DHMV, VMM, map-orchestration and source-contract tests passed
+  (49 tests).
+- Frontend TypeScript typecheck and production build passed before the full
+  release gate.