feat: add official Kempen operating scope
This commit is contained in:
@@ -935,6 +935,27 @@ the same bbox-selected FeatureCollection as a normal export record with
|
||||
`export_type="vector_selection_geojson"`. This creates a handoff artifact only;
|
||||
it does not create a derived dataset.
|
||||
|
||||
## Geographic scope provisioning
|
||||
|
||||
The explicit operator command below provisions the official 28-municipality
|
||||
Vlaamse vervoerregio Kempen boundary foundation:
|
||||
|
||||
```bash
|
||||
docker exec geointel python /app/scripts/provision_geographic_scope.py \
|
||||
--scope kempen-transport-region
|
||||
```
|
||||
|
||||
It reads current `VRBG/Refgem` boundaries, validates every registered name and
|
||||
NIS code, unions the regional geometry and creates one project, one regional
|
||||
Area, 28 municipality Areas and two source datasets through the public API.
|
||||
It never writes directly to PostGIS and does not run on startup. The persisted
|
||||
scope limitation explicitly distinguishes the transport-policy region from a
|
||||
cultural or landscape definition of Kempen.
|
||||
|
||||
Use `--fetch-only` for a source/geometry/checksum audit. The scope pass does
|
||||
not fetch thematic GRB, population or land-use data; those remain separate,
|
||||
bounded operator jobs.
|
||||
|
||||
## Temporal Mol data and evolution
|
||||
|
||||
Dataset uploads accept `temporal_series_key`, `observed_at`, `valid_from`,
|
||||
|
||||
Reference in New Issue
Block a user