Add governed bathymetry profile workflow
This commit is contained in:
@@ -1882,3 +1882,30 @@ boundary artifact. Defaults cap each municipality at 30,000 source features and
|
||||
the assembled snapshot at 300,000 features. It never truncates silently, never
|
||||
writes `vector_features` directly and never turns the single 2025 state into a
|
||||
fabricated historical series.
|
||||
|
||||
## Mol VHA bathymetry profiles
|
||||
|
||||
Provision and verify the official profile points for the exact persisted Mol
|
||||
Area:
|
||||
|
||||
```bash
|
||||
docker exec geointel python /app/scripts/provision_mol_bathymetry_profiles.py
|
||||
```
|
||||
|
||||
Use `--force` only for a deliberate fresh provider snapshot. The command finds
|
||||
`Mol Municipality Workbench` and `Gemeente Mol`, calls the canonical
|
||||
bathymetry acquisition endpoint and then verifies that vector selection count
|
||||
and semantic metrics match the persisted Job result. It never writes directly
|
||||
to PostGIS.
|
||||
|
||||
For another approved workspace or Area:
|
||||
|
||||
```bash
|
||||
python scripts/provision_mol_bathymetry_profiles.py \
|
||||
--base-url http://127.0.0.1:8000 \
|
||||
--project-name "Project name" \
|
||||
--area-name "Area name fragment"
|
||||
```
|
||||
|
||||
The output is a point dataset with historical evidence. It is not a continuous
|
||||
water-bottom raster and cannot calculate current water volume.
|
||||
|
||||
Reference in New Issue
Block a user