Add governed SPW bathymetry analysis
This commit is contained in:
@@ -8,10 +8,11 @@ GeoIntel must distinguish three different questions:
|
||||
2. What is the continuous elevation of the bed at a specific survey epoch?
|
||||
3. What is the water depth or volume at a specific moment?
|
||||
|
||||
Only the first question is operational for Mol through the VHA cross-section
|
||||
profile layer. A bed model does not provide water depth without a compatible
|
||||
water-surface elevation. Flood-hazard maximum depth is a scenario result and
|
||||
must not be reused as current water level.
|
||||
The first question is operational for Flanders through VHA cross-section
|
||||
profiles. The second is now operational for bounded, surveyed Walloon
|
||||
waterways through the official SPW raster. A bed model does not provide water
|
||||
depth without a compatible water-surface elevation. Flood-hazard maximum depth
|
||||
is a scenario result and must not be reused as current water level.
|
||||
|
||||
## Governed source matrix
|
||||
|
||||
@@ -19,7 +20,7 @@ must not be reused as current water level.
|
||||
| --- | --- | --- | --- | --- |
|
||||
| VMM VHA Digital Atlas | Flanders | Point locations, structured profile fields, PDF evidence | Document-specific | Operational, bounded vector acquisition |
|
||||
| MDK Belgian Continental Shelf model | Belgian North Sea | Continuous 20 x 20 m bathymetric raster | LAT | Available, not integrated |
|
||||
| SPW navigable waterways and reservoir lakes | Wallonia | 0.5 m bed-elevation raster and XYZ cloud | mDNG | Available, not integrated |
|
||||
| SPW navigable waterways and reservoir lakes | Wallonia | 0.5 m bed-elevation raster and XYZ cloud | mDNG | Operational, pinned operator archive and bounded COG |
|
||||
| Port of Antwerp-Bruges publications | Port survey areas | Periodic soundings | Product-specific | Catalog candidate |
|
||||
|
||||
VHA contains approximately 129,643 profile points across Flanders at the
|
||||
@@ -135,7 +136,10 @@ bed evolution.
|
||||
**Probe implemented. Acquisition blocked because the live endpoint fails
|
||||
strict hostname validation and does not expose usable capabilities.**
|
||||
4. Implement SPW download staging and vertical-datum metadata validation.
|
||||
**Done: pinned official ZIP, safe `/vsizip/` access, bounded COG,
|
||||
DatasetService persistence, map overlay and mDNG selection metrics.**
|
||||
5. Add maritime boundaries as separate authoritative scope layers.
|
||||
**Done for the Belgian territorial sea, EEZ and continental shelf.**
|
||||
6. Add cross-source vertical-datum transformation only with authoritative
|
||||
grids/parameters and uncertainty tests.
|
||||
7. Add volume only after a compatible measured or modeled water-surface source
|
||||
|
||||
Reference in New Issue
Block a user