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

fix(map): keep municipality analysis local
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
Details
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
Details
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
Codex
2026-07-19 18:11:39 +02:00
parent e2c90da11d
commit 1f5a2f0ea7
5 changed files with 22 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CODEX_EXECUTION_LOG.md
+5 -2
View File
@@ -10924,7 +10924,10 @@ Implemented:
states and counts results per theme rather than per contributing layer;
- registered VMM VHA historical profile points as an operational bounded
Flanders bathymetry source and connected its existing acquire/select routes
to the Map product catalogue.
to the Map product catalogue;
- treated both Dutch municipality names and release-golden
`... municipality` Areas as local scope after live verification exposed a
false regional flood-raster partition path.
Live evidence:
@@ -10939,7 +10942,7 @@ Live evidence:
Validation:
- the complete readiness gate passed: 1,053 backend tests, 24 frontend tests,
- the complete readiness gate passed: 1,053 backend tests, 25 frontend tests,
backend compile, frontend TypeScript/typecheck, production build, Alembic
head `202607160001` and script smoke checks;
- a live API smoke over `5.10,51.17,5.11,51.18` proved all 17 applicable Mol