-
Notifications
You must be signed in to change notification settings - Fork 9
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
Map change: remove the buffer overlap #117
Comments
A simple (from a coding/technology side) solution is to limit the buffers to only be within the county borders. This would automatically prevent any overlap from showing. |
I like @mdelcambre's recommendation. This could be as simple as calling turf.intersect passing it the buffer polygon and the county border polygon before saving the buffer. And yes, this is definitely of use when we are calculating % of the jurisdiction's land area that is within X distance of bike infrastructure. Right now Arlington's "% of jurisdiction within 1 mile of bike infrastructure" is calculating as over 100% because the buffer polygon extends beyond the actual jurisdiction. |
woah, DC boundary extends west of the potomac? #Themoreyouknow [image: Inline image 1] Nelle Pierson *| *Deputy Director * Your membership results in better bike rides. Click here On Fri, Sep 2, 2016 at 3:28 PM, Chris Slatt notifications@github.com
|
Yep. DC owns ALL of the water and everything in it - TR Island is DC, Memorial Circle is DC. |
This was done in #131! 🎉 |
We're looking to prevent buffers from overlapping when they cross jurisdictional lines to avoid the intestinal look.
Possible with modifying svg directly: Pull all paths into a single instead of multiple nodes. A little tedious, might be slow.
The text was updated successfully, but these errors were encountered: