Notifications: use next cross street

[brian6string]

All of the notifications (traffic, weather, police) etc. have this unhelpful habit of telling me a place name instead of a cross street. In Maryland, I travel MD Rt. 32 to and from work. Every morning I am notified that there is traffic at MD Rt. 32 and Bonaventure, or some other place name. Honestly, I've lived in this area for 30+ years, and have no idea what or where Bonaventure is, I presume its the name of the neighborhood or subdivision near where the traffic is. There certainly are no signs "now entering Bonaventure" or such. BUT, there are signs naming the exits I am approaching. And if I were getting turn by turn navigation, you'd tell me to exit at Rt. x or Main St. or such. Why can't the notifications be based on cross streets, or exits? It would make a lot more sense.

[AndyPoms]

Can you post a Permalink to the area?

[CBenson]

Here's a permalink for Bonaventure. Easy for me to provide because I'm likely the guilty party that added it. I must admit that I'm surprised that it shows on the Route 32 reports. I haven't noted that. I think I've seen reports with "Odenton" as the city in on 32 in that area. I wonder when waze decides to use Bonaventure instead.

I'll eliminate Bonaventure. Feel free to let me know others that cause confusion. I put a bunch in my early editing that I have since deleted, but have never made it priority to go back eliminate them all. But I didn't think they would show on freeway reports where the freeway doesn't traverse the city polygon and another polygon surrounds the more specific one.

All that being said, it doesn't really change your point. Would it really be all that more helpful if the notification was for traffic at MD Rt. 32 and Odenton?