EXPERIMENTAL work on prototyping the VT3 vector tile spec revision #611
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Don't tag zoom/x/y yet when creating tiles, to avoid remaking all the tests
They now stay in array form until just before printing, rather than being decoded into strings as part of tile deserialization
e-n-f
force-pushed
the
blake-properties
branch
from
4eab2c5
to
cf81880
Compare
|
Is there an expected release data for this (and for VT3 in general)? |
|
Sorry, there is not currently a VT3 roadmap. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As in mapbox/vector-tile-spec#121