fix: clarify population evolution semantics

2026-07-14 15:41:38 +02:00
parent 2fbefaa040
commit 986640d5b3
5 changed files with 64 additions and 5 deletions
@@ -7803,3 +7803,5 @@ Live deployment correction:
 - Vector upload persistence is now atomic across Dataset, DatasetVersion and VectorFeature rows, with storage cleanup on rollback. This prevents the failed-indexing orphan state observed during the live import.
 - Tower could read the historical WFS capabilities but its gateway rejected XML `FILTER` content embedded in a GET query. The operator now sends the same read-only WFS 2.0 GetFeature request as XML POST; a live two-feature forest page returned successfully before redeployment.
 - The 1778 edition classifies roads as `weg`, while later editions can use road subclasses. The exact server-side road filter now uses `weg*`, covering the documented class family without admitting unrelated themes.
+- Live population comparison returned 37,015 inhabitants for 2021 and 38,675 for 2025 (+1,660 / +4.48%). Full covered sectors now report exact source totals; only cut sectors are labelled area-weighted estimates.
+- Population sector identity is explicitly unstable across annual geometry editions, so source boundary/code changes are not presented as added/removed population objects.
@@ -42,6 +42,10 @@ Complete sectors use their published population total. A rectangle that cuts
 through a sector uses an explicitly labelled area-weighted estimate; the
 source does not justify a more precise intra-sector distribution.

+Statistical-sector codes and boundaries can change between editions. GeoIntel
+therefore compares population metrics but does not present sector additions,
+removals or boundary changes as population-object lineage.
+
 ### Mol historical land use

 `scripts/provision_mol_historical_landuse.py` uses the official Digitaal