Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Numerically equal attribute values are equivalent

Open
#124 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

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.

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.

Dominant language
No language data
Stars
1k
Forks
213
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/vector-tile-spec

All issues in mapbox/vector-tile-spec

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.