Add regional DHMV provisioning

2026-07-16 12:36:34 +02:00
parent eae7d22675
commit e620689d8c
11 changed files with 611 additions and 14 deletions
@@ -118,6 +118,13 @@ metadata records the 1 m native product, 5 m default analysis grid, EPSG:31370,
 derived browser views and are never authoritative. No raster binary is stored
 in PostgreSQL and no DHMV file is treated as water depth or volume.

+`provision_regional_dhmv.py` creates no separate evidence hierarchy and no
+monolithic regional raster. Each municipality/product result remains one
+ordinary Area-linked raster Dataset plus DatasetVersion. The retained
+provenance already includes every bounded WCS tile URL and aggregate response,
+coverage and normalized-output checksum. A repeat operator run resolves the
+same request identity and reuses the immutable file.
+
 VMM flood-hazard scenario outputs follow the same raster Dataset policy. The
 bounded acquisition service stores one normalized, compressed, Area-clipped
 GeoTIFF per scenario/request identity. `provision_regional_flood_hazards.py`