I have a UR, which is complaining that a specific house number is across the other side of a duel carriageway. The house number was been correctly located on the correct segment, which has a road number as well as the road name. Waze is still directing the driver to the side street that the road name without the road number:
Now, I’m trying to figure out what’s best to fix this. May be an alternative (road) name, or RPP? Any other suggestions?
I can get it to work if I navigate to 308 A34(S) - Liverpool Rd, as per the screenshots below. I dunno, maybe a Google result vs. Waze result thing?
Ah yes. I’m only searching in the first screen, not the ‘more results’. I’ll try alternative name first, to see if that fixes it.
This is a reoccurring issue and it appear to be cause by the way Waze translates Google addresses when we have a classified road (A & B) mapped with an unclassified road mapped adjacent with the same name. To fix the issue you will need to add RPPs as all other attempts have so far failed.
I was planning to submit a bug via centre code… if you’d like to do it instead do feel free. You’ll note that it will navigate to the classified segments if the house number is far enough away from the unclassified segment, this is approx 100m based on a quick test by Chris (Twister-UK).
So far we have fixed this on the B1103 - Exning Rd, Newmarket and have recently been discussing A322 - Worplesdon Rd, Guildford with the UK Champs.
I thinking of an alternative solution to this, rather than mapping a long line of RPPs. Would a Pedestrianised Area segment with the road name work?
Please do try it and see if it helps, after all someone will need to find solutions 
Ok, I’m testing this theory out on another example I’ve found in St. Helen’s.
I’ll report back on my finding in a couple of days.
I also noticed when I search for 660 Warrington Road, which is on the corner of Warrington Road and Knowsley Road, the route given actually finished on Knowsley Road, not Warrington Road. So it’s not only effecting addresses which have the road name without the classified number opposite, but also those close to side streets with a totally different name.
I’ve finally got around to submitting this as a bug in CenterCode - BUG-8345
Hi Chris, I’ve upvoted that.
Unfortunately the theory of using Pedestrianised Area segments doesn’t work.
Another one of these issues has occurred on the A34 - Kingsway in Cheadle.
I’m trying something else in adding House Number (using the house number tool) on to the Pedestrianised Area segments.
I’ll report back in a few days.
If this doesn’t work then it looks like we’ll have to rely on RPPs :roll:
After adding house numbers to Pedestrianised Areas, the routing still ends on the non-classified road opposite.
I think we’ll have to rely on RPPs :evil:
Hi.
I can see that Centercode bug report has not been answered for a while.
But, was there any solution or workaround for this problem that worked for you?
I see that somebody tried creating a residential place points, but that did not work for me.
My problem is 184 London Road, St Albans.
Because London Road is named A1081 - London Rd, Waze takes you to Old London Rd instead.
https://waze.com/en-GB/editor?env=row&lat=51.74707&lon=-0.33098&marker=true&s=33659289599&zoom=8&venues=235733509.-1937828809.22046475
Navigating to 184 London Road, St Albans works fine for me, are you sure you’re not using cached information?
Oh, that’s really weird 
I just downloaded Play store Waze on a device that never had Waze.
And I still get this issue.
Well, if I do a full search, then there is a result “184 A1081 - London Rd”
If I choose that, then it works.
But from the quick search, it always goes to Old London Road.
Steve, are you using a routing beta server or something like that?
This does route correctly because of the RPP mapped on 5th Feb 2020 by yourself. Tested on RBS and PRS.
As for the bug affecting house numbers on classified roads… no, nothing has changed, it has not been fixed. With the upcoming [no known timescale] change to how road numbers may be mapped on segments I have a feeling HQ aren’t rushing to correct this.
No, no beta, just standard android app.
As Chris says, it’s the RPP that I’m routing to and finding as the first suggested result for this address.
Thank you for clarifying that 