mapbox / mapbox/vector-tile-spec
[2.1] Feature ID datatype
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
We recently received a request to [Support text ids](https://github.com/terranodo/tegola/issues/101) for Feature IDs on our MVT server. Looking at the spec, it appears there is no restriction on the datatype for Feature ID:
> A feature MAY contain an id field. If a feature has an id field, the value of the id SHOULD be unique among the features of the parent layer.
The provided protocol buffer file has type [uint64 for Feature IDs](https://github.com/mapbox/vector-tile-spec/blob/master/2.1/vector_tile.proto#L32). Was the datatype for Feature ID left out of the spec intentionally to allow for future support of different data types, or is the intent to always require a uint64 type for Feature IDs?
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 linked request to support text IDs and the referenced 2.1/vector_tile.proto definition for Feature IDs. Read the issue discussion and the quoted specification language first. Done means reaching and documenting a clear decision about supported Feature ID datatypes, including any required specification or protocol-buffer changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100