https://www.waze.com/editor/?env=usa&lon=-113.99972&lat=51.12084&layers=389&zoom=2
The above permalink should show the Calgary airport. There has been a huge (well, “huge” in comparison to past counts) number of URs complaining of poor driving directions, routing Wazers to the end of 78 Ave NE, near the firehall, when they choose the first “Calgary International Airport” they get to on a search. There should be an open UR with comments from me right in the center of the map from the above permalink.
The problem lies in the fact that Google has placed the pin for driving directions on the center of the airport polygon, which is a couple hundred meters west of the firehall. And since Waze incorporates Google Maps searches into its own search engine, well…
The unfortunate part is that in order to get to the location where the most recent UR was posted, you have to take a route that used to be the correct route into the passenger terminal. But a few years ago, the airport began a big expansion project, adding a new runway and more than doubling the size of the passenger terminal. To make room for it, that road was removed - but a sideroad adjacent was kept, so that access to the cargo terminals, tower, firehall, etc., was still possible. So people are frequently driving to the directions Waze is providing them (due to Google’s bad directions), and have no way to get to the terminal - they have to backtrack 12 to 15 km (depending on which route you take) to get to the actual passenger terminal.
I have repeatedly tried to get this problem corrected in Google Map Maker by submitting edits to the Calgary International Airport pin. I’ve even cut-and-pasted an explanation that our own expert doctorkb suggested to me. If you look in GMM on that pin right now, you will see that edit, still sitting after 2+ weeks, untouched, which is how most GMM edits languish until a person with no local geographical knowledge rejects them as incorrect.
If anyone has any suggestions on how to fix this, or has any “pull” with GMM enough to make the change without having to submit it for others’ approval (i.e. if you’re an RER), I and the people who keep posting these URs (and surely others who just get frustrated and stop using Waze because of it) would greatly appreciate the help.
Can you share a link to the GMM edit? I’ve done a few edits there… not sure if it’s enough to approve them, though.
I think this will give you a link… I’m not 100% sure. It may just give you the airport and you’ll have to open the placemark and get the edit within it.
http://goo.gl/rAKUJZ
Thanks in advance. 
There are a few issues with the pins right now.
First, the “pin” you moved it the “center pin” , now although Waze routes to this marker, Google insists that it stay in the center of the area, they use their own nav marker that Waze can’t see and Map Makers cannot edit. Even their senior volunteers.
The reason no one can “review” your edit is that locked specialty items like airports and such, although we can edit aspects of them; must be approved by special mapping teams from Google. Not even their normal mappers can approve them. They must be personnel from one of the teams.
Although I personally don’t have any pull with a Google map team employee, their is a group of editors in the US that have gotten together who are also proficient at MM. We deal with most of the pin moves in the US now that a lot of Waze editors don’t want to deal with. They just enter the info into a Google Doc and we take care of the rest. It is a service I am planning to bring to CA. I just haven’t had time to get it together.
As for the airports. One of the members of the US group knows someone on the Google mapping team and is discussing the issue with them. When I hear something I will come back here and let you guys know. But don’t hold your breath, I wouldn’t expect anything soon.
-Ski
Thanks for the explanation. I also submitted this in regular Google Maps with the “report an error” function. Hopefully one of these solutions will take effect!
Not to go too off-topic, but we also have a similar problem in Toronto, where Waze tries to route users to the middle of the runway.
The temporary solution for us is to navigate specifically to either Terminal 1 or Terminal 3 at Pearson International.
Live Maps
Navigating to Toronto Pearson International Airport
Navigating to Terminal 1, Toronto Pearson International Airport
Perfectly on topic.
I have had a huge routing issue at the San Diego airport for some time now as well. Only for me, it was routing people into a military base. Well trying to, the Marines aren’t very friendly…
I spent a while and measured out the distance from the Google marker to all the roads surrounding.
What I ended up doing is disconnecting a few roads on the base that are special access only roads. Not even normal military individuals can go there. Now there were a few GPS traces there, so it might annoy a few. But those few compared to the 100’s of UR’s and people being late/missing flights is well worth it for now in my opinion.
Waze will soon change how it prioritizes it’s choice of destinations anyway.
I do not know what this road leads too, another terminal? A private part of the airport?
But I am guessing all (most) of the GPS points are from people being routed wrong. I cannot edit here to see the UR’s or measure distances myself with segments. But if this area is low access and can suffer the loss of routing for a bit, I would suggest disconnecting the road there and seeing if it will route to the correct side again.
I know this can’t always be done, and isn’t a great solution, but it can work and will hopefully only have too for a bit longer.
-Ski