Add governed bathymetry profile workflow
This commit is contained in:
@@ -709,3 +709,26 @@ thematic rasters for space occupation, open space, population density, node
|
||||
value and service level. The digital soil map should follow the existing
|
||||
canonical vector persistence path. Watercourse/runoff additions remain in the
|
||||
roadmap but no longer precede these cross-domain gaps.
|
||||
|
||||
## Bathymetry, inland profiles and maritime scope
|
||||
|
||||
The official VHA Digital Atlas profile-point layer is the first operational
|
||||
bathymetry-adjacent source. GeoIntel requests an explicit bbox, clips against
|
||||
the exact persisted Area and retains VHA point identifiers, watercourse names,
|
||||
profile numbers, measurement dates, available structured depth/width values
|
||||
and official document URLs. Scanned documents remain evidence; missing fields
|
||||
are not filled by fabricated OCR output.
|
||||
|
||||
The following sources are audited but not yet operational:
|
||||
|
||||
- MDK Dieptemodel Belgisch Continentaal Plat/Noordzee: 20 x 20 m continuous
|
||||
raster in LAT, exposed through WCS/WMTS.
|
||||
- SPW bathymetry of navigable waterways and reservoir lakes: 0.5 m bed
|
||||
elevation and XYZ data in mDNG.
|
||||
- Port of Antwerp-Bruges periodic soundings: catalog candidate pending a
|
||||
stable public machine contract.
|
||||
|
||||
See `docs/BATHYMETRY_EXPANSION_ROADMAP.md`. TAW, LAT and mDNG remain separate
|
||||
until an authoritative vertical transformation is implemented and tested.
|
||||
The territorial sea, EEZ and continental shelf are separate scope layers and
|
||||
must be labelled according to their legal meaning.
|
||||
|
||||
Reference in New Issue
Block a user