feat: map the complete municipality of Mol

2026-07-14 05:35:15 +02:00
parent f757a527cf
commit 490325e0cd
20 changed files with 1027 additions and 62 deletions
@@ -7395,3 +7395,41 @@ Open:
 ## Next pass

 - Harden detection QA coverage and matching diagnostics before making a retraining decision; keep that work separate from this presentation-only sprint.
+
+# Sprint 181 - Complete Mol municipality workspace
+
+## Implementation
+
+- Added an explicit operator provisioner for the official VRBG `Refgem`
+  municipality geometry for Mol (NIS `13025`) and the complete paged GRB `GBG`
+  building collection clipped to that exact boundary.
+- Added deterministic persistent source artefacts and a manifest containing
+  source URLs, checksums, page/feature counts, boundary bounds and area, and an
+  explicit truncation flag. Pagination and identity checks fail closed.
+- Kept the provider boundary honest: provisioning is an operator action and
+  imports through canonical Project, Area and Dataset HTTP routes. It does not
+  enable the dormant live GRB provider or write directly to `vector_features`.
+- Optimized the existing vector persistence path by replacing one ORM refresh
+  per feature with a single flush and commit. Persistence shape and API
+  behavior remain unchanged.
+- Made `Mol Municipality Workbench` the preferred fresh-session context once
+  its official boundary is ready. The boundary opens first; the much larger
+  building layer remains explicitly selectable from the Map database-layer
+  control.
+- Replaced spread-based map extent calculations with a streaming, memoized
+  GeoJSON bounds helper and added municipality/building layer styling. This
+  avoids large coordinate arrays while keeping the existing MapLibre path.
+
+## Initial validation
+
+- Exact clipping, pagination/truncation, persistence-scaling and frontend
+  wiring regression coverage passed locally.
+- No API route, ORM model, migration, QA metric, detection result or model
+  configuration changed.
+
+## Next pass
+
+- Deploy and execute the explicit provisioner on Tower, verify full PostGIS
+  feature counts and exact Mol bounds, then audit the complete municipality in
+  MapLibre before acquiring raster imagery for a deliberately selected Mol
+  analysis zone.