Add governed bathymetry profile workflow
This commit is contained in:
@@ -360,3 +360,18 @@ the composite expression index
|
||||
It supports exact preclipped municipality selection without changing the
|
||||
canonical `vector_features` schema or introducing operator-specific tables.
|
||||
Free rectangle queries continue to use the geometry GiST index.
|
||||
|
||||
## Bathymetry profile persistence
|
||||
|
||||
VHA profile points require no new table or migration. The immutable GeoJSON
|
||||
artifact is stored as one normal reference `datasets` row and
|
||||
`dataset_versions` row; each exact point is a normal `vector_features` row with
|
||||
EPSG:4326 geometry and source properties. Existing dataset, source-feature and
|
||||
GiST indexes support selection.
|
||||
|
||||
Profile measurement dates remain feature properties because a bounded Dataset
|
||||
can contain many historical campaigns. No artificial Dataset `observed_at` or
|
||||
temporal series is assigned. A future bed raster remains file/object storage
|
||||
plus Dataset metadata, not raster-in-database storage. Any national/maritime
|
||||
extension keeps source vertical datum, survey epoch and Area partition
|
||||
explicit and does not create a provider-specific shadow schema.
|
||||
|
||||
Reference in New Issue
Block a user