feat: map the complete municipality of Mol

2026-07-14 05:35:15 +02:00
parent f757a527cf
commit 490325e0cd
20 changed files with 1027 additions and 62 deletions
@@ -1131,6 +1131,32 @@ thresholds without changing the script. The main readiness gate checks this
 script's syntax; run it explicitly against Docker/PostGIS when validating a
 live deployment.

+## Complete Mol municipality workspace
+
+Provision the official municipality boundary and every GRB GBG building that
+intersects it through the existing project, area, dataset and vector-feature
+persistence paths:
+
+```bash
+docker exec -it geointel python3 \
+  /app/scripts/provision_mol_municipality_workspace.py
+```
+
+The command queries `VRBG/Refgem` for municipality `Mol`, verifies NIS code
+`13025`, follows every `GRB/GBG` pagination link and clips the resulting
+buildings to the official boundary. It writes source artefacts and a checksum
+manifest below `/app/storage/operator-data/mol-municipality`, then creates or
+reuses `Mol Municipality Workbench` and imports both layers through the public
+API. It never writes directly to PostGIS and never runs implicitly at startup.
+
+Completed artefacts and ready datasets are reused on a repeat run. Use
+`--force` only when an operator deliberately wants to refetch and replace the
+local source artefacts. Use `--fetch-only` to prepare and inspect the manifest
+without changing application persistence. The internal API default is
+`http://127.0.0.1:8000`, avoiding proxy timeouts during the large vector
+import; override it with `--base-url` when running outside the all-in-one
+container.
+
 ## Tower deployment

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