Fix regional bathymetry context labels
This commit is contained in:
@@ -10141,3 +10141,16 @@ Validation:
|
||||
- The complete readiness gate passed: 927 backend tests, backend compilation,
|
||||
116 documented API routes, Alembic head `202607160001`, frontend TypeScript
|
||||
typecheck and the production Vite build.
|
||||
- Tower deployment passed container health, PostGIS 3.6, schema/index,
|
||||
Alembic, frontend proxy and icon checks. Live selection returned 828
|
||||
profiles from the exact Mol partition in 0.59 seconds, 8,806 profiles from
|
||||
22 intersecting partitions in 1.95 seconds and 128,913 profiles from all
|
||||
269 data-bearing partitions in 15.89 seconds.
|
||||
- The live partitioned export persisted a canonical 1,000-feature GeoJSON
|
||||
sample with `total_feature_count=8806`, all 22 contributing Dataset ids and
|
||||
`server_recomputed=true`.
|
||||
- Browser acceptance showed the complete Flemish metric result, all five
|
||||
configured structured depth/width measurements and the explicit 1,000-item
|
||||
display limit. A final shell follow-up replaces the representative
|
||||
municipality count with regional profile/partition totals and uses the
|
||||
end-user label `Vlaanderen (285 gemeenten)`.
|
||||
|
||||
Reference in New Issue
Block a user