fix: polish measured map quality output
This commit is contained in:
@@ -8168,6 +8168,26 @@ Validation before deployment:
|
||||
- Focused review/evidence regressions passed and the production bundle retained
|
||||
separate React, application and MapLibre chunks.
|
||||
|
||||
Live operational proof:
|
||||
- Tower deployed commit `d22abe8` with AI extras enabled. The all-in-one
|
||||
runtime became healthy, PostGIS 3.6 passed, Alembic reached `202607150001`,
|
||||
and the new table exposed 13 columns plus six expected indexes.
|
||||
- Quality check `acaca138-dbb9-4498-ae53-d0732b6270e3` returned 206 persisted
|
||||
evidence geometries in 338 ms with zero unresolved ids. All 72 reviewable
|
||||
false-positive/false-negative features were explicitly `unreviewed`.
|
||||
- A new browser-driven 35.57 ha Mol rectangle acquired the official orthophoto,
|
||||
ran the configured local YOLO model and persisted analysis run
|
||||
`14f3b856-1ff0-4939-892a-3c8347a669f1` plus quality check
|
||||
`087d2b6a-6d3c-4508-ab1e-da49734097c2` at IoU `0.25`.
|
||||
- The live run produced 100 candidates, 73 matches, precision `0.73`, recall
|
||||
`0.4965986395`, F1 `0.5910931174`, mean IoU `0.5361610234`, 27 false
|
||||
positives and 74 false negatives. The UI showed these values as measured
|
||||
candidates and retained the explicit `controle vereist` source warning.
|
||||
- Browser audits at 1280x720 and 3440x1440 had no console warnings/errors or
|
||||
horizontal overflow. The review queue rendered 50 paginated rows; the
|
||||
ultrawide map used about 2,410 px. A final compact-metric fix was queued after
|
||||
the 1280 px screenshot exposed cramped six-column labels.
|
||||
|
||||
Next:
|
||||
- Deploy the migration and UI, verify one live review queue and map QA result,
|
||||
then complete representative manual decisions before constructing any new
|
||||
|
||||
Reference in New Issue
Block a user