Recent comments in /f/baltimore

routable t1_iwlbk11 wrote

Waze rep here, the “aggressive routing” is due to the No Turn On Red restriction at the light at Cold Spring/Harford. You could lift that restriction, at the peril of pedestrians (hint: don’t do this) and solve the problem. You could also (and should) make List Ave one way eastbound and put a No Left Turn restriction at the east end, effectively negating the usefulness of the cut through. The barrier option could have unintended consequences like impacts to emergency vehicles (and it looks low budget.)

19

theghostofm t1_iwlbfye wrote

3

BmoreCityDOT OP t1_iwlb9d5 wrote

We are so grateful for your work!

What we’d like to be able to do is share that data directly with Waze themselves so that they can make appropriate changes. The progressional relationship is rather new, but we’re planning on doing even more with them.

8

theghostofm t1_iwla9zz wrote

Interesting!

> Waze is constantly updating the map itself

I'm a part of that. For the past few years, I've been pretty active as a volunteer map editor for the city. I've added thousands of updates and additions, especially in East Bmore. One challenge is the fact that unfortunate routing problems are somewhat obfuscated from us. But if we were able to have broader insight into where we should mitigate these kinds of issues, it'd be great for Waze users and hopefully for city traffic in general!!

Oversimplified explanation: we have several different metadata we can apply to intersections and road segments which can impact how aggressive the routing algorithm will be with them. If we know about where there are likely problems with routing, we can work to improve them!

I don't necessarily want to add to your (likely considerable) burden, but I wonder if it'd be okay to suggest something like this: Would you guys consider sharing information regarding traffic patterns with the volunteers or reps?

7

bmore t1_iwl9xrc wrote

4

[deleted] t1_iwl9ppm wrote

You mean when we're all dead? Sure.

But we both know the better gain would be more/better public transit so that the roads were quiet because people weren't on them but still alive.

Any word on the red line coming back with Wes Moore?

1

BmoreCityDOT OP t1_iwl9ezh wrote

Nope. We are only working with road closures at this time. Waze is constantly updating the map itself, so we’re providing them with the most up-to-date data of whatever we’re physically doing on the ground so they can do what they’re best at.

5

theghostofm t1_iwl90se wrote

> Well, this isn’t just a Waze update. Concrete barriers are being placed.

Yep, I totally got that (The "try not to drive through the concrete barrier" comment is the best thing to come out of official City communication channels in the history of forever). But more clarification never hurt anyone, so thanks for communicating that!

> But yes; we work very closely with Waze reps and traffic professionals. We have a partnership with them, and any and all closures (temporary and permanent) you see us announcing are getting uploaded to Waze so you can use it to navigate around them.

That's cool to hear. One note: Your answer specifically mentions road closures, but my question was more about mitigation of aggressive routing in cases where road closures are not done. Is that something you also work on with Waze reps?

12

BmoreCityDOT OP t1_iwl8mwj wrote

Well, this isn’t just a Waze update. Concrete barriers are being placed.

But yes; we work very closely with Waze reps and traffic professionals. We have a partnership with them, and any and all closures (temporary and permanent) you see us announcing are getting uploaded to Waze so you can use it to navigate around them.

22