Add operator YOLO tile dataset exporter
This commit is contained in:
@@ -266,6 +266,25 @@ This remains operator tooling only. GeoIntel does not expose Training Studio in
|
||||
V1, does not generate labels from predictions and does not treat the trained
|
||||
artifact as useful until it passes the same real-data Detection + QA matrix.
|
||||
|
||||
If the whole-image dataset underfits or produces unusable detections, export
|
||||
overlapping tile-level samples:
|
||||
|
||||
```bash
|
||||
docker exec -it geointel python3 /app/scripts/export_operator_yolo_tile_dataset.py \
|
||||
--manifest-path /app/storage/operator-data/operator_samples_manifest.json \
|
||||
--output-dir /app/storage/operator-data/yolo-building-tile-dataset \
|
||||
--tile-size 192 \
|
||||
--stride 96 \
|
||||
--negative-keep-ratio 0.5 \
|
||||
--val-samples turnhout \
|
||||
--force
|
||||
```
|
||||
|
||||
The tile exporter clips reference building boxes into tile-local YOLO labels
|
||||
and records the positive/negative tile counts. This gives the training smoke
|
||||
more image samples while preserving the same explicit operator-data and QA/QC
|
||||
validation boundary.
|
||||
|
||||
For visual error inspection, export the persisted QA evidence from a calibration
|
||||
summary:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user