mapbox / mapbox/vector-tile-spec
Numerically equal attribute values are equivalent
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
The spec should be clear that tile encoders may choose any representation (`sint`, `uint`, `float`, or `double`) for numeric attributes that correctly represents the value, and should choose the one that produces the smallest tile, rather than preserving the type of the original input value, so, for example, `2.0`, `2`, and `2u` will all be represented as the same `uint 2`.
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
Locate the repository's specification source and review the existing wording for numeric attribute values; the issue names no file or test. Done means the specification clearly states that equivalent numeric values may use the smallest valid representation, with the 2.0, 2, and 2u example covered.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100