Routing issue - Lane Cove Tunnel vs. Epping Rd

Hi,

I have found on a number of occasions that Waze has routed me via Epping Rd. rather than the Lane Cove Tunnel as part of my route from the city to North Ryde.

I do not have ‘Avoid Toll roads’ turned on.

There has been no accidents or other obstructions in the tunnel at the time so there is no way possible that taking Epping Rd is faster than the Lane Cove Tunnel, especially given they effectively start and end at the same points.

This appears to be a routing issue of some sort?

Correct, so have either come off the bridge (or Harbour tunnel) and am on Gore Hill freeway.
My destination is actually my home address in Pymble so the goal is always to end up on Lane Cove Road heading East toward Pacific Hwy. Lane Cove Tunnel and Epping Rd both lead to that same intersection in the same way.

Fastest route should always be straight down Lane Cove Tunnel.

Instead, when this occurs, it is always keeping me to the Left, past LCT, past Reserve Rd exit (on right), past Pacific Hwy exit (on Right), and keeping me on Epping Rd the entire way to the Lane Cove Rd intersection.

I rarely get routed via LCT.
Usually it is exit via Pacific Highway for me.
I assume it is incorrect speed data in the tunnel.

On some occasions I have been instructed to Exit Right to Pacific Hwy, Newcastle / Artarmon. Other times, it does not and keeps me heading to Epping Rd.

I think the deal-breaker scenario for me was when I was coming back from the airport heading to Pymble and hit Gore Hill freeway at around 5:30am. No traffic anywhere. It absolutely should have sent me through the LCT but instead it kept me heading to Epping Rd.

I’ve noticed it happens on the cross city tunnel too when checking routes on livemap in the past, I drive with the avoid tunnels box ticked but on at least 1 occasion when I’ve been waiting at the lights at bathurst/harbour st intersection I’ve been snapped into the tunnel and waze has assumed that I was in the tunnel till after I turned right onto Elizabeth St, so I would assume that my slow speed on Bathurst St would be allocated to the Cross City Tunnel, with Route speeds in the past you could see there were some warped speeds like below 10km/h in the tunnel although I haven’t checked recently. I think it’s a problem we are just going to have to live with at the moment. At least we know waze is working on a solution for tunnels, getting the government to install it is a different story.
https://www.waze.com/beacons

So I’ve been keeping a close eye on this every time I start a trip from the Eastern Suburbs or Airport to my home in Pymble and I’m still getting routed via Epping Rd rather than the Lane Cove tunnel each time.

What I have observed, is that if I manually force it to recheck routes at some point along the Gore Hill Freeway, it will generally change the route into the Lane Cove Tunnel.

I note earlier in the thread there was some speed limits fixed, when would that like have ‘gone live’ (roughly)? This would help me know which change is resulting in different outcomes.

Still seeing incredible inconsistency on this route.

if I set a route home, starting from anywhere city-side of the harbour, it will route me down Lane Cove Rd. unless it specifically wants me to take the Pacific Hwy exit.

There is still something wrong with the Lane Cove tunnel.

I’d posit that some of the misleading route time information is due to the closeness of the alignment of Epping Road and the Lane Cove Tunnel alignment at near the Centennial and Longueville Road intersections.

For example, today I saw URs of heavy traffic with the location given as ‘M2 Lane Cove Tunnel’ when you clicked on the report.

Of course, considering that you wouldn’t be able to get a GPS signal in the tunnel (and you can’t make URs with no GPS signal), this UR was almost certainly associated with Epping Road. I also would expect that there are occasional glitches where Waze locates slow moving traffic on Epping Road and shifts them (and their associated traffic statistics) over to the Lane Cove Tunnel.

Waze is obviously not smart enough to deduce that if a UR is made next to both a road and a tunnel, to preference the road because you can’t get a GPS signal in the tunnel.

I think a good thing to try would be to shift the tunnel north or south of its actual alignment by about 100 metres so that this cannot possibly occur.

At the moment (9pm on Saturday night), the Lane Cove Tunnel is marked with a 17km/h routing speed westbound (when using WME Route Speeds), which is clearly incorrect. The other direction has a 80km/h routing speed

Raising from the dead.

Route times from start of tunnel to end of tunnel as follows:

Monday 5:30pm
Using tunnel - 8min 29 sec
Using Epping Rd - 9min 43 secs

Saturday midnight
Using tunnel - 5min 40 secs
Using Epping Rd - 6min 20secs

Whether the times are accurate or not (due to close alignment, etc) the tunnel should always be a preference based on the historical time data (at least at these times).

If current traffic data is skewing the results, I don’t know, but (except for an accident) there would be no occasion when the tunnel was the slower option.

At this moment, the Live Map will route via the tunnel, but the app does not even use the tunnel as a potential option, with Epping Rd being the preference.