Waze was crazy this morning...

[thoalex]

I know everyone is going to say there are lots of posts on this but what Waze was trying to do to me this morning was just jacked up.

I take the same route every morning. I live in Las Vegas, I go 215 to Summerlin to 95 to MLK. I do expect Waze to reroute me if there are accidents or some other reason to NOT go those paths. I understand that's kind of the point. But this morning...?

First, it always tries to get me to go straight to 95 from where I live. It doesn't understand that there is construction on part of that road that I'm avoiding like the plague. It's a mess at Cheyenne and 95 and I'm not going near that mess.

So, I let it think I'm going 95 and then I just go to Summerlin and it usually re routes. This morning it KEPT trying to get me to go to 95. Finally it got the hint (but not until I was ON 215). But then...

There are three exits that I can take. One is short and fast but sometimes has traffic and Waze has rerouted me away from this to the second one. Today, it tried to send me to the third one which is absolutely the worst. And it did it for no reason. The first two were completely available.

Again, I know there are a lot of posts about this but this sounds like a defect more then anything else.

[RallyChris]

Without any permalinks or livemap examples, it's hard to diagnose if this is a map issue which the community can help with, or a routing code issue which only the developers can deal with.

It helps to provide the permalinks as waze community members might not have enough knowledge of the area to be able to test for map issues without them.