I have a UI here .
Basically Waze should have directed the user to make a left on Brooks Robinson to get on 695. Instead, Waze directed to continue down Park Heights, make a left on Autumn Drive, then another left on Stevenson Road.
Basically you can see the inverted triangle the incorrect directions give, instead of just cutting through the top of the triangle.
I’ve gone through the direct route to see if there are any blocked turns or continuations but am stumped.
Ed
I’ve reproduced the routing the reporter indicated using the LiveMap: the data indicates the speed on Brooks Robinson is VERY SLOW during the morning rush hour.
You can see the progression from 6a, 7a, 8a in these screenshots: Link. Looks like the same thing happens during the afternoon rush (5:30p until 8:00p also in the Link).
I would caulk this up to lousy data in the residential neighborhood. My response would be that Waze is providing the fastest route based on historical traffic data, and the only way to fix that data is to drive the waze recommended route and prove it wrong (improve the data).
I’ve had conversations via UR Comments with that reporter in the past month suggesting similar courses of action. I’m glad they are receiving answers from other editors - maybe they will just accept it as a bug.