Add governed Statbel release promotion
This commit is contained in:
@@ -1073,6 +1073,46 @@ excluded from spatial metrics. The 2025 REDEGEO contract deliberately compares
|
||||
explicit municipality fields; it does not assume that `CD_SECTOR` still starts
|
||||
with the current `CD_REFNIS` after municipal mergers.
|
||||
|
||||
Future official editions use the separate four-phase release coordinator. The
|
||||
project id must belong to `Kempen Regional Workbench`:
|
||||
|
||||
```bash
|
||||
docker exec geointel python /app/scripts/manage_statbel_population_release.py plan \
|
||||
--project-id <KEMPEN_PROJECT_ID> \
|
||||
--api-url http://127.0.0.1:8000/api/v1 \
|
||||
--refresh-catalog
|
||||
|
||||
docker exec geointel python /app/scripts/manage_statbel_population_release.py stage \
|
||||
--project-id <KEMPEN_PROJECT_ID> \
|
||||
--api-url http://127.0.0.1:8000/api/v1 \
|
||||
--confirm-edition <YEAR_FROM_PLAN> \
|
||||
--confirm-layout <LAYOUT_FROM_PLAN>
|
||||
|
||||
docker exec geointel python /app/scripts/manage_statbel_population_release.py review \
|
||||
--project-id <KEMPEN_PROJECT_ID> \
|
||||
--api-url http://127.0.0.1:8000/api/v1 \
|
||||
--confirm-edition <YEAR_FROM_PLAN> \
|
||||
--confirm-layout <LAYOUT_FROM_PLAN> \
|
||||
--confirm-plan-sha256 <SHA256_FROM_STAGE> \
|
||||
--approve --reviewer "<OPERATOR_NAME>" \
|
||||
--review-note "Schema, totalen, ZZZZ en geometrieherstel nagekeken"
|
||||
|
||||
docker exec geointel python /app/scripts/manage_statbel_population_release.py apply \
|
||||
--project-id <KEMPEN_PROJECT_ID> \
|
||||
--api-url http://127.0.0.1:8000/api/v1 \
|
||||
--confirm-edition <YEAR_FROM_PLAN> \
|
||||
--confirm-layout <LAYOUT_FROM_PLAN> \
|
||||
--confirm-plan-sha256 <SHA256_FROM_STAGE> \
|
||||
--confirm-review-sha256 <SHA256_FROM_REVIEW>
|
||||
```
|
||||
|
||||
`plan` is read-only and creates no file. `stage` always uses bounded fresh
|
||||
downloads and `--fetch-only`; `review` imports nothing; `apply` revalidates
|
||||
the current catalog, plan, review, source archives, preflight manifest and
|
||||
derived snapshot before using the existing upload API. An already-current
|
||||
release cannot be staged. A repeated successful apply resolves the existing
|
||||
Dataset through complete paginated lookup rather than creating a duplicate.
|
||||
|
||||
Historical land-use work can be bounded explicitly:
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user