Streamline data pipelines with incremental tileset updates in the Mapbox Tiling Service (MTS)
summary
Mapbox Tiling Service now accepts incremental: true recipes so vector tilesets update by sending only changed features instead of reprocessing everything. The demo uses the tile-sets CLI, a Node script that emits gojsonl features with a unique ID, uploads a tileset, then uploads a change set and publishes it. Out of ~815 bike-share stations the change set contains 263 changed features (updates use _action fields: update/create/delete), the map reflects the new num_bikes_available after publish, and processing is much faster and cheaper than full reprocess.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:26What are vector tiles
- 3:13MTS and incremental updates
- 6:01Demo overview
- 7:09Preparing the data
- 11:48Setting up MTS CLI
- 12:51Creating tile set source
- 13:35Configuring recipe for incremental updates
- 15:19Publishing the tile set
- 16:45Visualizing the tile set
- 19:38Preparing incremental update
- 22:25Uploading the change set
- 23:30Publishing the change set
- 27:04Verifying the update
- 30:39Closing and Q&A
related talks
16mRaster tiles to vector tiles: how to cross the gulf
15mHave you checked your vector tiles lately?
05mMVT Tiles and Autonomous Driving, and other non-UI usage
17mBoosting Map Performance with Mapbox and Flutter
06mSwitching to PMTiles
19mEstablishing a Serverless Dynamic Tile Generation Workflow
15mMaking maps work on mobile
21mPoint-in-polygon lookups with vector tiles: quick, effective, and no server needed!