PBF vector tile support
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 296
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
TileJSON doesn't seem to support Mapbox's own [vector tiles spec](https://github.com/mapbox/vector-tile-spec/tree/master/1.0.1). Am I misunderstanding something, or is this an omission?
I can see two ways to support it:
1. The `data` element should allow URLs that end in .pbf and return PBF files. But then, with the REQUIRED `tiles` attribute, it would be a bit awkward to conform to the spec for a purely vector source...
2. The `tiles` element should allow URLs that end in .pbf and return PBF files.
Either way I guess the scope of the spec is changing, since presumably it was originally envisaged that this was strictly for raster tiles and here it is being used for vector data...
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 reading the TileJSON specification and the linked Mapbox vector tile specification. Resolve whether PBF URLs belong in the data element or the tiles element, including the interaction with the required tiles attribute; done means the specification clearly defines the chosen vector-tile behavior.
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