Add Flemish bathymetry partition workflow
This commit is contained in:
@@ -1728,3 +1728,29 @@ The Dataset exposes profile count and nullable structured depth/width metrics.
|
||||
It does not claim a continuous bed model, current depth or volume. Use
|
||||
`scripts/provision_mol_bathymetry_profiles.py` for the canonical Mol operator
|
||||
flow.
|
||||
|
||||
Provision the complete current Flemish land scope and then run the resumable
|
||||
VHA municipality coordinator:
|
||||
|
||||
```bash
|
||||
docker exec geointel python /app/scripts/provision_flanders_geographic_scope.py
|
||||
docker exec geointel python /app/scripts/provision_flanders_bathymetry_profiles.py
|
||||
```
|
||||
|
||||
The first command discovers all current VRBG RefGem municipalities, validates
|
||||
a 270..300 safety range and persists their exact Areas. The second writes its
|
||||
manifest after every partition. Repeating it reuses completed source
|
||||
identities; `--force` deliberately refreshes them. A partial `--members` or
|
||||
`--max-partitions` run never marks regional coverage complete.
|
||||
|
||||
Inspect the MDK North Sea WCS without downloading coverage:
|
||||
|
||||
```bash
|
||||
docker exec geointel python /app/scripts/probe_mdk_bathymetry.py
|
||||
```
|
||||
|
||||
Exit code `0` means verified capabilities; `2` means a truthful blocked
|
||||
readiness state such as TLS or endpoint failure. Runtime controls are
|
||||
`MDK_BATHYMETRY_PROBE_ENABLED`, `MDK_BATHYMETRY_WCS_URL`,
|
||||
`MDK_BATHYMETRY_PROBE_TIMEOUT_SECONDS` and
|
||||
`MDK_BATHYMETRY_PROBE_MAX_RESPONSE_MB`. TLS verification cannot be disabled.
|
||||
|
||||
Reference in New Issue
Block a user