Maximum number of vertices
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- documentation
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.
Description
Mapbox Tiling Service docs 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?
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from mapbox/vector-tile-spec
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
mapbox/vector-tile-spec#157 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
mapbox/vector-tile-spec#153 ·
-
Typo in §4.4Open
Difficulty 1/5 Under an hour Newbie friendliness 55/100
mapbox/vector-tile-spec#148 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
mapbox/vector-tile-spec#145 · 2 comments · 1 reaction ·
-
3.0 Specification
Difficulty 5/5 Over a week Newbie friendliness 25/100
mapbox/vector-tile-spec#142 · 5 comments ·
All issues in mapbox/vector-tile-spec
Similar issues
-
bug
Difficulty 2/5 Under an hour Newbie friendliness 82/100
awslabs/visual-asset-management-system#413 ·
Maintainers usually reply within 1 day
-
good first issue hacktoberfest
Difficulty 2/5 Half a day Newbie friendliness 70/100
HelpCode-ai/anythingmcp#996 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
zerocracy/judges-action#2730 ·
Maintainers usually reply within 8 days
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
afarber/OpenMapView#21 ·
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
githubnext/gh-aw-workshop#4417 ·
Maintainers usually reply within 1 day