mapbox / mapbox/vector-tile-spec
Current spec is not friendly for massive points.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
I have massive points that almost fill the tile.
So the coordinate data takes the major size of tile.
Would the spec design new format for this situation?
For example, supposing the extent is 4096, it can use 4096 * 4096 bit matrix to store x and y.
if( bit(x, y) == 1), it has coordinate, else.....
And we can use array to store properties(number value?)., then compress them like being done in 3d tiles.
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
No files, tests, or entry points are mentioned. Start by reviewing the current vector-tile specification and the proposed bit-matrix and property-array representations. Done would require a decided, documented format change or a clear determination that the existing specification should remain unchanged.
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
- Needs clarification
- Newbie friendliness
- 20/100