Add governed orthophoto release preflight

2026-07-17 01:30:19 +02:00
parent 99f1e393cd
commit f48fe7b091
14 changed files with 1187 additions and 3 deletions
@@ -1300,6 +1300,26 @@ Settings: `ORTHOPHOTO_ENABLED`, `ORTHOPHOTO_WMS_URL`,
 `ORTHOPHOTO_CACHE_TTL_HOURS`. Keep the official HTTPS URL and 1 m profile
 unless a separately verified deployment/model profile requires a change.

+Before a future `most_recent` source release is allowed into a governed pixel
+stage, run the metadata-only preflight for the exact intended rectangle:
+
+```bash
+docker exec geointel python /app/scripts/orthophoto_release_preflight.py \
+  --project-id 82a85913-c522-45d7-84a1-02b393d89e55 \
+  --api-url http://127.0.0.1:8000/api/v1 \
+  --bbox 5.110 51.180 5.117 51.185 \
+  --refresh-catalog
+```
+
+The command reads canonical API envelopes, exact official WMS capabilities,
+WCS `DescribeCoverage` and at most 64 queryable flight-day points. It never
+requests raster pixels or mutates application/storage state. Only
+`staging_permitted=true` may feed a future separate staging command. `current`,
+remote-older, mixed/incorrect flight years and legacy local values such as
+`most_recent_at_2026-07-15` remain non-stageable. The report's point grid is
+flight-date evidence; complete selected-area coverage comes from containment
+inside the official 15 cm WCS raster domain.
+
 ## Governed DHMV terrain acquisition

 `GET /api/v1/projects/{project_id}/datasets/dhmv/products` exposes the fixed