feat: map the complete municipality of Mol
This commit is contained in:
@@ -513,6 +513,18 @@ This file now starts with the current implementation status. Older preparation/b
|
||||
- [x] Train and reject `geointel-building-yolov8s-aoi1024cleanpx12vis035e50-pt` through the positive/background promotion gate.
|
||||
- [x] Keep every local YOLO candidate inactive until positive-AOI and hard-negative promotion reports recommend default activation.
|
||||
|
||||
# Sprint 181 - Complete Mol municipality workspace
|
||||
|
||||
- [x] Persist the official VRBG municipality boundary for Mol (NIS `13025`).
|
||||
- [x] Page, deduplicate and boundary-clip the complete GRB GBG building layer.
|
||||
- [x] Import municipality layers through the existing DatasetService and
|
||||
VectorFeatureService path, with no direct provider-to-database write.
|
||||
- [x] Prefer the complete municipality workspace on a fresh session while
|
||||
keeping the lightweight boundary as the initially rendered layer.
|
||||
- [x] Make GeoJSON bounds calculation safe for municipality-scale layers.
|
||||
- [ ] Acquire and tile a georeferenced raster only for an explicitly selected
|
||||
Mol analysis zone before running the next configured-YOLO validation.
|
||||
|
||||
# Sprint 171 - Positive AOI expansion and small-building recovery
|
||||
|
||||
- [x] Reject cross-model false-negative comparisons when reference populations differ.
|
||||
|
||||
Reference in New Issue
Block a user