feat(scope): make Belgium and North Sea operational default
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s

This commit is contained in:
Codex
2026-07-22 02:11:48 +02:00
parent 46884cbbc9
commit 0aff8e3b8c
61 changed files with 2499 additions and 194 deletions
+11 -5
View File
@@ -15,9 +15,12 @@ runtime source of truth.
- Buildings, population, terrain, imagery, nature, agriculture, soil and flood
themes may report `partial`, `not_configured` or `unsupported` outside the
materialized source partitions. The UI and exports retain that state.
- Belgian North Sea planning/reporting boundaries are materialized. Continuous
authoritative bathymetry acquisition remains `not_configured`; VHA profile
observations are not presented as a seabed model or water volume.
- Belgian North Sea planning/reporting boundaries are materialized. Bounded
strict-TLS MDK WCS acquisition is implemented but stays disabled until the
operator enables `MDK_BATHYMETRY_ACQUISITION_ENABLED` with a coverage id that
the live readiness probe advertises. Until then the theme reports
`not_configured`; VHA profile observations are not presented as a seabed
model or water volume.
- Official endpoints can be temporarily unavailable. Bounded acquisition fails
closed and never substitutes fixture or fabricated production data.
@@ -47,8 +50,11 @@ runtime source of truth.
trained general model for all Belgian objects or themes.
- PyTorch and Ultralytics are present only in the AI image. No model weights
auto-download. A missing local model reports unavailable.
- Real segmentation models remain placeholders; fixture segmentation is
explicit-only. No SAM or YOLO-seg dependency is installed.
- Local YOLO-seg and SAM segmentation are implemented through the ultralytics
interface but stay `not_configured` until the operator points
`YOLO_SEG_MODEL_PATH`/`SAM_MODEL_PATH` to existing local weights and enables
them explicitly. GeoIntel never downloads segmentation weights automatically;
fixture segmentation remains explicit-only.
## Operations