-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PBF vector tile support #17
Comments
@stevage we have been going with option 2 (specifiying |
Ah thanks. No, there's nothing that says explicitly that However, when I tried using .pbf tiles with Mapbox Studio and it didn't work I concluded (wrongly) that using .pbf files wasn't ok. Which is perhaps another way of saying that the spec isn't totally clear. |
Also, it does seem that there is an ambiguity if you're serving GeoJSON tiles. A quick reading of the spec would suggest using the Another ambiguity is in the "All endpoints MUST return the same content for the same URL" clause. It's not totally clear to me whether having a .pbf and .geojson endpoint would satisfy that clause or not (it would be the same "content", but in two different formats.) I imagine it probably wouldn't. (It's also slightly wrong to say "for the same URL", because by definition different endpoints have different URLs...that confused me a bit at first, thinking it meant that each endpoint just had to be consistent about how it responded to a given request...) |
What if I want to support both PNG and PBF tiles? I could use |
Hey y’all, this could use some improved language in the specification to make it clear where to specify the tile format. We’ll plan on clearing this up in the upcoming v3 specification, with an eye towards the tiles, and data. We'll comment back here when there's something to review! |
TileJSON doesn't seem to support Mapbox's own vector tiles spec. Am I misunderstanding something, or is this an omission?
I can see two ways to support it:
data
element should allow URLs that end in .pbf and return PBF files. But then, with the REQUIREDtiles
attribute, it would be a bit awkward to conform to the spec for a purely vector source...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...
The text was updated successfully, but these errors were encountered: