More steps towards blocks and bundles #257
Merged
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
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.
#248. A "block" is just the space between roads and intersections; there shouldn't be other roads and intersections in there. This PR firms up the idea of a "bundle" -- either a road and its sidepaths or a junction, or just the land-use space in between roads. The classification is wrong in many cases, but it's starting to chop up things into junctions and road-bundles nicely in some cases:
(Ignore the misclassified parking lot)
Two adjacent road bundles is interesting -- that's how the dog-leg intersection shows up. All of this logic is very dependent on where the crossings are -- if they aren't everywhere, some of these ideas start to break down.
