Jens/geointel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add governed VMM flood hazard scenarios
GeoIntel CI / docs-smoke (push) Canceled after 0s
Details
GeoIntel CI / contract-smoke (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
Codex
2026-07-15 22:14:12 +02:00
parent 6238b252a9
commit 501f824257
38 changed files with 2059 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/README.md
+23
View File
@@ -1539,6 +1539,29 @@ docker exec geointel python /app/scripts/provision_mol_dhmv.py --resolution-m 5
Do not use DHMV output as water depth or water volume. The command fails when
the API no longer reports those metrics as explicitly unsupported.
## Mol VMM flood-hazard scenarios
Acquire and validate all twelve official VMM fluvial/pluvial flood-depth
scenarios for the exact persisted Mol Area:
```bash
docker exec geointel python /app/scripts/provision_mol_flood_hazards.py
```
The operator resolves the project and Area through canonical APIs, validates
the backend registry and acquires every current/2050 T10/T100/T1000 coverage.
The backend performs bounded WCS 1.1 retrieval, tiled mosaicking, exact Area
clipping and centimetre-to-metre normalization. The operator then runs the
full-Area selection smoke and rejects any response that stops declaring
bathymetry, permanent water volume and concurrent flood volume unsupported.
Useful safe overrides:
```bash
docker exec geointel python /app/scripts/provision_mol_flood_hazards.py --products pluviaal_current_t100
docker exec geointel python /app/scripts/provision_mol_flood_hazards.py --resolution-m 5 --force
```
## Tower deployment
Push the local branch to Gitea, then rebuild the Unraid/Tower Docker runtime: