mapbox / mapbox/vector-tile-spec
Support multiple values for tags and opaque tag byte tag values.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
Not all tags naturally have a single value, so for MVT3 it'd be nice to support repeatedly specifying the same tag and different values for it. The client could decide to expose this in a couple of ways. Alternatively repeated fields could be one of the optional tag types.
Also, it'd be nice to have an optional bytes tag value that could hold some application-specific encoding of data (e.g. another protobuffer).
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 by reviewing the existing MVT tag model and any MVT3 specification material. Define how repeated values and opaque byte values should be represented, exposed, and encoded; done means the specification records a settled design and its compatibility expectations.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100