mapbox / mapbox/vector-tile-spec
Registry of special attributes
Open
Nobody has claimed this yet.
3.0 Specification
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
We should track these and make sure they are handled uniformly and perhaps give them a more native representation.
clip_start,clip_end,lineMetricsin https://github.com/mapbox/geojson-vt/pull/93cluster,point_count,cluster_idin https://github.com/mapbox/superclusterclustered,point_count,sqrt_point_countin https://github.com/mapbox/tippecanoe/pull/511tippecanoe_feature_densityin https://github.com/mapbox/tippecanoe/pull/252
Others?
cc @mourner
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 listed attributes and the linked geojson-vt, supercluster, and tippecanoe pull requests. Determine which special attributes belong in a shared registry and what a native representation should cover. Done means the scope is agreed and the vector tile specification documents the resulting registry and handling consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100