Doing deliveries in Liverpool today (an area I don’t know well, as will become clear)
Going from Bem Brasil, Hanover St (L1 3DN) to Viva Brasil, Castle Street (L2 0NR)
According to Google Maps (now I’m home) this is an 8 minute drive
Waze directed me to the M62, A5300, A533, A557, M56, M53, up to Birkenhead, then through the Queensway Tunnel (despite being set for no toll roads) then when I came out the other end suggested I did the route all over again!!!
Detour of around 55 miles.
On the Live Map, L2 0NR’s nearest road is A41(E) Queensway Tunnel and you would have to use the tunnel both ways to get there. However that would only take 12 minutes at this time of day. Of course you didn’t want to be in the tunnel at all.
It may have been there was a road problem somewhere and that is why you were redirected.
I would suggest that you always check the route map of the routes you are offered in areas you don’t know.
I would also suggest that the street can be better than the postcode, but I think your problem occurred because Viva Brazil is pretty well directly above the tunnel entrance road.
I think the problem is a combination of the Waze map and the way Waze copes with being told to go to a postcode. Waze has no knowledge of postcodes, instead asks Google, which in turn looks up information supplied by the Royal Mail. This gives a point for the postcode (which is inherently unsatisfactory as postcodes usually cover an area). Anyway, Waze then navigates to the closest road to that point.
Typing L2 0NR into the editor, you can see the pin drop at a point between Castle St and Fenwick St. The closest map road to the pin however is neither of these, but the eastbound lane of the Queensway Tunnel. So the eastbound road through the tunnel is where Waze is going to try to get you to, which of course means that it has to get you to the west side of the Mersey first.
The avoid tolls setting will have no effect on using the eastbound tunnel, since this is the only way of getting to the closest point to your destination. However, avoid tolls will kick in and cause Waze to avoid the westbound tunnel, hence your massive diversion.
So what can be done about this?
The precise route of the tunnel on the map isn’t important, since GPS doesn’t work in the tunnel thus Waze has no idea of the exact line. Moving the tunnel to the other side of Brunswick St would prevent the problem for this particular postcode, but would probably create the same problem for a different postcode.
Adding Viva Brazil to the map as a “place” would help, but only if it was carefully positioned, and you ask Waze to navigate to the place rather than the postcode. I’ve added it now, carefully positioned to be nearer to Castle St than the tunnel.
Likewise if you asked to navigate to Castle St instead of the postcode, you could be sure of getting the right road, but not necessarily the right part of it.
I wonder whether there might be any scope for putting a facility into the Waze search so that it ignores roads of elevation -5 (or +5 for that matter) when looking for a postcode?
Ian
At Iain House’s suggestion, I’ve added a walking trail (footpath) linked to Castle St on the postcode side of the tunnel. So if you put L2 0NR in now, Waze will take you to the start of a footpath that doesn’t exist - but at least it will take you to somewhere on the surface rather than down a hole.
Think that’s the best we can do. Unfortunately it’s reactive; once a problem is reported, we can prevent it recurring for the same postcode, but it’s not practical to anticipate it for every postcode along every tunnel (or bridge).
Ian
I’ve stepped in and tweaked this slightly. 
The 2 changes I’ve made are to disconnect the walking trail from Castle Street and move it well away from the tunnel segments.
What will happen is that Waze will find the walking trail closest to the postcode. Since it can’t actually navigate there, it will route to the driveable segment closest to either end of the walking trail.
The way you had positioned the walking trail segment would have hidden it “under” the tunnel segments - but also left it very close to them, so Waze might still have routed to the tunnel. Instead, I’ve run it directly from the postcode location to Castle Street. Note that it is nearly invisible in the app.
I also disconnected it from Castle Street because, I suspect, Waze will route up it if it’s connected. As long as that end is closest to Castle Street, the “magic” works.
:ugeek:
This has always been a major issue and have responded and tried to fix many URs where drivers have been directed to use one of the two tunnels we have directly under Liverpool City Centre.
As you two did, my usual fix is to check if there is a place for that destination, check if there is a Google place and try and move what is possible.
I think as Ian mentioned above, Waze ignoring any -5 or +5 roads from its final navigation might be the best fix as you would never be ending a journey there (or at least you shouldn’t be!)
I’ve been informally advised that Waze will never agree to this.
So we’re stuck with firefighting, I’m afraid.
Ian
I presumed that would always be the answer!
A very simple change would be two check boxes similar to ‘Toll Road’ that would be ‘Tunnel’ / ‘Bridge’ (or even just one that when ticked would prevent navigation). In that way Waze would only use those segments to navigate through and never as a destination.
I won’t hold my breath though! 
I’ve had another tunnel routing disaster UR for a place called Beetham Plaza. I’ve added a place on Waze for it. Reporter was a bit irate because he was late for a meeting and had to pay the toll, twice (I just think he should have look out the window, but hay ho).
Looking at Google Maps, Queensway looks like it’s only down as a single carriageway when on Waze it’s a dual. The postcode (L2 0XJ) for this place also direct drivers down the Queensway tunnel. Are we going to have to add ‘footpaths’ for all postcode points above the tunnel? And maybe also for the Kingsway tunnel?
Just an idea, would adding a footpath like this have any impact on the problem, a catch all? Probably not, but I’m throwing it out there anyway.
It looks like this place has an underground car park accessible off Brunswick St, if this was added it would act as a destination instead of the tunnel. I would suggest the car park should be shown as a “L” shape (running along Brunswick St and The Strand) regardless of what it actually does underground - then lock to L5.
Are we making it harder for ourselves by showing the two carriageways of the tunnel so far apart? With Brunswick St apparently between the two carriageways we are going to be causing problems on both sides of the road. If the A41 (W) was moved north of Brunswick St then that would also cure this problem. Is there any reason why the two carriageways can’t be mapped almost touching each other?
Feel free to shoot me down on this:
Does the Tunnel have to 100% match it’s route?
You don’t get GPS once under ground and Waze does not ‘route’ while in the tunnel.
My suggestion would be to either:
a) move the segments of the tunnel further apart away from routable surface streets, or
b) move the tunnel north, closer to Water St and put the 2 lanes as close as possible?
If these suggestions are bad, please let me know 