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

feat: make Mol explorer map-first
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-14 13:21:53 +02:00
parent e340b7f1ec
commit 2958c25b6f
24 changed files with 1901 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CODEX_EXECUTION_LOG.md
+21
View File
@@ -7743,3 +7743,24 @@ Open:
- Final internal-browser verification loaded the official Mol municipality
boundary over the OpenStreetMap road basemap from the persisted PostGIS
workspace. The live Tower page reported no console warnings or errors.
## Sprint 186 Map-first Mol geographic explorer (2026-07-14)
Changed:
- Made Map the default application workspace and reduced the primary task to data theme, rectangle selection and evidence review.
- Added a dedicated three-column explorer with explicit available/missing themes, full-Mol scope, true MapLibre drag selection, automatic PostGIS queries, exact totals, density, property evidence and GeoJSON handoff.
- Preserved the previous technical workflow behind `Geavanceerde werkbank` and kept QA, AI and export persistence unchanged.
- Added exact `total_feature_count` to the vector bbox-selection response while retaining the existing 1,000-feature geometry cap.
- Added `provision_mol_context_layers.py` for official GRB roads (`Wegsegment`), water (`WTZ`, `WLAS`, `WGR`) and parcels (`ADP`) clipped to NIS 13025 and imported through the public dataset API.
Validated so far:
- Frontend typecheck and production build passed.
- Focused map, orchestration and new explorer tests passed.
- Official fetch-only smoke produced 8,444 Mol road features, 3,668 water features and 32,961 parcels with complete pagination and no truncation.
- Full backend suite reached 516 tests; one legacy component-boundary guard initially failed and was resolved by moving theme API orchestration into `useMapThemeSelectionInsights`.
Limitations:
- Population and forest/green remain unavailable rather than simulated until suitable authoritative sources and semantics are selected.
- Live Tower import and browser verification follow after the full readiness gate and deployment.
Next:
- Deploy, import the three official Mol context layers, validate rectangle analysis in the in-app browser and then define authoritative population and land-cover source adapters.