Integer values for attributes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or entry points; start by tracing the variable-to-band mapping and current -b <var name> <band no> option handling. Review how output attributes are encoded and compare the two proposed precision approaches. Done criteria are not defined because the issue does not choose an approach or specify expected behavior.
Written by the indexing model from the issue text.
Description
Using integers for most output attributes might reduce vector tile file size in a number of ways. First off, an integer in and of itself is stored more efficiently than other, higher precision formats. Secondly, @yhahn indicated in conversation that if attributes are repeated across features within a vt, that value is effectively only stored once.
I see two ways to handle this:
- Always force integers. Downside of this is attributes with actual higher precisions (eg a field that ranges from -1 to 1, as do many pixel indices). Of course, this could be handled by the user scaling these values before encoding, but.
- Build into the variable --> band mapping. Right now, to specifically map a band, we pass an option like so:
-b <var name> <band no>
We could easily make this into:
-b <var name> <band no> <precision>
cc @ian29 @MateoV
- Dominant language
- Python
- Stars
- 91
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
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.
More from mapbox/make-surface
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mapbox/make-surface#92 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
mapbox/make-surface#91 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mapbox/make-surface#90 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
mapbox/make-surface#89 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mapbox/make-surface#84 · 1 comment ·
All issues in mapbox/make-surface
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
StevenBlack/hosts#3256 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
qualcomm/qai-appbuilder#275 ·