Aggregate regional bathymetry partitions
This commit is contained in:
@@ -50,14 +50,19 @@ the provider and the application. A regional logical layer may group complete
|
||||
partitions, but each Dataset retains its Area id, query URLs, checksums, exact
|
||||
count and measurement-date range.
|
||||
|
||||
Before regional activation:
|
||||
Regional activation now uses the complete checksum-bound municipality
|
||||
manifest. The Map flow chooses the exact Area partition for a municipality and
|
||||
uses a bounded multi-Dataset PostGIS query for regional rectangles or the
|
||||
complete Flanders Area. GeoJSON remains limited to 1,000 rendered features;
|
||||
counts and configured metrics cover the complete spatial result. Individual
|
||||
profile dates remain authoritative and no Dataset-level survey date is
|
||||
fabricated.
|
||||
|
||||
Remaining operational follow-up:
|
||||
|
||||
- add a governed Flanders boundary manifest and partition coordinator;
|
||||
- prove idempotent resume and no duplicate VHA `OBJECTID` within a partition;
|
||||
- benchmark PostGIS point selection and viewport delivery;
|
||||
- add freshness/version probing for the VHA MapServer;
|
||||
- keep individual profile dates instead of fabricating one Dataset
|
||||
`observed_at`.
|
||||
- keep selection-performance evidence as the profile inventory grows;
|
||||
- retain explicit no-profile municipalities in every refreshed manifest.
|
||||
|
||||
## Tier 3: Belgium
|
||||
|
||||
@@ -123,7 +128,9 @@ bed evolution.
|
||||
1. Operate and validate the Mol VHA profile Dataset and map flow. **Done.**
|
||||
2. Add VHA municipal partition orchestration for Flanders. **Done and live:
|
||||
285/285 municipality partitions accounted for, 269 with data, 16 explicit
|
||||
no-profile results, 128,913 profile points and zero failures.**
|
||||
no-profile results, 128,913 profile points and zero failures. Regional
|
||||
selection and export now aggregate the latest complete manifest in
|
||||
PostGIS.**
|
||||
3. Implement a bounded MDK WCS probe, then acquisition behind live evidence.
|
||||
**Probe implemented. Acquisition blocked because the live endpoint fails
|
||||
strict hostname validation and does not expose usable capabilities.**
|
||||
|
||||
Reference in New Issue
Block a user