evaluate models on fresh regional calibration AOIs
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s

This commit is contained in:
Jens
2026-08-09 22:36:27 +02:00
parent 116b8e291e
commit b068a5e065
28 changed files with 5053 additions and 18 deletions
+17
View File
@@ -53,6 +53,23 @@ marker before release verification or CUDA allocation. Non-overlap proves only
that tiles do not share pixels; checkpoint reports explicitly avoid claiming
statistical independence for adjacent tiles from the same AOI.
`provision_belgium_building_training_portfolio.py --aoi-spec` provisions a
pre-registered custom portfolio but deliberately accepts only `train`, `val`
and `calibration`; protected test roles are rejected. For regional diagnostic
work where the PICC/UrbIS harmonisation contract is still pending,
`assemble_belgium_building_corpus.py
--evaluation-only-pending-regional-contracts` preserves the exact authority
failure, writes `NO_TRAINING.json` and makes no release claim.
`export_yolo_diagnostic_evaluation_tiles.py` accepts only such a
training-prohibited calibration manifest. It emits empty train directories and
retains only full canonical non-overlapping grid cells; generic final-edge
coverage windows are removed from the generated view and listed explicitly.
`audit_evaluation_lineage_spatial_independence.py` then resolves every ancestral
sample back to its georeferenced source raster and checks the frozen metric
distance floor. These controls supplement, rather than replace, exact sample
lineage checking in the checkpoint evaluator.
Setup-, import-, demo- en maintenance-scripts voor GeoIntel.
## WALOUS source provisioning