feat: add map-driven orthophoto analysis
This commit is contained in:
@@ -199,6 +199,20 @@ detector fixtures or download weights. A zero detection count is acceptable on
|
||||
the synthetic demo raster; production usefulness still requires validation on
|
||||
real georeferenced orthophotos and reference vectors.
|
||||
|
||||
### Map-driven building analysis
|
||||
|
||||
The primary map can hand an explicit EPSG:4326 rectangle to the bounded
|
||||
orthophoto acquisition endpoint. Its canonical raster Dataset then uses the
|
||||
unchanged configured-YOLO pipeline: 512 px tiles with 64 px overlap, preflight,
|
||||
local inference, Job + AnalysisRun + Detection persistence and persisted
|
||||
GeoJSON. When a ready GRB buildings reference Dataset exists, the same action
|
||||
launches existing detection QA and persists QualityCheck and Metric rows.
|
||||
|
||||
This flow does not download a model, bypass the model registry, write directly
|
||||
to Detection/vector tables or present AI boxes as official building truth.
|
||||
The 1 m request sampling is an operational model profile; provenance retains
|
||||
the official orthophoto source and latest-mosaic limitation.
|
||||
|
||||
### Real-data detection and QA validation
|
||||
|
||||
The real operational validation path uses operator-provided files rather than
|
||||
|
||||
Reference in New Issue
Block a user