Jens
faeb58ef6d
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
# ADR-003 — GRB as Authoritative Reference Dataset
|
|
|
|
## Status
|
|
Accepted for V1 research and implementation planning.
|
|
|
|
## Context
|
|
The Basiskaart Vlaanderen / GRB is a professional Flemish geospatial reference dataset. GeoIntel is scoped to the Kempen, so Flemish official data is highly relevant.
|
|
|
|
## Decision
|
|
Treat GRB as the primary QA/QC reference where available. Use it for building/reference geometry validation and later for roads, water, and other base-map objects.
|
|
|
|
V1 integration strategy:
|
|
|
|
1. Implement a GRB provider abstraction.
|
|
2. Start with WFS or downloaded sample/cache depending on practical availability.
|
|
3. Normalize GRB features into a common `reference_features` model.
|
|
4. Compare AI detections against GRB with IoU/overlap metrics.
|
|
|
|
## Consequences
|
|
GeoIntel becomes more relevant to real Flemish GeoAI workflows than a generic OSM-only demo. GRB validation becomes a portfolio killer feature.
|
|
|
|
## Non-goals
|
|
Do not block the entire build on live GRB integration. Provide fixtures and provider interfaces first, then connect real GRB when endpoint details are tested.
|