I know the Google data for house numbers can be widely inaccurate, but I’m sure I’ve added house numbers to streets in the past and it’s worked after a tile update. Please feel free to correct me on this.
I responded to a UR here and added in the house number (59).
The tiles have been updated but navigation to 59 Foxglove Drive takes you near Coltsfoot, half way around the Drive, not to No.59 which is up near the Leisure Centre.
Any ideas?
The comments here suggest that it may take two tile update cycles for HN changes to propagate through the system…
OK ta. I shall wait and see.
Unfortunately, the latest update hasn’t made any difference.
Hmm… Not sure what the problem is on Waze’s side of the fence then. From the Google side, I’ve just spent the last 10 minutes being reminded what an utterly awful editing environment they provide us in the shape of Map Maker, whilst fiddling with the house numbering up on that end of Foxglove Drive.
Interestingly, numbers 57 and 61 were already correctly located in the Google map data, however most of the numbering for that road is located on/near the Coltsfoot roundabout, hence Waze currently using that as its destination point as well.
I’ve now correctly located 51-61 in Google, so once that change propagates through their systems it should provide an interim fix for Waze users as well (or at least that tiny minority who need to navigate accurately to one of those 6 houses).
Thank you.
I have ventured into Map Maker a few times, but didn’t realised you could play with the house numbers.
Edit - It works now. Thanks again.
I have a couple of similar things going on over here in the States, HNs all repeatedly verified, Waze keeps using Google data and you can’t get it to use its own data no matter which way you run a search or where you check for results.
Mind-numbing…having to muck around in MapMaker to force a correct external solution because Waze dutifully and completely ignores its own correct internal data.
Sorry, nothing to add of value here, just ranting… sorry.
IIRC, Waze will only use its own HN data if either:
you’re searching for that specific HN
or
you’re searching for a HN which Waze would need to interpolate from two other HNs in its own data, and if the external datasource search returns no results for that HN
In this case, since we’re trying to navigate to a HN that doesn’t need to be interpolated, there’s no reason I know of why Waze should then be overriding its own result with the Google one. Maybe HQ have changed/broken something in the address search code…