Global/MVT acceptance tests: the rest of the config-level checks #125
Labels
No labels
blocked
claude-wip
map-report
map:is
map:se
needs-review
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
art/ismap#125
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of the #115 plan: the config-level (global) acceptance tests landed in #119 with two (every map_* table's geom column has a gist index; the densest z5 tile stays under 8 MB). This issue tracks the rest of the global/MVT checks the review comment asked for ("check that the MVT is sensible"). The general instruction from #115: a test is a sentence citing the R-number where relevant, a SQL query whose first column is the pass/fail boolean, and a timeout from {1, 10, 100, 1000}.
Candidates:
Result is in #140 — #140; the review note is the PR description. Shipped: R30 floor/ceiling via the zxy_map_* functions, per-country z5/z8 tile budgets, all-ocean empty check, index coverage extended to ismap_*. The MVT attribute-set (R121 decoded-tile) half cannot be a SQL test (MVT is protobuf, no decoder in Postgres) — recorded here and filed as #139 (mapsrv-side).