Add regional DHMV provisioning
GeoIntel CI / docs-smoke (push) Canceled after 0s
GeoIntel CI / contract-smoke (push) Canceled after 0s

This commit is contained in:
Codex
2026-07-16 12:36:34 +02:00
parent eae7d22675
commit e620689d8c
11 changed files with 611 additions and 14 deletions
+26
View File
@@ -1556,6 +1556,32 @@ 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.
## Regional DHMV terrain rasters
Plan and provision the governed DTM/DSM pair for all 28 persisted Kempen
municipality Areas:
```bash
docker exec geointel python /app/scripts/provision_regional_dhmv.py \
--scope kempen-transport-region --dry-run
docker exec geointel python /app/scripts/provision_regional_dhmv.py \
--scope kempen-transport-region
```
The complete run plans 56 canonical acquisitions. `--members Mol,Geel` and
`--products dtm_1m` provide bounded validation subsets; `--stop-on-error`
turns the default complete failure report into fail-fast behavior. Existing
checksummed request identities are reused unless `--force` is explicit. Each
successful item is reported immediately so a long operator run remains
observable. Every output is still an ordinary Area-linked Dataset and
DatasetVersion produced by the existing DHMV service.
The regional operator deliberately retains municipality partitions. It does
not assemble a monolithic Kempen height raster, does not claim annual terrain
change and rejects any terrain-analysis response that stops listing water
depth and water volume as unsupported.
## Mol VMM flood-hazard scenarios
Acquire and validate all twelve official VMM fluvial/pluvial flood-depth