Files
geointel/geointel/docs/DATAVINDPLAATS_SOURCE_ROADMAP.md
T
Jens 21015757bd
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s
Update
2026-07-27 23:13:09 +02:00

10 KiB

Datavindplaats Source Roadmap

This roadmap was rebalanced on 2026-07-16 after a platform-wide review of public Vlaamse Datavindplaats sources. Water is one analysis domain, not the organizing principle of GeoIntel. The target product remains simple:

  1. select an area on the map;
  2. choose a subject;
  3. read source-correct measurements;
  4. compare persisted observations when a valid time series exists;
  5. inspect provenance and export evidence.

Every source below is either already operational or has an official public catalog/service record. A catalog entry is not the same as an implemented provider. GeoIntel may label a source operational only after governed import, CRS/unit validation, persisted provenance and selection-metric tests pass.

Current Operational Foundation

  • Space and buildings: GRB building/road context, Buildings and Addresses Register for Mol, official land-use snapshots and orthophotos.
  • Nature and agriculture: regional BWK/Natura 2000 state 2025 and definitive agricultural parcel editions.
  • Soil and relief: bounded DHMV DTM/DSM acquisition with height, relief and slope metrics.
  • Climate and environment: VMM flood-hazard scenarios and station-bound Waterinfo series.
  • Historical context: official 1778, 1873 and 1969 mapped land-use classes and modern land-use editions where persisted.

The cross-domain Wave 1 implementation now adds population/services, modeled accessibility, space occupation, open space and the DOV soil classes to Mol. Regional completeness beyond Mol remains a controlled operator rollout rather than an automatic startup fetch.

Domain A - Space, Buildings And Economy

Highest-value additions

Domain B - Nature And Agriculture

  • BWK / Natura 2000 state 2025 is operational regionally. It remains a current state, not an invented annual nature series.
  • Open geodata agricultural parcels is operational as annual declared-use area. Parcel identities remain intentionally unstable between editions.
  • Open-space and land-use rasters complement these object layers. Metrics must not add overlapping classification surfaces as if they were disjoint.

Domain C - Soil And Relief

  • Digital soil map: soil types
    • Vector soil polygons in EPSG:31370.
    • Measure hectares by soil type, texture and drainage class.
    • Historical field mapping from 1949-1971 is baseline evidence, not a claim about current parcel drainage.
  • Potential soil erosion per parcel 2023
    • Modelled potential erosion, not observed damage.
    • Combine with agricultural use and DHMV slope only while keeping each source and method explicit.
  • Physical system map
    • Coarse interpretive landscape zones for context, not parcel evidence.

Domain D - Mobility And Accessibility

Accessibility scores are not live timetable reliability. Network length and proximity are separate measurements from modeled accessibility.

Domain E - Population And Services

Domain F - Climate And Living Environment

Implementation Waves

Wave 1 - Cross-domain area profile

Implement one governed Mercator thematic-raster registry instead of separate ad-hoc provider code. Its fixed allowlist should first cover:

  1. space occupation 2025;
  2. open space 2022;
  3. population density 2019;
  4. node value 2022;
  5. total service level 2022.

The existing Dataset, DatasetVersion, Job and raster-selection architecture is sufficient. Each product needs a fixed coverage id, native unit/classes, observation date, resolution, legend, permitted aggregations and caveat. No arbitrary WCS URL or layer name may enter the API.

In parallel, add the digital soil map through the existing canonical vector DatasetService/VectorFeatureService path. This immediately gives every drawn rectangle a balanced profile across space, soil, people, services and accessibility.

Implementation status on 2026-07-16: complete for Mol. The five raster products use one fixed MercatorNet registry and the soil map uses the official bodemkaart:bodemtypes DOV WFS. All outputs are persisted through existing Dataset services, carry source year/period and limitations, and are selectable on the map. Regional raster provisioning is supported per persisted municipality; regional soil partitioning remains the next scale-out step.

Wave 2 - Economic and mobility objects

Add governed vector operators for business parks, Hoppinpoints and cycle highways. Persist provider output only through DatasetService and VectorFeatureService. Selection metrics should be area for business parks, counts/proximity for Hoppinpoints and length/status for cycle highways.

Wave 3 - Living environment

Add heat and air-quality sources only after their spatial scale and temporal comparability are explicit. Then add VHA/runoff as hydrological context. Do not derive missing volume, exposure or health outcomes.

Wave 4 - Historical completeness

Search for comparable earlier editions of every accepted product. A valid series requires compatible classes and methods, explicit observation dates and persisted versions. When methods differ, show side-by-side evidence rather than a fabricated trend.

Build Governed Flemish Thematic Raster Registry - Wave 1. It is the best next platform step because one bounded, allowlisted acquisition architecture unlocks spatial planning, open space, population, accessibility and services without changing the database schema or creating one-off provider paths.

Acceptance requires:

  • product registry and honest capability metadata;
  • bounded WCS acquisition through the existing Job/Dataset flow;
  • exact Area/rectangle selection with product-specific metrics;
  • MapLibre image overlay and simple legend;
  • source date, unit, method and caveat in every result;
  • no startup/browser fetch and no fabricated historical observations;
  • focused GIS, API, persistence and frontend tests;
  • one Mol live smoke before regional provisioning.