Aggregate regional bathymetry partitions

2026-07-17 17:08:35 +02:00
parent 24247746c1
commit 4fd6c06f5c
17 changed files with 661 additions and 29 deletions
@@ -2111,6 +2111,26 @@ accounting sets `partitioned_source_audit=true` and
 `regional_partitions_complete=true`; partial operator runs remain hidden at
 regional scope.

+### POST `/api/v1/projects/{project_id}/datasets/bathymetry/profiles/partitions/select`
+
+Runs one bounded spatial selection across the latest complete `flanders`
+VHA manifest. The request reuses `VectorSelectionRequest`: EPSG:4326 bbox,
+optional persisted Area and a result limit of at most 1,000 features.
+
+The backend first rejects incomplete or inconsistent manifests, selects only
+municipality Dataset partitions whose recorded bounds overlap the request and
+then queries their persisted `vector_features` with one PostGIS intersection.
+When the Area is a municipality, only that exact Area partition is eligible.
+A regional Area can combine all intersecting partitions without treating one
+municipality Dataset as representative regional data.
+
+The canonical response extends the ordinary vector-selection result with
+`partition_count`, `available_partition_count`, `partition_scope_key`,
+`source_name` and the contributing `dataset_ids`. GeoJSON is capped by the
+request limit, while `total_feature_count` and all configured depth/width
+metrics are calculated across the complete spatial result. Empty municipalities
+return an empty, honest result. No provider request occurs during analysis.
+
 Future provider output continues to use DatasetService and, for vectors,
 VectorFeatureService. Arbitrary service URLs, browser-side fetches, insecure
 TLS bypasses and startup downloads remain forbidden.