feat: guide raster building analysis workflow

2026-07-15 00:19:38 +02:00
parent d528677e03
commit 2f9898bc82
12 changed files with 598 additions and 64 deletions
@@ -85,6 +85,18 @@ Detection Lab and Segmentation Lab now share the same AI workspace hierarchy: mo

 AI Lab run controls explicitly explain when no raster dataset is available, instead of only showing disabled detection/segmentation run buttons.

+Detection Lab now provides one guided operational path for configured building detection:
+
+1. choose an existing raster or explicitly upload a georeferenced GeoTIFF;
+2. create canonical 512 px tiles with 64 px overlap through the existing raster API;
+3. run the read-only YOLO preflight for the selected local model asset;
+4. execute the existing persisted detection endpoint;
+5. load the persisted Detection rows and GeoJSON and open them on the existing MapLibre map.
+
+The browser never manufactures manifest content, detections or QA metrics. Manual manifest paths and direct-manifest execution remain available only under technical tile settings. Detection QA remains the existing persisted reference comparison and is shown as a primary review step.
+
+Before creating tiles, the guided action inspects raster dimensions and estimates the number of 512/64 tiles against the backend-reported `YOLO_MAX_TILES`. Oversized imagery is stopped before tile files are written and must first be clipped to the intended work area. Repeated runs reuse the currently linked manifest.
+
 ## Scope implemented
 - API client layer (`src/services/api`)
 - Project and area list/create flows