Files
geointel/docs/DATA_COVERAGE_STATUS.md
T
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
Initial public release
2026-08-31 21:56:53 +02:00

4.0 KiB

GeoIntel data coverage status

Status date: 2026-07-22

This document is the operational interpretation of the source registry. It does not replace the legal/source provenance stored with each Dataset.

Status labels in the workbench

  • Beschikbaar: a persisted Dataset covers the selection and can be queried immediately.
  • Automatisch: an audited official source contract exists. GeoIntel obtains and persists only the bounded selection when analysis starts.
  • Alleen huidig: one official observation exists, so no honest evolution can be calculated.
  • Ontbreekt: no operational source contract covers that theme and zone.

Automatisch therefore does not mean unavailable or simulated. It means that the source is materialized on first use and reused afterwards. AI training cannot replace missing official GIS observations and is not used to fabricate coverage or historical dates.

Current operational coverage

Zone Persisted or bounded operational sources Historical comparison
Belgium NGI administrative boundaries; Statbel population/statistical sectors Statbel population 2021-2025
Flanders GRB buildings, roads, water and parcels; DHMV terrain/surface; VMM flood scenarios; BWK/Natura 2000; DOV soil; policy rasters for space, open space, accessibility and services; agriculture and orthophoto where governed Population 2021-2025; land-use/land-cover series where retained; agriculture editions; historical maps/orthophotos where the selected product has a real observation date
Wallonia Bounded PICC buildings, roads and hydrography; legal SPW flood-hazard polygons; bounded WALOUS 2018/2020/2023 land-cover analysis; bounded SPW MNT 2021-2022 terrain analysis in DNG; governed SPW bed-elevation/bathymetry products Governed WALOUS land-cover area metrics for 2018-2023 with the 2018 crosswalk/methodology limitation; no general cross-theme regional history yet
Brussels Bounded UrbIS buildings, street axes, cadastral parcels and Land Cover blocks; official FO/GB blocks provide forest/park area and WB blocks provide permanent water area No general cross-theme regional history yet; the live WFS has no per-feature observation date
Belgian North Sea RBINS reporting units; Marine Spatial Plan 2026-2034; governed MDK bathymetry only when runtime acquisition is explicitly configured No multi-epoch bathymetry or marine-plan trend yet

Mol and the Kempen are golden regression areas. Their persisted partitions are not national coverage. A partition is only selected when its recorded bbox_epsg4326 intersects the drawn rectangle; otherwise GeoIntel uses an applicable bounded official source or reports the theme as unsupported.

Priority coverage gaps

  1. Add a common Belgium-wide topographic baseline with normalized theme semantics across NGI, Flanders, Wallonia and Brussels.
  2. Govern comparable Walloon and Brussels historical editions before exposing evolution for buildings, roads, land cover, soil, elevation or flood risk.
  3. Add nationally comparable land-cover history with explicit class crosswalks and uncertainty; never compare incompatible legends silently.
  4. Add multi-epoch marine bathymetry and survey-footprint metadata before presenting seabed evolution.
  5. Expand persisted raster partition manifests beyond the regression regions only where repeated use justifies caching; bounded acquisition remains the default for one-off selections.
  6. Add source freshness probes only for publishers with stable official edition contracts. Do not infer a new observation from an import or HTTP date.

Acceptance rules for a new source

A source is visible as operational only after its licence, authority, observation time, CRS, spatial coverage, schema, units and limitations are validated. It must persist through DatasetService and the canonical feature or raster flow, retain provenance/checksums, return semantic metrics, and have a selection-level regression test. Historical support additionally requires at least two distinct, methodologically comparable official observation dates.