-
-
Notifications
You must be signed in to change notification settings - Fork 337
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
Glitchy Geometry for road #833
Comments
To repro easily, geojson is:
Look for lane 1763. Something very funny is going on with OSM here... try clicking the intersections at either end and jumping to the OSM nodes. I get https://www.openstreetmap.org/node/1297431637#map=19/35.58856/139.72453 and https://www.openstreetmap.org/node/2071014569#map=19/35.58835/139.72473, but that second one isn't a member of the way |
Actually wait, this is the classic problem with curved roads that have lots of points: I manually removed some of the points with the I'll try this out! |
… OSM too close together, it explodes PolyLine shifting. #833
… OSM too close together, it explodes PolyLine shifting. #833
…r after collapsing degenerate intersections. This is a followup to #833. And clean up some other things that RDP does better
…r after collapsing degenerate intersections. This is a followup to #833. And clean up some other things that RDP does better. Fallout from regenerating everything: - Enfield borough crashed, so removed it - All UK scenarios are now much bigger, due to the changes in #853 being picked up - Poundbury gridlocks now due to that
…r after collapsing degenerate intersections. This is a followup to #833. And clean up some other things that RDP does better. Fallout from regenerating everything: - Enfield borough crashed, so removed it - All UK scenarios are now much bigger, due to the changes in #853 being picked up - Poundbury gridlocks now due to that
Way: https://www.openstreetmap.org/way/114559247
I do not expect any action on this, I just wanted to point out a case where there was something funny going on.
The text was updated successfully, but these errors were encountered: