Add Belgium and North Sea coverage foundation
This commit is contained in:
@@ -987,6 +987,30 @@ it does not create a derived dataset.
|
||||
|
||||
## Geographic scope provisioning
|
||||
|
||||
The release-candidate national foundation is provisioned explicitly:
|
||||
|
||||
```bash
|
||||
docker exec geointel python /app/scripts/provision_belgium_north_sea_scope.py
|
||||
```
|
||||
|
||||
Use `--fetch-only` to validate official NGI AdminVector, RBINS marine
|
||||
reporting units and the Belgian Marine Spatial Plan 2026-2034 without changing
|
||||
application persistence. The normal command creates or reuses
|
||||
`Belgium and North Sea Workbench`, persists Belgium, all three regions,
|
||||
territorial sea, EEZ and continental shelf as Areas, and uploads six
|
||||
checksum-bound reference Datasets through `DatasetService`.
|
||||
|
||||
The operator has a fixed URL/layer allowlist, verified TLS, archive and
|
||||
response-size limits, safe ZIP extraction, complete WFS pagination and
|
||||
immutable artifact checksums. It does not run at startup and does not write
|
||||
directly to `vector_features`.
|
||||
|
||||
`GET /api/v1/external/coverage/catalog` exposes audited national source
|
||||
contracts. `POST /api/v1/external/coverage/resolve` intersects a drawn bbox
|
||||
with persisted legal/administrative Areas and reports a split zone/theme
|
||||
matrix. `operational` requires a matching `ready` Dataset; integration without
|
||||
materialized data is only `partial`.
|
||||
|
||||
The explicit operator command below provisions the official 28-municipality
|
||||
Vlaamse vervoerregio Kempen boundary foundation:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user