Hello
This airpot is sending people around the back, having a look at it the location looks good and was updated weeks ago.
The street address was wrong so I’ve corrected that (it needs authorising) but I didn’t think that would make any difference, i thought it was about the point?
You can blame this on Waze preferring Google Maps results over its own mapped places, and then navigating to the closest segment.
You need an L3 to link the Google data to the Waze place and then Waze should route to the destination marker even if the users selects the Google result in the App.
Address change approved and Google link added :mrgreen:
Norwich International Airport? Forgive a brief smirk and then I’ll get on. 
:roll:
Right. I see that Iain has pulled the Access Point right down to the terminal building and even a L1 Editor some time ago named some otherwise un-named roads approaching the terminal building/long-stay car park “Norwich International Airport” - my favourite trick for trying to resolve problems like this. But all will be to no avail if the primary source - much as we may grumble about it being such - is wrong.
And Google is wrong. It’s marker pin is slap-bang in the centre of the main runway, as it was for Limoges and perhaps countless other airports. This is as Mandarin in its accuracy as it is useless in practicality - even Google can’t navigate to the damn place. It gets nearer than Waze does though, as is often the case.
I’ve had some success with this in the past, so have tried again to move the mountain a bit closer to Mohammed . . .
I’ve suggested to Google that it move its marker, like Iain has Waze’s, to the front door of the terminal building. It’s a not unreasonable request.
Don’t cross things or hold anything - these appeals to reason can take weeks - but if I can find this thread later, I’ll post any good news on it and then Googleers and Wazites both will be able to drive to this gateway to international travel with some confidence . . .
Mike
Even if, as suggested above, the Waze place is linked to the Google place? This flatly contradicts my own experience of using linked places… You do have to pay attention to make sure you’re linking to all of the Google results which may be thrown up for a place, but so far every time I’ve linked a Google place, the effect on in-app routing has been almost instantaneous. Usual caveats about not trying to re-route to a location that your app has already cached locally, of course.
Also to note here that, you really need to be testing the effects of Google place linking within the app, not using Livemap - the latter still returns the Google location for the airport, whereas the former returns the Waze destination point for almost every variation of search result I’ve tested.
The only one which differs slightly is the result for “Norwich Airport Ltd” which doesn’t appear to have been linked to the Waze place, but as its native location is just a few yards away from the Waze location anyway, the app simply tries to navigate me slightly past the front door of the terminal rather than off to a completely incorrect destination around the far side of the field.
Thanks all, I’ve just tested it on my app and it’s correct, but not Livemap. I assumed they would be the same so I that’s useful to know in future.
Cheers