mapbox / mapbox/vector-tile-spec
Maximum number of vertices
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
[Mapbox Tiling Service docs](https://docs.mapbox.com/mapbox-tiling-service/reference/) allude to MBGL performance issues with long linestrings and polygon rings:
> Note: Even if the simplification is specified as 0, complex features will receive additional simplification so that they can be rendered correctly by Mapbox GL. Polygons or MultiPolygons with more than 65535 vertices and LineStrings and polygon rings with more than 6553 points will be simplified to reduce their complexity to these limits.
With tilemaker-generated tiles, rendered by MBGL JS, we've also encountered rendering issues that appear to be caused by very long linestrings.
Should the MVT spec recommend (probably as SHOULD rather than MUST) a maximum size, or is this a rendering implementation detail that users are expected to check with their chosen client?
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
Start with the MVT specification and the linked Mapbox Tiling Service documentation; compare their stated vertex limits with the MBGL JS rendering behavior described here. Determine whether a normative recommendation is appropriate, then record the decision or resulting specification change in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100