-
Notifications
You must be signed in to change notification settings - Fork 91
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
Mapzen MVT vector tiles #57
Comments
How hard would it be to modify the current VTM decoder for this format? VTM and MVT seem very similar but I would need to look into it a bit more. Was just asking in case you have already looked into this (or whether it was just a passing thought). MapZen have deprecated VTM (though it is still accessible if you specify the API version as 0.8), but I have no doubt they will completely remove it soon. |
The MVT format hasn't changed that much. I got this decoder working with some minor tweaks a while ago: https://github.com/opensciencemap/vtm/blob/master/vtm-extras/src/org/oscim/tiling/source/mapnik/TileDecoder.java Looking if I find the updated code again somewhere |
Great, thanks! Looking on working on this some time in the near future just so I can continue using this library. :) |
@deviousgeek I hadn't the time to check any of #55, #56 or #57... @hjanetzek thanks for the info and any additional help! |
|
Definitely going to try this out when I get the chance, you rock. :) |
Thanks @hjanetzek ! I played with it, probably theme(?) needs some work? (BTW I cannot find the new commit in opensciencemap history) |
Yup, looks like I can only get greenery and bodies of water showing up using that theme file. I am sure it's just a matter of adapting the correct attributes in the theme file, however. :) |
For what it's worth, MapZen have posted a "cheat sheet" which they used to migrate to MVT internally. https://gist.github.com/nvkelso/a7cfec649bb0de49f4ac71596a148a32 |
After upcoming VTM 0.6.0 release, I'll merge @hjanetzek 's commit so that's easier to work on it. |
@devemux86 yeah, this is unfinished code I had floating around. Please just pick the commit and cleanup (no need to merge the branch) |
Mapzen != Mapbox (IMHO) |
@andreynovikov what do you mean? |
Ah, ok. But mapbox format is from Mapbox, so it's better be referenced there. |
Everbody uses MVT format now (which is a slightly modified and rebranded OpenScienceMap VTM format IMHO :). Mapzen and Mapbox both offer vector tiles as MVT. The tiles use different tag schema for the contained data - so styling rules must be written for the respective schemas. |
I pushed a series of commits for anyone wanting to work with
|
For people asking how they could improve Mapzen MVT tiles parsing, I post some notes:
|
Thanks to @boldtrn and PR #279 we now have a working Mapzen MVT implementation!
@boldtrn please report any other cases need checking. |
I added an option to select the preferred locale in Mapzen MVT vector tile source. |
Yes this is possible, see some samples here:
|
A reference of layers in Mapzen's vector tiles is here. |
This is fantastic news! Can't wait to try this out. |
Closing this as Mapzen MVT vector tiles are now supported. Issues can be followed separately, e.g. see #288 for the artifacts. |
Mapbox-format binary tiles uses the
.mvt
extension.This is a compact format using protocol buffers that is used for raster tile rendering in TileMill2 and vector rendering in MapboxGL.
It is one of the available tile formats from Mapzen.
The text was updated successfully, but these errors were encountered: