Fix runtime GIS uploads for operator QA

2026-07-09 14:03:38 +02:00
parent a1b33555b9
commit 7bf0757470
9 changed files with 75 additions and 5 deletions
@@ -7,6 +7,16 @@

 # Changelog

+## Sprint 151 runtime GIS upload and AOI1024 YOLO candidate (2026-07-09)
+
+- Fixed the operator YOLO training wrapper so the all-in-one runtime defaults to `/opt/geointel/venv/bin/python` when present, while still falling back to `python3` for local shells.
+- Raised the Nginx upload limit to `250m` in both the compose frontend proxy and Unraid all-in-one proxy after a live 1024px GeoTIFF QA upload hit `413 Request Entity Too Large`.
+- Prepared a larger Tower operator sample manifest at `/app/storage/operator-data/operator-samples-1024` using explicit `1024x1024` rasters and doubled AOI half-size.
+- Exported and audited `/app/storage/operator-data/yolo-building-aoi1024-visible025`: 144 tiles, 117 positive tiles, 27 negative tiles, 15,079 labels and `min_label_visible_ratio=0.25`; audit remains `needs_attention` because median label area is still below gate.
+- Trained inactive local model asset `geointel-building-yolov8s-aoi1024visible025e50-pt` from the AOI1024 dataset. Ultralytics validation ended at approximately precision `0.275`, recall `0.331`, mAP50 `0.188` and mAP50-95 `0.0716`.
+- The candidate remains inactive and must pass persisted detection QA/QC plus background/hard-negative promotion gates before default activation.
+- No API contract, migration, product feature, provider fetching, fake detection data or active model default changed.
+
 ## Sprint 150 YOLO label visible-ratio gate (2026-07-09)

 - Added `--min-label-visible-ratio` / `OPERATOR_YOLO_MIN_LABEL_VISIBLE_RATIO` to the operator YOLO tile dataset exporter.