Road Names vs Route Numbers

Is there any way to have the Waze app refer to roads using their state route number? Here in Connecticut, we refer to most roads using the state route number. I’m not talking about large interstate roads like I-95 or I-91. I am talking about the main local roads that wander from town to town that most of us here use everyday to travel through the state. For example, Route 79 or Route 68 or Route 17 or Route 148. In Waze, these roads are referred to using a name such as Durham Road or Madison Road or Wallingford Road or Main Street or Killingowrth-Durham Road. On roads such as this, there are no signs anywhere that indicate a road name. All road signs indicate the route number. This makes using Waze for navigation very confusing, almost impossible. It gets even more confusing when a road name is used more than once to refer to a different route number in different towns. For example, a section of Route 68 (not the whole road)in Wallingford, CT is called Durham Road in Waze. Then, as far as I can tell, there is no road named Durham Road in the town of Durham, CT. Then, just down the road a few minutes in the town of Madison, CT you see Route 79 referred to as Durham Road in Waze. Often times, a state numbered route will turn at intersections as it winds through various towns. The only indication that you have to take a left or right at an intersection to stay on a numbered route is the signs indicating the route number. You may want to stay on Route 68 but that road winds through towns and, for example, in one area changes road names 3 times in Waze, twice in the middle of the road as it changes from the towns of Durham to Wallingford. We don’t use road names here in Connecticut. We use route numbers. Route numbers are what all the road signs use. Almost always, there are no road signs indicating the road name as used in Waze. In my tavels around the north east this seems to be the case in many other states as well. I have seen numerous posts asking my same question but they always seem to get the brush off excuse that route numbers are confusing and road names are better because signs show road names. Again, that is NOT the case around here. Google Maps, and many other navigation apps I have tried, refer to roads by their route number whenever possible. Is there any chance of ever getting this fixed in Waze? Without this fix, it makes an otherwise great app pretty much useless.

(Moved from the global forum to the US>CT forum)

In CT, almost every non-highway numbered route (signed & unsigned) has a name & that name (not the number) is the primary designation for that road (according to the state & municipalities). That name is used on signs (they aren’t as big as the signs for the numbers, but they are there in most cases), by the addresses on those roads, etc.

Waze has the numbers listed as Alt-Names, just like the official documents do. It’s the same with Google - except they have the ability to display both, something that we have asked Waze to do numerous times.

There are a handful of exceptions to this, notable a chunk of Route 7 & a chunk of Route 12 - which are named “Route #” as that is what the addresses along those sections use.

If you are trying to follow a specific road number in Waze, then you aren’t using the power of the app.

so when Waze tells me to turn onto Boston Post Road or Durham Road or Madison Road or Wallingford Road or Main Street or Killingowrth-Durham Road and there are NO SIGNS indicating those road names, ONLY signs indicating the Route #, I am using the app incorrectly? I see it looks like you are from Connecticut. I have lived here my entire life and I have never seen road name signs on most of the state route # roads. So Waze is basically confusing people by telling them to turn onto a road that they will NEVER see a road sign for. Great app. I guess I am using it wrong… by using it at all. Thanks for the info. I apologize as I understand that you only have so much control over how the app shows things but after all the posts I have seen regarding this issue, I would think Waze would make some sort of effort to correct it or at least use both the road name and the route # together as Google Maps does. I was hoping this issue could be passed up the chain to someone who could possibly fix it since other than that confusing problem, Waze is a pretty great app. But giving confusing directions using road names that aren’t posted for you to follow makes the app pretty useless. Doesn’t Google own Waze now? Seems like it would be an easy fix. I guess they just want to force people to use Google Maps instead. Well I think that finally worked on me so I think I’ll just uninstall Waze and use a different app that is actually helpful. I’ll be sure to tell everyone I know as well.

Hi Unicron7721
I’m the Regional Coordinator for CT and I can certainly help address this issue. According to our National Waze wiki HERE and based on what you are explanation above we might need to make some changes. I’ll review these with my local State Managers and make the appropriate changes. In addition, you can also review our local guidelines here: CT Wiki

Hi orbitc,

Thank you for your response. I am happy to see that there is a chance we can get this issue resolved since, as I said, other than this confusing issue, Waze is a great app that I would love to continue using as long as it remains useful and does not confuse your while you’re driving. If there is any way I can be of any assistance, please let me know.

Thanks!

In an ideal world, Waze would pull from Alt-Name for shields on the map & in the directions - something we’ve been asking for for years, but haven’t been able to get.

Orbit, incoming PM.