Linear feature end points at tile boundaries
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Review the current vector tile specification and the handling of linear features at tile boundaries. Determine how the format could distinguish a true endpoint from a feature continued in a neighboring tile, then document a proposed specification change and its completion criteria.
Written by the indexing model from the issue text.
Description
This is a bit of a corner case, but. When rendering linear features with distinct end-point rendering styles (a symbol at the end, or a dumbell or something) there is no way in the current spec to distinguish between a line that ends at a tile boundary, and one that is carried over the tile boundary by another line in the neighboring tile.
- 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 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
mapbox/vector-tile-spec#149 ·
-
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 ·
All issues in mapbox/vector-tile-spec
Similar issues
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ramnes/notion-sdk-py#409 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
salesforce/multicloudj#667 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
End of term: remove the PerfForesightCRRA-Approximation stub, and redirect its econ-ark.org pageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Bug pulumi/pulumi
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day