Draw custom LTN boundaries, by painting blocks. #794 #821
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.
Still need to think through the UX of how to manage custom boundaries
and incorporate them in the "browse neighborhoods" screen.
Demo:
Context here is that defining the "boundary" of a neighborhood is hugely contentious. What if people want to "merge" two adjacent LTNs? What if the OSM classification of a major road is wrong? What if the government's inclusion of some road as a major arterial road is based on historic context and should be challenged now? Should the boundary of an LTN include parks, waterways, railroads or not -- #794 (comment)?
Instead of trying to decide all of this by heuristic, just let the user paint their own boundary!
The UX is clunky right now -- after you draw a boundary, it won't be "saved" to the "browse neighborhoods" screen yet. Will think through some of that next.