CBenson wrote:My understanding is that when autofill results are generated, they are generated from the Google database and this is unlikely to change in the near future. However, if there is an exact match in the waze HNs to a selected autofill result, then waze will route to the waze stop point for that address.
If you complete the search, then waze first parses the search to determine if it is for an address or for a POI. If it is for an address, then my understanding is that waze does look to its own HNs first. However, it only looks to those HNs that have been added or modified by an editor. If it finds such a waze HN match it uses it first before looking to Google addresses. If there is not a perfect match, there may be results from both waze and Google shown on the waze tab.
It's unfortunate the auto complete doesn't look internal first, that would make sense.
I think the exact match has a flaw, in my other post about Quail Crossing vs Quail Xing, Waze still won't recognize my Waze pin in auto complete even though the address, street name, town is EXACT except the suffix.
On the topic of HNs that have been imported but not touched by an editor, don't these imported HNs have a stop point on the actual street? If Waze imported HNs for internal use why would they not then refer to them if they are searched?