Files
geointel/docs/40-build-launch/GOLDEN_DATASET_PACKAGE.md
T
Codex 6ea3586a3e
GeoIntel CI / docs-smoke (push) Has been cancelled
GeoIntel CI / contract-smoke (push) Has been cancelled
Initial GeoIntel V1 foundation
2026-06-16 23:36:32 +02:00

68 lines
1.7 KiB
Markdown

# GOLDEN DATASET PACKAGE
The golden dataset package defines the stable demo/test inputs that Codex must protect.
## Purpose
Golden data allows Codex to build and test without depending on live external services.
## Golden area
`demo/geel/area_geel_center.geojson`
Represents the canonical Sprint 1 area fixture. It must remain valid GeoJSON.
## Golden reference layer
`demo/geel/reference_buildings.geojson`
Represents reference building polygons. In future this will map to GRB-like reference data.
Required properties:
- stable feature IDs where possible;
- polygon or multipolygon geometry;
- deterministic feature count;
- valid geometries.
## Golden prediction layer
`demo/geel/demo_detections.geojson`
Represents predicted building detections or imported detection outputs.
Required properties:
- class label;
- confidence where available;
- polygon or bbox-derived polygon geometry;
- stable enough for QA/QC fixture checks.
## Golden expected metrics
`demo/geel/expected_qaqc_metrics.json`
Represents expected QA/QC output for the demo fixture. Codex may update this only if:
- the fixture geometry intentionally changes;
- the QA/QC algorithm version changes;
- changelog explains the reason.
## Golden data rules
- Do not delete golden fixtures.
- Do not replace golden fixtures with random generated data.
- Do not make tests depend on external services when golden fixtures are sufficient.
- Keep fixtures small enough for fast CI/smoke runs.
- If new fixture files are added, update `docs/DEMO_FIXTURE_MANIFEST.md`.
## Sprint 1 usage
Codex should use golden data for:
- frontend map layer smoke display;
- backend fixture validation;
- dataset metadata extraction tests;
- future QA/QC regression tests;
- export contract tests.