Jens/geointel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add governed SPW bathymetry analysis
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
Details
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
Details
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
Codex
2026-07-19 04:07:01 +02:00
parent ae3d3dc634
commit 70c5e34ecf
37 changed files with 1852 additions and 102 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/STORAGE_ARCHITECTURE.md
+17
View File
@@ -142,6 +142,23 @@ Dataset/DatasetVersion plus PostGIS `vector_features` through the canonical
persistence services. Temporary standalone preflight output does not create a
database record and may be removed explicitly after operator review.
SPW bathymetry follows the same immutable-source/derived-dataset separation:
```text
storage/operator-evidence/spw-bathymetry/2023-05-23/
raw/BATHY_50CM_ALTITUDE_DNG_GEOTIFF_3812.zip
derived/spw_bathymetry_{selection_hash}_3812.tif
```
The raw ZIP is pinned by official URL and SHA-256 and is never extracted as an
8+ GiB working tree. Rasterio/GDAL reads the official GeoTIFF through
`/vsizip/`; the operator writes a bounded compressed COG and uploads that COG
through DatasetService. The queryable file therefore remains an ordinary
versioned raster Dataset. Source URL, archive/member checksum, selection
geometry/hash, survey period, EPSG:3812 and mDNG semantics are retained in
source/provenance metadata. PNG map overlays are derived responses and are not
authoritative storage.
Governed release-decision evidence is separate from the source artifacts:
```text