plan: record the tiling-alternatives evaluation (SVG/raster/streaming-ABI)

[AdaWorldAPI]

Doc-only follow-up to #119: the operator asked for the worst-case comparison of the merged OSM1 design against SVG tiling (render load on server) and a further-compressed streaming-ABI wire (traffic burden). This lands the verdict in claude-notes/plans/2026-08-12-osm-vector-perf.md so the next session inherits the decision, not just the code:

• SVG tiling — dominated on every axis (server serialization + XML-bloated wire + client DOM rasterization); rejected without measurement.
• Server raster tiles — wire is O(pixels) (~15–40 KB/tile, density-immune) so it wins traffic at maximum city density, but only behind a CDN; on one Railway container every tile is rasterized per viewer, plus a rasterizer dep + style engine. Re-enters only with a CDN, as a hybrid.
• Merged osm basemap: wire the slab straight into the renderer (OSM1 binary tiles) #119 — the right point to measure from: mask + fold + LE encode server-side, 5.1× under JSON on the wire (measured, pre-gzip), 304s on revisit, ~150 native draws/frame client-side.
• Escalation path if city-zoom traffic still bites: OSM1-v2, not raster — i16 tile-relative + delta + zigzag-varint (post-simplification deltas are adjacent pixels) for another ~4–6×, paired with the bake-side .tiles sidecar (the genuine ndarray home; serving becomes a file-range read).

🤖 Generated with Claude Code

https://claude.ai/code/session_01NMeiLmtDKhomJNSo2ecbJw

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@AdaWorldAPI, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 36e1f879-559e-41fd-b197-91ccc69c2165

📥 Commits

Reviewing files that changed from the base of the PR and between fcfc5a0 and 62378c4.

📒 Files selected for processing (1)

• claude-notes/plans/2026-08-12-osm-vector-perf.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_0deaadc0-ca2b-49db-a323-7c020b5019a8)