High-precision vector tiles are downsampled to 8192 extent for rendering
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to switch my current map-based application from geojson type source to vector tile source.
As a proof of concept, I did a small experiment to visually compare the features drawn from geojson source vs vector source. Features drawn from vector source are geometrically different than that of geojson.
Especially polygon geometries have a skew effect like shown below where features with black boundary are drawn from geojson source and blue one are from vector tile source


As per the discussion here, it is confirmed that the tiles being generated are up to the expectations but mapbox gl-js is somehow trying to modify it. How do I get the tiles rendered(blue colored layer) so that they match exactly with the tiles generated from geojson source(black colored layer)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Begin by reproducing the GeoJSON and vector-tile comparison described in the issue, then trace the mapbox-gl-js vector-tile rendering path with attention to the reported 8192 extent downsampling. Done means determining whether rendering can preserve the tile geometry and validating the result against the GeoJSON rendering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- computer-graphics, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100