Make admin boundary post-processor work with lines.#71
Merged
zerebubuth merged 1 commit intointegration-1from Oct 13, 2015
Merged
Make admin boundary post-processor work with lines.#71zerebubuth merged 1 commit intointegration-1from
zerebubuth merged 1 commit intointegration-1from
Conversation
…tring fragments rather than needing an oriented polygon.
Member
|
👍 |
zerebubuth
added a commit
that referenced
this pull request
Oct 13, 2015
Make admin boundary post-processor work with lines.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Make admin boundaries post-processing filter work with boundary linestring fragments rather than needing an oriented polygon. This is to support tilezen/vector-datasource#302, in which we want to do some more processing in the database to avoid transferring the whole admin polygon over the network.
Connects to tilezen/vector-datasource#302.
@rmarianski could you review, please?