Vector Tiles
- Dominant language
- JavaScript
- Stars
- 15.7k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
2D maps like Google, Apple, MapBox GL, and OL3 are moving to actual vectors for rendering vector data, instead of baking vector data into a raster tile. This allows, for example, to make labels always face up even if south is up and to fade out labels so they never hit each other.
For now, this roadmap is a collection of resources on this topic.
- [Google Maps + WebGL = MapsGL](https://docs.google.com/presentation/d/1pL-OZnsWIKWcXflfJV8MPH3kKBehn0Mlx6-cdjmP3A0/edit#slide=id.g1e3a90e_1_28)
- [Vector tiles for fast custom maps](http://vimeo.com/106228141) (video)
- [Videos from FOSS4G](https://www.mapbox.com/blog/foss4g-jsgeo-videos/)
- [Mapbox Vector Tile Specification](https://github.com/mapbox/vector-tile-spec)
- [blog post](https://www.mapbox.com/blog/vector-tiles/)
- tools: [vector-tile-js](https://github.com/mapbox/vector-tile-js) and [mapnik-vector-tile](https://github.com/mapbox/mapnik-vector-tile)
- Client-side: pbf.js to decode tiles (protocol buffers).
- [geojson-vt](https://github.com/mapbox/geojson-vt)
- [MMT-Vector-Tiles](https://github.com/glob3mobile/mmt-vector-tiles/)
Contributor guide
Research direction
Start by reviewing the Mapbox Vector Tile Specification and the linked vector-tile-js, mapnik-vector-tile, pbf.js, and geojson-vt resources. The issue is currently a roadmap and does not identify Cesium files, tests, an implementation entry point, or a concrete definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100