Searching for Bob Hope Airport or Burbank Airport drops the destination pin at the back-end of the airport, not the front where the main entrance is.
Searching by the actual street address is correct, but doing it by name causes problems.
Back in August the “pin” (center location) for the Waze landmark was change (unnamed) and a smaller landmark was created at the main terminal entrance. So the true question is which search provider returns the “pin” closer to other location and not at the main terminal entrance. And that is where the correction needs to take place.
Well it appears to be wrong using Waze Live Map search, Waze search in the app, and Google. The other search engines show the correct location.
The problem is the Google Search results. It puts the pin in the middle of the airport, and I haven’t found any way to change it. This is a problem on any Google result that has an “area” defined rather than a pin. Google always reports the center of the “area” to Waze. See this thread:
https://www.waze.com/forum/viewtopic.php?f=8&t=72753
The easy way around this problem is to switch from the Google tab, to the Waze tab, which does have the correct location as one of the options. This issue also affects people going to the Ontario Airport, and even LAX depending on which result/tab they use. This is what I send users for Ontario:
“Waze defaults to the Google search results when searching for the Ontario airport, and unfortuantely Google provides GPS coordinates to the center of the airport which results in being routed to the wrong side of the airport. If you switch to the Waze tab, you can choose results which will correctly route you to the terminals. You can also try updating the GPS coordinates at Google, but so far I haven’t figured out how to do it.”
I requested Google move the pin to the main entrance. We’ll see if they actually do.
Search for
Bob Hope Airport Terminal
Yeah that works, but most people search by the common name “Burbank Airport”.
Bob Hope Airport Terminal popped up on one of the search providers when I searched for ‘burbank airport’…
Likewise, but again, not everyone is going to be selecting that option. It’s not the first one on the list.
Technically it is directing them where they asked to go…
Well, yes…but there’s no way to get into the terminal from the back, so I would thing a navigation app should avoid the back entrance. 
I’ve been stewing on this one for months and months. I think I even wrote to Google once, but never heard anything back. Unfortunately you can’t move the marker. I originally thought it was just the Landmark that caused the problem, so I pulled it and placed one over just the terminal. That stopped one of the errant search results, but not the Google one. Shortly thereafter, Shawn completely replaced my terminal landmark for some reason, and added the big unnamed one over the whole thing. I was hoping that would solve it, but here we sit, seemingly stumped again. 
I also found that removing a little parking lot stub at the corner of Sherman Way and Clybourn reduced, but didn’t eliminate, the incidence of these misroutings. Someone had recently added it back, and that may have helped bring about some of these new URs. Hard to say.
I can easily imagine how frustrated I’d be if I was running late for a flight and Waze took me 10 minutes out of the way, around the back of the airport.
That “parking lot stub” at Sherman Way and Clybourn is the General Aviation terminal. This is where one would end up if taking a private or non-scheduled flight into BUR. Similar to the West Imperial terminal at LAX. Perhaps a “General Aviation Terminal” landmark here, but that will not fix the overall problem.
Seeing a lot of URs in this area, people complaining they are getting taken to the back of the airport and not the front. Is there any resolution pending or should we just tell these people they are SOL?
Thank you
For now, let them know that the result with “terminal” in it will get them to the correct place. Others will as well, but it’s tricky getting the right one.
I’ve spent a lot of time trying to track down the source of the problem marker, even put in a request to Google, but haven’t heard anything yet. Maybe time to try again- anybody know how they feel about Wazers in general?
Tapatalked from my Nook Color running CM 10.2
I moved the pin on google map earlier today. I had done the same thing for an incorrectly placed Radio Shack - San Fernando pin that was miles from the correct location. The Radio Shack one looks like it’s been updated permanently on Google Maps now so perhaps if we move the Airport marker closer to the terminal side they will apply it this time.
Thanks for the response. I’m debating whether to reply to these poor folks or leave it to someone higher ranked such as yourself 
By all means, reply with a short, polite description and let them know that we’re trying to get the problem fixed. You can mention the “terminal” thing if you like.
We’re not the only ones with this problem, it’s confounding a number of airports throughout the country, and there was some discussion on it just recently, throughout this thread, which actually started about the roads within airports.
Sadly, still no great solution until, it seems, we will get a new POI system within Waze.
What did you actually manage to move in Google? Several of us have tried to move things, but as shawndoc described earlier in the thread, the main culprit seems to be the “boundary/grounds” pin, which is located at the geometric (or similar) center of the outline. Unfortunately, because of the shape of the airport, it ends up closer to the other side.
I did just have an idea I’m going to consider, though…hmmm.
I’ve gotten them to move the address/location pins of several businesses. Some of the moves were several miles. I have not tried anything so granular as moving the pin by feet or yards, sorry.
Thank you for the reply. If I encounter any of those types of unresolved issues I’ll give them suggestions if any are applicable.
Once I’ve identified the UR as a known issue, do I mark it Not Identified since the issue isn’t actually solved? Or mark is Solved because we gave them the best workaround for a reoccurring/currently unfixable problem?
Leave it open because a workaround is not the same thing as an actual fix.
Got it, thanks Borg.