Hmm, I would think these should work. Do you know when the residential place for 11901 Cross Road Trl was added? When did you adjust the house number for 128 Bay Ave? Is there any chance these will work after the next tile build?
No I am not in the MD Google hangout, I guess I should join. How do I join?
I don’t know when 11901 Cross Road Trl was adjusted.
I adjusted 128 bay months ago. But the crazy thing is I get navigated to Dresser if I navigate to “home” when I am 10+ minutes away. But If I start the navigate to “home” when I am with in 10minutes, then Waze correctly navigates me to Bay.
Hmm. I don’t why the waze result for 11901 Cross Road Trl is not returned.
Is the Bay issue only when you use your “Home” favorite? Waze is routing to Bay Ave for 128 Bay Ave. The favorite locations are essentially stored as coordinates. They are not linked to the place on the waze map. So updating a place or address doesn’t change the location of the favorite.
Hmm, lets see if we can find out whats different between your search and mine. What precisely do you search for? Do you add a city name in the search? I don’t get a relevant result with no city name, so I’m searching for “128 Bay Ave, Dares Beach”.
I got another one. The pin location is correct, but Live maps and the app are navigating your to 8th street.
9027 Michael Way, Owings, MD 20736, United States
So, I am confused, I though Waze was suppose to always route you to the road the address was on. Adding the ability to have the stop point on a different rad was going to be a future ability, but is currently unavailable?
I did submit the 11901 Cross Road Trail issue to waze. The response is they’ve added Cross Road Trail as a street name and 11901 as a house number. They say this should solve the issue and ignore google’s search result, which seems to be the case.
Waze dosen’t use the postal address. Waze uses whatever we decide to put in as the city name as editors. So if we aren’t using the postal city and you search specifically for the postal city, then you are essentially forcing the return of the Google pin location.
Waze doesn’t do “always.” If the result choosen is actually from the waze house number data, then the stop point will be on the road with the name of the address. However, there are many instances where the search result may come from something other than the waze house number data. In this case as waze has the city as Dares Beach (I’m not sure we should though), when you search for “128 Bay Ave, Prince Frederick, MD” you get the Google pin location.
Sort of. Waze currently chooses Google’s address pins first, and navigates to the closest road despite name.
If the Waze house number marker is “verified” by bumping it, and updating the road geometry, it has a better chance of being selected in the search results, though the instant results in the app still return google pins.
I don’t know. I’ve heard conflicting reports on how alternate names are currently being used. It is probably worth a shot at this point to see what happens.
(There is likely old language in various waze documentation stating that postal cities are used in the search results rather than the township/community names. But this was there because at one point the search results were entirly based on the Google data, so the township/community (and house numbers) entered in WME didn’t effect the search results. Now that the waze house number data is used in search results, the township and community names entered in waze are used as the city data for the waze house number results.)
Sort of.
If there is a precise enough match of a trusted house number, the waze location can override the Google location when the auto complete result selected. (At least I’ve been told this is the case. I’ve experienced this and don’t think it is due to any beta results at this point.)
Waze hasn’t always navigated to the closest road despite the name when routing to a Google pin location. I’ve been told it depends on which of various Google APIs waze calls. Which API is called seems to be in state of flux and has at times depended on which tab you selected the results from. So at times you could get different results to same Google pin location depending on which tab you used to select the result. I’m not sure where all this stands at this point.