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

fix: keep Mol database layers explicit on map
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 11:01:36 +02:00
parent 1ba479b50b
commit aae6315981
9 changed files with 190 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+8
View File
@@ -7,6 +7,14 @@
# Changelog
## Sprint 183 Mol map source clarity and live AI validation (2026-07-14)
- Added an explicit Database/Analysis result map-content mode so an automatically loaded detection result can no longer mask a newly selected persisted municipality layer.
- Kept the Map workspace database-first and made dataset selection switch back to the selected PostGIS layer without discarding available detection, segmentation or change-analysis results.
- Restored the premium UI's viewport status row so visible/total feature counts and the 1,000-feature truncation warning remain readable.
- Rebuilt and deployed the all-in-one Tower runtime, then passed PostGIS 3.6 connectivity, schema/index, single-head migration, frontend proxy and browser runtime checks.
- Ran the bounded Mol-center raster -> tiles -> configured YOLO -> persisted Detection -> GRB QA -> export chain against the live runtime: 36 detections, 17 matches, precision 0.4722, recall 0.0455, F1 0.0829 and mean IoU 0.5958. These honest metrics confirm the workflow while keeping the current model below production-quality acceptance.
## Sprint 182 Municipality viewport delivery and bounded AI handoff (2026-07-14)
- Replaced full-file loading for vector datasets above 5,000 features with debounced, zoom-aware requests to the existing persisted PostGIS bbox-selection endpoint.