Fix YOLO class normalization
This commit is contained in:
+6
-3
@@ -180,9 +180,12 @@ metadata, tiles the raster, selects a mounted local model asset, verifies
|
||||
read-only YOLO preflight, runs configured YOLO detection, runs detection QA
|
||||
against persisted `vector_features`, and exports the detection run as GeoJSON.
|
||||
It does not seed demo data, enable fixture detections, fetch external data or
|
||||
download model weights. A zero detection count is accepted operationally, but
|
||||
must be interpreted as model/data quality evidence rather than as a successful
|
||||
building extraction result.
|
||||
download model weights. Configured-YOLO model class labels are normalized to
|
||||
lowercase for filtering and persisted detections, while the original model label
|
||||
is retained in detection provenance. A zero detection count is accepted
|
||||
operationally only when the selected model genuinely returns no usable
|
||||
detections after class filtering; it must be interpreted as model/data quality
|
||||
evidence rather than as a successful building extraction result.
|
||||
|
||||
Docker images install only the GIS runtime by default. To build a local/Tower
|
||||
image with PyTorch/Ultralytics available for the configured-YOLO preflight and
|
||||
|
||||
Reference in New Issue
Block a user