ploben wrote:don't these imported HNs have a stop point on the actual street?
ploben wrote:If Waze imported HNs for internal use why would they not then refer to them if they are searched?
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.
Bigbear3764 wrote:Because the pin location is closer to the alley than the street the address is on. If you are in North America, Google pins are set back on the property. Do a Google search of your address and see where the pin is. Once Waze starts using it's own addresses, and if they entered, Waze has a stop point for the street.
CBenson wrote:Have you routing to saved the location in the app (a search entry with a star) or are you routing to a history entry (a search entry with a clock)?
Users browsing this forum: No registered users