Choosing Tegola to create vector tiles
summary
Tegola (Go) is chosen for production vector tiles because it compiles to one static binary, speaks HTTP, encodes protobuf MVT, and connects directly to Postgres for dynamic vector tiles from Postgres so edits can trigger targeted cache-busting instead of full re-generation. It scales both vertically and horizontally, uses all CPUs automatically during seeding, supports S3/backing stores and Docker, carries an MIT license, and proves reliable in production since v0.6 with gzip, cache tooling and CLI utilities. Front-end rendering uses OpenLayers.
AI-written summary · about
chapters (8)
- 0:00Introduction to vector tiles
- 1:51Vector tiles advantages
- 3:38Why use a tile server
- 7:32Choosing Tegola over others
- 10:18Tegola in production setup
- 14:10Tegola updates and benefits
- 15:11Static vs dynamic tile workflows
- 16:59Front-end tools and licensing
related talks
05mMVT Tiles and Autonomous Driving, and other non-UI usage
23mQGIS to Static Raster Tiles
21mPoint-in-polygon lookups with vector tiles: quick, effective, and no server needed!
05mCloud Optimised Geotiffs in TerriaJS
06mSwitching to PMTiles
46mCreating vector tilesets with the Mapbox Tiling Service
15mMaking maps work on mobile
37mStreamline data pipelines with incremental tileset updates in the Mapbox Tiling Service (MTS)