There’s a UR saying that Waze is consistently avoiding the Lane Cove tunnel to get from Macquarie Park to Manly. I’ve tested this on the live map & it’s true. Waze does avoid Lane Cove Tunnel, even with tolls turned on. It seems that Waze thinks this segment is extremely slow, at 9km/h, & is therefore routing via Epping Rd instead.
Is this an issue because this is a tunnel & Waze doesn’t have GPS to calculate speeds, therefore has no idea what’s going on? Is there any way of fixing this?
I commute from Macquarie Uni to Sydney CBD every working day. Not enabled ‘avoid toll road’.
Waze never route me thru Lane cove tunnel on both directions unless I was already on M2.
My guess, waze wants to save me $3.19*2 everyday.
I’ve seen it happen on the Cross city Tunnel eastbound. some of those segments have really low average speed on route speed script.
If your waiting at the lights coming off the Western distributor onto Bathurst St I’ve been snapped into the cross city tunnel and the route only changes when I turned right into Elizabeth St Southbound, so I’m guessing the slow speed on Bathurst St is going into the Cross city segment data.
Can anyone advise on the mechanism of the waze segment speed calculation and routing coding? I have just been considering workarounds to this issue… Bit of a strange idea I know, but what would happen if we made the entire tunnel one segment including 200 meters outside each end - ie enough time for Waze to pick up the GPS signal at the exit end. Would it then correctly record the travel time for the tunnel and route traffic via the tunnel?
I realise the suggestion breaks a few rules - eg seagull rule. Would have to be a common speed limit for the entire length - or the speed limit indication could be removed. And it wont work for where there are undergound exits as these will break the segment. There are no exits westbound on the Lane Cove tunnel, nor on the Sydney Harbour tunnels… worth a trial??
Isn’t this already being addressed with the new “tunnel” flag for road segments? It seems to me like Waze is planning on using the Tunnel flag for this exact purpose when they have enough tunnels appropriately enabled.
Last week I travelled in a westerly direction from North Sydney. Waze routed me to get on the Warringah Fwy/Gore Hill Fwyheading west then exit and use Lane Cove Rd rather than the tunnel. Being a Saturday and also being a scrooge I decided to save the toll and headed up Pacific Hwy with intent to turn left onto Lane Cove Rd. Waze however then rerouted me to use Lane Cove Tunnel - Pacific Hwy entry. Is there some issue with the segments that anyone else can see, from where tunnel branches off Gore Hill Fwy and where the Pacific Hwy ramp enters the tunnel? I have had a look and cant see anything wrong.
I also just had a look, but nothing I could see except some unverified speed limits, which I’ve fixed, although this shouldn’t make any difference to routing.
I was surprised to find the tunnel at an L3 lock though, instead of L5. Is this intentional?
I’ve never had that happen, i’m guessing just bad cell coverage. However i’m never in that right lane, always middle or left lane on bathurst st.
I’ve had something similar on the ED southbound, whenever I’m in the right lane it thinks i’m above ground in surry hills.
When driving north west on gore hill fwy, i get routed on lct when epping rd has 1 or 2 traffic reports. Never routes me on LCT when there is no traffic reports.