Hi,
There is always a number of User Requests around Melbourne Airport with people complaining they are being directed to the back of the airport. Now I know, and I’m sure readers of this forum would know that a search for T1, T2, or T3, or the BP or any of the parking towers will always take me to the right place, but the average user will just search for Melbourne Airport.
What I think is happening is that although the Melbourne Airport place shape has it’s ‘entry point’ on Departure Drive, as it should, the Melbourne Airport city shape has it’s centre pin in the middle of the runway.
Using the Live Map, a search for Melbourne Airport from some random place nearby shows the result.
I actually came on the forums tonight for the same reason. There are UR all around the airport with similar complains, wrong directions, being directed to the (inaccessible) tarmac.
Some of these reports are on ‘link road’, and so it’s possible some of these are being redirected due to heavy traffic.
However there may be some of these that are being caught up with the construction and constant re-configuration from Melbourne Airport.
With so many reports, I think at a minimum until a fix can be decided on, there be a unified response to reporters.
I suggest "We’re aware of some navigating issues concerning Melbourne Airport at present. To assist in making Waze better, can you please tell us:
What time of day were you travelling?
What did you search for in Waze?
Which terminal were you after?"
This might give us better insight to the root cause.
I agree with HairyDrumRoll that what is probably happening is that the App is navigating drivers to the centre of the “City” or “Suburb” shape. I checked my references to confirm what the official suburb name is, and can confirm that the entirety of Melbourne Airport is encompassed within a suburb named “Melbourne Airport”.
When I do a search, since I have not driven there, the first results are all the Terminals and Departure Drive. It is only when I search for additional results that I get the middle of the airport/taxiway marker.
One of the possible contributing factors to the problem is possibly due to the App’s caching behaviour for recent and favourite drives. Once the App has cached the location for a destination, it will hang onto it until it is manually cleared. It might be possible to resolve some of the issues by advising drivers to clear the previous “Melbourne Airport” destination(s) for Melbourne Airport.
Tap the “Search”, locate the cached result, tap on the vertical …, and select Remove from the options.
Also, there is a error flagged for T4 (https://www.waze.com/editor/?env=row&lon=144.85109&lat=-37.67515&s=120821847&zoom=5&mapUpdateRequest=10187217) which highlights that directions for T4 try and take drivers to the wrong location.
The T4 ‘Shape’ has an entry point where it should be, but the LiveMap seems to direct users to the wrong location. Why is this?
And can someone (level 3 or up) please rename T4 to “Melbourne Airport - T4”
This is where a search for “Melbourne Airport” takes you. This is where a search for “Melbourne Airport, Australia” takes you.
Neither of these are where you want to be!
I’ve just checked in the app and a search for ‘Melbourne Airport’ is directing me to Arrival Drive in front of Terminal 2 as expected. We might just have to wait and see if anyone else flags the issue again.
Hi editors… Seems to be a super massive build up of UR at Melbourne Airport again. Most require level two, some higher. I’m still on level one (trying really hard to to get to 2) so I don’t think i’m much help yet…
I live 5 minutes from the Airport, so hopefully moving forward (when i’m a higher level) I can try keep on top of them.
I have found the Google Map Pin for “Melbourne Airport (MEL), Departure Dr, Melbourne Airport VIC” which was providing a bad location. A request is in with Google to move it.
