feat: add official modern Mol land-use series

2026-07-14 17:51:24 +02:00
parent 8f27c5cc6f
commit b35f135fea
14 changed files with 1199 additions and 20 deletions
@@ -1212,9 +1212,47 @@ normal dataset API. Artifacts and manifests are retained below
 datasets; use `--force` only for an explicit source refresh. Use
 `--layers roads,water` or `--fetch-only` for a bounded operator run.

-The context provisioner does not add population or forest values. Those themes
-remain visibly unavailable until an authoritative/statistically appropriate
-source is imported; zero is never substituted for missing source data.
+The context provisioner itself does not add population or forest values. Use
+the dedicated official-source operators below; zero is never substituted for
+missing source data.
+
+## Official Mol temporal sources
+
+After the municipality workspace exists, provision official Statbel population
+and both independently modelled land-use series:
+
+```bash
+docker exec -it geointel python3 /app/scripts/provision_mol_population_history.py
+docker exec -it geointel python3 /app/scripts/provision_mol_historical_landuse.py
+docker exec -it geointel python3 /app/scripts/provision_official_landuse_timeseries.py
+```
+
+The modern land-use command checks the MercatorNet WCS capabilities, downloads
+only the Mol bounding subset of each 10 m `EPSG:31370` raster, validates the
+categorical integer grid, clips against the official boundary and polygonizes
+class `12` (`Bos`). Raw rasters, vector artifacts and checksum manifests are
+stored under `/app/storage/operator-data/official-landuse/mol`. The resulting
+2013, 2016, 2019, 2022 and 2025 vectors are uploaded through the canonical API
+as `department-omgeving:land-use:forest:mol`.
+
+Prepare and inspect artifacts without changing the database:
+
+```bash
+docker exec -it geointel python3 \
+  /app/scripts/provision_official_landuse_timeseries.py --fetch-only
+```
+
+Use `--force` only to refetch and rebuild local artifacts. Existing persisted
+snapshots remain immutable and are reused by year/series. To use the operator
+for another approved region, pass all scope inputs explicitly, for example
+`--boundary-path`, `--project-name`, `--area-name`, `--municipality-name`,
+`--nis-code`, `--scope-key` and `--output-dir`. GeoIntel does not infer what
+"Kempen" means administratively.
+
+The 2013-2025 series is methodologically separate from the historical
+1778/1873/1969 series. The map-first Evolution view exposes a series selector
+when both exist; it never calculates one continuous trend across those source
+families.

 ## Tower deployment