-
Notifications
You must be signed in to change notification settings - Fork 3
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
Background data causes chunks of traffic in Great Kneighton simulation to stop completely #151
Comments
Gridlock is unfortunately normal in A/B Street. A few lucky maps (like Poundbury) have had special attention to fix the worst bugs there, but Cambridge is more complex and hits different issues. Glancing at a few:
Getting a map to run without gridlock is very hard, but I can spend a little time working on Cambridge if it's important. Ultimately I need to attract more open source people to the project and get help with some of the hard modelling bits (like auto-timing traffic signals around a roundabout) to make faster progress. |
Portugal Place is no cycling anyway - but a cycle track is shown.
NB Known as the "Addenbrooke's roundabout" :) |
Are the issues predominantly OSM or A/B Street? |
Is it currently possible to model? |
In my view, almost impossible in OSM for complex junctions - the inability to group junction components is problematic. See fuller discussion in my State Of The Map talk, e.g. from 15 minutes on and my conclusions at the end: https://media.ccc.de/v/sotm2019-1038-is-the-osm-data-model-creaking- |
Quite apart from the simulation issues - Addenbrooke's roundabout has three circulatory lanes and that might help sort things out in this case, depending on your lane-changing model (which I understand is still a bit crude). When I get some time I might also take a look at modifying this demo. |
…r the Great Kneighton map, at least fixing the crazy geometry at Portugal Place. cyipt/actdev#151 [rebuild] [release]
It's quite possible more lanes would break the simulation even more. ;) But if OSM doesn't match reality, it'd be awesome to update it. https://www.openstreetmap.org/way/58559114 and similar don't have the |
No, the Dutch roundabout, which is the one at the next junction, has been created in glorious detail by yours truly (and subsequently iterated upon). https://www.openstreetmap.org/#map=19/52.17930/0.14903 I can't remember the lanes layout on the Addenbrooke's roundabout; there have been changes made which may make the current Bing satellite imagery incorrect. |
This was really my question - can complex signal timing be incorporated? It might need someone to sit with a stopwatch at that junction! Re the need to get contributors, I suspect Cambridge is a good place to start with that. There are plenty of technically competent transport geeks hereabouts. |
Depends how it works. We have actuated signals, where a stage lasts a fixed time, plus up to some additional time if there's still demand from that direction. We can also offset a signal relative to another. Hopefully that should cover this particular situation, but I don't know what it's like in person. I made a feeble attempt last spring to hand-time Seattle's signals in person. It could be done theoretically, but there are complications, particularly: many signals are on different plans at different times of the day or on weekends; and actuated signals are much harder to observe than fixed time. The bugs at this particular roundabout aren't exclusive to the timing; you can use the signal editor to convert them all to stop signs, and it still gets stuck. There's a gridlock bug elsewhere.
Any recommendations for online meetups (maybe a local OSM, GIS, or civic tech group?) that I could solicit people from? |
…aths are enabled. Removes Portugal Place from Cambridge. cyipt/actdev#151 Now regenerate everything
I know congestion in South Cambridge is bad, but I don't think being stationary for 35 minutes is normal (notably around the hospital). I stopped the sim at that point.
The text was updated successfully, but these errors were encountered: