Waze forum

Noam,
This is what happens if you search for the Richmond Airport in Richmond, Virginia. If you pick the first entry you are routed to the neighborhood behind the airport as Brandon stated. (This is the correct route to the Richmond Airport.)

I get the same list in the client: The first entry is listed as an ad and all the "Pins Prediction 2" entries have stars. What do the stars mean?

If I ask for info for the first entry, the "ad," I get: So what is "Pins Prediction?" Where are these results coming from?

Note: I am using the Android beta version of the client.

I'm still routed correctly if I use the results on the waze tab. The problem is that the autocomplete results rely on the Google pin. Currently Google is placing the pins at the center of the airport boundary object. It has been very difficult to get these changed in the Google database. I'm not sure what to do with airports at this point other than to tell users to actually hit search and select the location from the waze tab.

My understanding is that waze is using its own data as the primary lookup if you complete the search and get the results on the waze tab. However, its also my understanding that the auto-suggestions come entirely from the Google data. This doesn't appear likely to change soon. It seems that developing a good auto-suggestion feature is not a easy at might appear and Google is very good at it.

I can no longer reproduce this. Its possible that results are different if you are closer to the airport when you search. We need some steps that reproduce the wrong route to give to waze to illustrate the issue.

I understand that the Google result is still showing. But when I route to the Google result, I am routed to the closest point on Bland Blvd to the Google pin, which at least routes by where the waze result puts you.

Maybe we could get rid of the Google result by using as slash or space instead of the dash in the airport name. But that's just a wild guess on my part.

AlanOfTheBerg wrote:blue means Waze Place

I'm not getting a blue pin. Ever. Even for Waze Places.

For the autocomplete results I now get "RICHMOND airport" as the first result. This shows a pin in the middle of the airport grounds and routing to it takes me to Raines Ave in the adjacent residential community. But I can't find anything in Waze or Google capitalized like that entry. The second result appears to be the Google result for an airport in Rhode Island.

Hitting search does not bring up the Waze result first for me. The Google result still shows first under the places tab. If I switch to the Waze tab the Google result is not listed.

I agree that this is concerning. If we have a place entered correctly, the default returns should not be unidentifiable.

Depends what you mean by a workaround. You can add a (fake) road from where you want waze to route to the near the google pin. This would cause waze to at least route through the correct location rather than the backside community. However, there are some obvious negative side effect of doing this. There is also the problem that depending on which selection is choosen you get different results. So for instance if the fake road is close to the stop point for the airport, it can adversely effect good routes that are given to those who manage to select the waze result. A further problem is that how waze routes to Google results seems to change from time to time, such as taking the street address into account for Google POIs for brief time after 3.9 was released.

I'm not understanding. Waze fixed it, did they not? The initial result on each list I bring up now takes me to the correct location.

If the problem is that waze is routing to the Google pin, then you should submit the issue on the form discussed here: viewtopic.php?f=8&t=105736 That is what seems to have worked for Richmond.

AlanOfTheBerg wrote:I agree with the issue here. Richmond airport is a plain pin (not blue; blue means Waze Place) and it shows the middle of the field, so is a google result. Hitting Search, of course, brings up the Waze result first, which then is much better. Someone made some updates yesterday, not sure what. I did a couple more updates today. I do see that Richmond International Airport search has the same issue and that is the exact primary name in WME.

This is a concerning issue. Why would google results be preferred for a near-exact match?

I added alt names to the airport to cover all of our bases.

Machete808 wrote:I wish there was a way to get a message through to top-level Google Maps editors that they need to MOVE THE MARKERS for all airports to a sensible location.

[img][/img]

On a local basis, it's good to try to establish a good GMM editing history and build trust with one or two reviewers. Having more of a "personal" relationship through repeated interaction helps a lot. It's still a bear to prove a case sometimes though.