Add governed Wallonia and Brussels orthophotos
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:
Jens
2026-07-26 22:02:10 +02:00
parent 0c328fd3d1
commit ec6f2d9061
17 changed files with 238 additions and 49 deletions
+13 -9
View File
@@ -365,16 +365,20 @@ Vector uploads remain stored as original files and are also persisted into `vect
### GET `/api/v1/projects/{project_id}/datasets/orthophoto/products`
Return the governed Digitaal Vlaanderen orthophoto product allowlist in the
canonical envelope. Every product reports its key, display/observation label,
temporal granularity, native resolution, colour mode, catalogue URL,
limitations and whether current configured-YOLO detection is allowed.
Return the governed Belgian orthophoto product allowlist in the canonical
envelope. It contains Digitaal Vlaanderen products plus `wallonia_latest`
(SPW) and `brussels_latest` (Paradigm UrbIS). Every product reports its key,
provider, coverage zone, display/observation label, temporal granularity,
native resolution, colour mode, catalogue URL, attribution, licence note,
limitations and whether configured-YOLO detection is allowed.
### POST `/api/v1/projects/{project_id}/datasets/orthophoto/acquire`
Explicitly acquire a bounded orthophoto selection from a governed official
Digitaal Vlaanderen WMS product. Arbitrary WMS URLs and layer names are not
accepted.
regional WMS product. Arbitrary WMS URLs and layer names are not accepted.
The regional products require the persisted project Areas `Wallonia` or
`Brussels-Capital Region` and reject a rectangle unless that Area covers at
least 99% of it.
```json
{
@@ -493,9 +497,9 @@ Safety contract:
reuse;
- WMS bytes are georeferenced to EPSG:31370 and persisted only through
`DatasetService`; no fetch runs on startup;
- only `most_recent` can enter the current configured-YOLO plus GRB-QA path;
historical products are visual evidence and are never validated against the
current GRB state;
- only `most_recent`, `wallonia_latest` and `brussels_latest` can enter the
configured-YOLO path; QA must use the matching regional reference source
(GRB, PICC or UrbIS). Historical products remain visual evidence;
- product periods such as `1979_1990` remain explicitly multi-year and are not
presented as exact annual observations.