@GlockGirl1, I apologize for not responding quicker. I am out of the country right now with limit time and access. I will get back on this early next week.

One thing you mentioned in the report thread was that Waze would eventually reroute to the preferred route. Please let us know where that occurs.

Thanks,
Chuck

Duplicate post deleted

Duplicate post deleted

Duplicate post deleted

Duplicate post deleted

Duplicate post deleted

Duplicate post deleted

And that is apparently what happens with flakey international connectivity. Sorry for all of the duplicates.

Just a reminder to let us know where Waze reroutes and finally chooses your route. If it's at an intersection, what are the cross streets. If it's in the middle of nowhere, what distance is it from some identifiable landmark or cross road. Thanks.

So, looking at your UR thread, you actually got the 2 best folks to fix it. Chuck happens to be a Denver area manager and Josh is the state manager. Both are excellent editors.

One of the things not mentioned in the thread is that over longer routes, Waze stops looking at smaller roads. This saves processing time, and generally speaking, a smaller road is less efficient and less likely to actually produce a time benefit. There's a long and convoluted explanation about how and why roads are mapped as they are, but I'll boil it down to "if Josh and Chuck feel the roads are mapped correctly, then they are."

If you are 100% sure that your way is faster, then I would suggest ignoring Waze until you get to a point where you need the app again. I do that often near my house, but in my case it's because the roads are not traveled enough to generate reliable speed data.

Sorry for not being able to give you exactly what you want.