Complete regional raster exploration
This commit is contained in:
+8
-6
@@ -519,12 +519,14 @@ GeoJSON export stays disabled. The UI never labels the maximum-depth area
|
||||
integral as current, permanent or concurrent water volume.
|
||||
|
||||
Regional VMM provisioning creates one scenario raster per municipality Area.
|
||||
The explorer therefore shows only the flood scenarios whose `area_id` matches
|
||||
the active work area. This avoids presenting a Mol scenario while the map is
|
||||
focused on another municipality. The region-wide Area remains the navigation
|
||||
context; municipality Areas are the analysis scope for flood rasters because
|
||||
the public WCS and raster cell limits make one monolithic Kempen raster
|
||||
operationally unsafe.
|
||||
For a municipality the explorer still uses only that exact Area-linked file.
|
||||
For the complete Kempen Area it presents the 28 VMM and DHMV partitions as one
|
||||
logical map layer, deduplicates VMM into twelve scenario choices and renders
|
||||
every matching MapLibre image partition. A drawn rectangle is sent to the
|
||||
partition endpoint, which opens only intersecting files and calculates exact
|
||||
combined cell statistics. A monolithic full-region 5 m calculation remains
|
||||
disabled because it exceeds the governed raster-cell limit; users draw a
|
||||
bounded rectangle without first choosing a municipality.
|
||||
|
||||
## Useful repository scripts
|
||||
|
||||
|
||||
Reference in New Issue
Block a user