City driving is different from suburban or freeway driving, due to increased traffic, and more importantly, unpredictable pedestrians and bikes, that are not part of Waze's data. Turning left-then right-then left-then right to save 1 minute often actually takes longer; changing lanes within one block can be impossible in heavy traffic, and waiting for pedestrians to cross the street when you want to turn negates any time savings. It may be a big process, but having a different algorithm for city rush hour driving would be beneficial.

Would like to see a tolerance setting added. For example, don't switch me off my usual route unless a new route saves me at least x minutes.

I frequently get routed to a major highway with the resulting route taking longer AND having more miles than my usual route (which typically end up being option #3). I cant figure out how to stop this. It's whacked! Other navi apps have something called an optimal route, I.e. sacrificing a few minutes for a much shorter route is OK. But driving 10 miles more to save less than a minute on a 35 minute drive is NOT OK.

With this option, users will not be asked to drive an extra 3 miles in order to save 1 minute, which is what happens with the "fastest" route style option. X minutes = Y extra miles (extra compared to the shortest route). This saves time, money, and is most energy responsible.

let us be able to view them on the map also with choies them

Instead of redirecting my route to save (for example) two minutes, I'd like waze to know what routes I prefer and only divert me if an alternate route saves me a time amount of my choosing.

For example, only reroute me if the alternate route saves me 10 minutes. In other words, only take me through the sticks if its really worth my while...and I'll tell you what's worth my while.

I have the client set to choose the shortest route. Sometimes when I look at the routes there a re a number of alternatives with by similar ETAs. While I'm usually keen to get to get to my destination as a soon as possible I don't want to go on a long detour to save one or two minutes.

Can the routing server identify such a situation and make a sensible choice. I guess similar issues may be in play for toll roads.

Perhaps you could consider travelling 5 miles to save 1 minute excessive but anything less than this ratio is acceptable.

There are already many options which affect a Wazer's routing, and many many more suggested on these forums. But sometimes a user will deactivate features without realizing their worth. For example, I never want to take a toll road, so I have those disabled -- but if I was stuck in traffic, and a toll road could save me some ridiculous amount of time, I might consider it, despite my usual preference.

So I would propose that any preferences which affect navigation can sort of "self-activate." Perhaps the user could set a time or distance delta threshold before the option flips on. Or perhaps when Waze determines that it really really is in the driver's best interest, it can suggest using that feature (rather than just rerouting).

There should be more that 3 suggesting routes that include and don't include highway and tolls!