feat: make Mol explorer map-first
This commit is contained in:
@@ -1196,6 +1196,26 @@ without changing application persistence. The internal API default is
|
||||
import; override it with `--base-url` when running outside the all-in-one
|
||||
container.
|
||||
|
||||
After the municipality boundary/building workspace exists, provision the
|
||||
official GRB road, water and parcel context layers:
|
||||
|
||||
```bash
|
||||
docker exec -it geointel python3 \
|
||||
/app/scripts/provision_mol_context_layers.py
|
||||
```
|
||||
|
||||
The command reads `Wegsegment` for roads, `WTZ`/`WLAS`/`WGR` for water and
|
||||
`ADP` for parcels from the Digitaal Vlaanderen OGC API, clips every geometry
|
||||
to the persisted official Mol boundary and uploads each artifact through the
|
||||
normal dataset API. Artifacts and manifests are retained below
|
||||
`/app/storage/operator-data/mol-context`. Repeat runs reuse both artifacts and
|
||||
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.
|
||||
|
||||
## Tower deployment
|
||||
|
||||
Push the local branch to Gitea, then rebuild the Unraid/Tower Docker runtime:
|
||||
|
||||
Reference in New Issue
Block a user