Add Mol multi-zone operational validation
This commit is contained in:
@@ -460,6 +460,13 @@ manifests generated for AI handoff include source CRS metadata so pixel-space
|
||||
model outputs can be transformed to WGS84 GeoJSON coordinates. Current V1 upload
|
||||
support is limited to GeoTIFF-style rasters and GeoJSON/JSON reference vectors.
|
||||
|
||||
When `REAL_AREA_BBOX=minx,miny,maxx,maxy` is supplied, the same workflow also
|
||||
persists an EPSG:4326 project Area before uploading data. `REAL_AREA_NAME` and
|
||||
`REAL_PROJECT_REGION` retain operator context. The multi-sample runner fills
|
||||
these values from manifest `wgs84_bbox` and municipality metadata, so generated
|
||||
projects are immediately usable in the map without an alternate persistence
|
||||
path or API contract.
|
||||
|
||||
To prepare the documented operator sample corpus inside the all-in-one runtime
|
||||
container, run:
|
||||
|
||||
@@ -477,6 +484,12 @@ empty GRB FeatureCollections for negative-tile training; normal reference AOIs
|
||||
still fail when GRB returns no buildings. These are runtime artifacts only and
|
||||
are not committed to Git.
|
||||
|
||||
Mol additionally has operational holdouts for Achterbos, Gompel, Donk and
|
||||
Postel, with Mol center as the historical baseline and Postel-bos as a separate
|
||||
background control. Prepare and execute that pack with the documented
|
||||
`prepare_operator_real_data_samples.py` and
|
||||
`run_mol_operational_validation.sh` commands in `scripts/README.md`.
|
||||
|
||||
The current recommended local building model is
|
||||
`geointel-building-yolov8s-smallbld-minpx3-img640-ft30-pt` with tile size
|
||||
`512`, overlap `64` and confidence threshold `0.15`. Its SHA256 is
|
||||
|
||||
Reference in New Issue
Block a user