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/DATABASE_IMPLEMENTATION_PLAN.md
+9
View File
@@ -291,6 +291,15 @@ which creates the ordinary annual `datasets`, `dataset_versions` and
year remains idempotent and previous annual snapshots are never updated or
deleted.
SPW bathymetry also requires no migration. The immutable official ZIP and
bounded operator COG are filesystem artifacts. A successful API upload creates
an ordinary raster `Dataset` and `DatasetVersion`; raster values stay in the
versioned GeoTIFF rather than PostGIS. `source_metadata` retains EPSG:3812,
mDNG, survey period, source checksum and bounded extent, while
`provenance_metadata` retains the official URL, archive member, derived
checksum and selection geometry/hash. Analysis never writes metric rows and
never converts the vertical datum implicitly.
Definitive ALZ release management uses the same persistence boundary and adds
no migration or release table. Catalog planning, staged archive/GeoJSON,
crop-code evidence and named review live on the filesystem. Only an approved