> Highway on/off ramps https://a-b-street.github.io/docs/tech/map/geometry/index.ht... It's hard to say which is better here, to be honest. A giant blob of gray is less helpful than showing some lanes, but the original version is much closer to the actual shape: https://www.google.com/maps/@47.6564275,-122.3223112,203m/da... Though apparently even google can't handle this intersection. Where did the middle layer of r…
Transforming OpenStreetMap into thick roads and intersections
31–36 of 36 posts
Re: Transforming OpenStreetMap into thick roads and intersections
#32Very cool. Unfortunately it looks like I managed to put it into an infinite loop in the tutorial. Or possibly I just didn’t wait long enough after saving my changes…
Re: Transforming OpenStreetMap into thick roads and intersections
#33I am a professional traffic engineer and I build micro-simulation models for most of the projects I am involved with. I can say that compared to software that is used in industry (PTV Vissim, PTV Vistro, and Trafficware Synchro) it looks like A/B is a reasonable toy model that can get pretty close to the real thing. I think it is great that software exists at a level for individuals without huge budgets to be able to…
Thank you for the industry insight! I'm definitely not trying to match the degree of realism and calibration with the professional stuff -- there's no way I could, without way more resources. A/B Street's simulation is more for visualization than getting meaningful results -- although I am quite proud of the dataviz we've baked in. From talking to planners, reaching for these tools is a huge time and money commitment…
Re: Transforming OpenStreetMap into thick roads and intersections
#34Earlier quoted context omitted.
Can you or any other traffic engineers here tell me why we find it acceptable that cars are allowed to make unprotected left turns while pedestrians have a walk signal? Right turn on red is bad enough, but unprotected lefts give drivers a direct incentive to torpedo into crossing cyclists / pedestrians, as slowing down would mean a collision with oncoming traffic! Too many intersections in downtown Atlanta, for insta…
Most North American road infrastructure has been rebuilt over the last century to be automobile-centric. "We" deem that conflict to be acceptable because the alternative is more complicated phasing - most of which results in delays to car traffic (and pedestrians!), and so most places won't accept it. For details, here's [1] a document that outlines the tradeoffs in various different signal phasing designs. TL;DR is…
Re: Transforming OpenStreetMap into thick roads and intersections
#35I am a professional traffic engineer and I build micro-simulation models for most of the projects I am involved with. I can say that compared to software that is used in industry (PTV Vissim, PTV Vistro, and Trafficware Synchro) it looks like A/B is a reasonable toy model that can get pretty close to the real thing. I think it is great that software exists at a level for individuals without huge budgets to be able to…
As someone with interest in traffic models, what spaces do you or your peers hang out outline?
Re: Transforming OpenStreetMap into thick roads and intersections
#36Earlier quoted context omitted.
Most North American road infrastructure has been rebuilt over the last century to be automobile-centric. "We" deem that conflict to be acceptable because the alternative is more complicated phasing - most of which results in delays to car traffic (and pedestrians!), and so most places won't accept it. For details, here's [1] a document that outlines the tradeoffs in various different signal phasing designs. TL;DR is…
I agree completely with this comment. Most places signal timing is done with the main scoring metric of reducing vehicle delay. Pedestrians are just an after thought that can be squeezed into a vehicle specific timing plan. As an example, how often do you see a pedestrian scramble, walk signals in all directions, outside of somewhere like Time Square?