Add Mol multi-zone operational validation
This commit is contained in:
@@ -227,6 +227,21 @@ the first 1000-feature page. Generated reference GeoJSON records
|
||||
`reference_max_features` and `source_urls` for auditability. The application
|
||||
itself still does not perform live provider fetching.
|
||||
|
||||
### Mol operational validation pack
|
||||
|
||||
The operator registry includes a Mol-first validation pack: Mol center,
|
||||
Achterbos residential, Gompel mixed settlement, Donk canal/industrial and
|
||||
Postel rural village. The four new zones are marked as validation holdouts so
|
||||
future training exports cannot silently consume the operational benchmark.
|
||||
Postel-bos is evaluated separately as a background control.
|
||||
|
||||
`run_mol_operational_validation.sh` composes the existing positive multi-sample
|
||||
quality matrix and background detection matrix. Positive runs use persisted GRB
|
||||
`vector_features` and create real `QualityCheck`/`Metric` rows; background runs
|
||||
only report persisted detection pressure and never synthesize QA metrics. AOI
|
||||
bounds from the operator manifest are persisted as EPSG:4326 `Area` records so
|
||||
every generated project opens as a complete map context.
|
||||
|
||||
For confidence-threshold calibration, use the sweep wrapper:
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user