MVT Tiles and Autonomous Driving, and other non-UI usage
summary
Argues that Map Vector Tiles (MVT) work for more than rendering and demonstrates a GitHub proof-of-concept repo with 51 replies and 14 comments that adds lane geometry, elevation profiles and per-vertex curvature metadata so self-driving stacks can read ahead instead of recalculating. Shows generation from Postgres and Elasticsearch, serving via a MapLibre-compatible tile server, and notes Valhalla-style routing tiles could reuse the same pipeline. Claims protobuf delta compression proves inadequate and calls for CLI tooling, dynamic tile serving, and 3D-support extensions to the MVT ecosystem.
AI-written summary · about
chapters (5)
related talks
19mChoosing Tegola to create vector tiles
30mStreamlined Map Development: Part 1
16mRaster tiles to vector tiles: how to cross the gulf
37mStreamline data pipelines with incremental tileset updates in the Mapbox Tiling Service (MTS)
45mA Pinch of SVG, a Note of 3D* and Maps
21mPoint-in-polygon lookups with vector tiles: quick, effective, and no server needed!
26mUpdates to the Mapbox Tiling Service: Faster, simpler, more cost-effective tiling
15mMaking maps work on mobile