feat: add official Kempen operating scope

2026-07-14 18:32:32 +02:00
parent e9c75b2fd6
commit bb7310e015
17 changed files with 1020 additions and 9 deletions
@@ -1254,6 +1254,38 @@ The 2013-2025 series is methodologically separate from the historical
 when both exist; it never calculates one continuous trend across those source
 families.

+## Official Kempen operational scope
+
+GeoIntel defines its regional `Kempen` workspace as the official Vlaamse
+`Vervoerregio Kempen`: 28 explicitly registered municipalities. This is a
+reproducible policy boundary, not a claim about the wider cultural,
+landscape or historical Kempen.
+
+Prepare and inspect the current VRBG union and all member boundaries without
+changing persistence:
+
+```bash
+docker exec -it geointel python3 /app/scripts/provision_geographic_scope.py \
+  --scope kempen-transport-region --fetch-only
+```
+
+Persist the complete scope foundation:
+
+```bash
+docker exec -it geointel python3 /app/scripts/provision_geographic_scope.py \
+  --scope kempen-transport-region
+```
+
+The command creates or reuses `Kempen Regional Workbench`, the regional Area,
+28 municipality Areas and two VRBG source datasets through the canonical API.
+Artifacts and checksums remain below
+`/app/storage/operator-data/geographic-scopes/kempen-transport-region`.
+Repeat runs are idempotent; `--force` refreshes today's source snapshot.
+
+This command provisions boundaries only. Regional buildings, population,
+land use, roads, water and parcels must be added by bounded source operators;
+missing themes remain unavailable and are never filled with synthetic values.
+
 ## Tower deployment

 Push the local branch to Gitea, then rebuild the Unraid/Tower Docker runtime: