Salt Lake City to Las Vegas

by **Dev745** » Thu Nov 22, 2012 3:22 pm

Hello,

Waze could not route Salt Lake City to Las Vegas via I-15. It routed via I-80 to Reno the south, for 986 miles. It should route via I-15 which is 390-ish miles. It would not reroute, but kept instructing me to turn around. Love the app. And thanks for your help.

by **txemt** » Fri Nov 23, 2012 5:44 am

Is there a certain point that it gets up to before it tells you to turn around?

by **pnordi** » Fri Nov 23, 2012 3:05 pm

I did that drive a couple weeks ago and it worked fine for me.

[Edit] I just tried routing and it sent me on I-80 through Reno. I will check out the map and see if I can see any problems.

Sent from my iPhone using Tapatalk

by **daknife** » Sat Nov 24, 2012 4:33 am

I've been looking at this for a couple days now. Tracing along the route in the editor as well as trying from various start and end points on the live map. Still trying to find the cause of the problem. I started on it due to UR's complaining about it being unable to route from SLC to Barstow CA. Sure enough I can route from SLC to LV and St. George UT to Barstow but somewhere in there is a discrepancy that bounces everything up across I-80 to Reno or into CA before coming back down.

by **daknife** » Sat Nov 24, 2012 4:57 am

Now it might simply be distance, isn't there a max distance Waze will route?

by **pnordi** » Sat Nov 24, 2012 5:26 am

I think it is 1000 miles. But, the route through Reno is longer than the route south on I-15 so that doesn't make sense.

Sent from my iPhone using Tapatalk

by **daknife** » Sat Nov 24, 2012 6:11 am

Found what was most likely the problem, A turn restriction at the southern interchange for Beaver. And it's a mea culpa. I remember working on that interchange back in Oct when I found the SB on ramp wasn't even connected. Evidently in connecting it I somehow did a Q but not the following W on the junction.

Only question is why wouldn't those long distance routes go from Beaver to Minersville, down the minersville hwy to Cedar and get back on 15. It would add about an hour to the drive, versus 10 hours to go west via 80 then down.

But I also came across some areas where level 1's had been playing with the lanes so I've locked almost everything south of Fillmore, I'll get the stuff to the north later on. But locking it should reduce these occasional issues, this is the first I caused but the third or fourth time We've seen this problem crop up since I've been editing. So I'm confirming the green arrow at the end of each segment, then locking it.

by **daknife** » Sat Nov 24, 2012 6:16 am

And interestingly enough My sister went through there a week ago with no problems at all.

One last note, I locked it all the way down to the north Cedar Interchange, I'll take it to the border or further tomorrow. I'm not a fan of locking but if a careful scan and lock will prevent or at least reduce the likelihood of these problems in the future so be it.

by **txemt** » Sat Nov 24, 2012 6:51 am

I went from Vegas to...somewhere in Utah and didn't find anything wrong. I did some changes, but nothing too major. I linked some links together and renamed a few segments, but other than that, connection wise, everything looked good.

On another note, a lot of the I-15 Southbound lanes aren't labeled as such, but the northbound lanes are.

by **pnordi** » Sat Nov 24, 2012 2:35 pm

Good news. Your edit must not have been pushed out in a tile update last time I drove down there. Thanks for your help!

Sent from my iPhone using Tapatalk