michaeljmyers wrote: ↑Thu Feb 22, 2024 5:50 pm I live in Miami.  I do NOT want to use the I-95 expressway durning rush hour - it is the most dangerous piece of highway in the USA according to Google.

There are times when I want "fastest", and there are times when I do NOT want to be on the Miami highways, no way.  To many crazy drivers.

This is one reason for why - maybe I could make the selection using Siri ??

 

The best place to ask for feature requests is here: https://waze.uservoice.com/forums/59223 ... estion-box instead of on this 12 year old post that is way out of date.
We recommend adding your suggestion there, or upvoting a similar suggestion to make it more popular to the developers.
 

I live in Miami.  I do NOT want to use the I-95 expressway durning rush hour - it is the most dangerous piece of highway in the USA according to Google.

There are times when I want "fastest", and there are times when I do NOT want to be on the Miami highways, no way.  To many crazy drivers.

This is one reason for why - maybe I could make the selection using Siri ??

Just playing devils advocate, but if (and I understand how this is sometimes the capital IF) the maps are correct and waze has some good speed data. Why do you want to artificial influence the routing server to potentially give you a route that may not be as fast?

We do know that for "long" routes, the waze server starts ignoring streets and will only use freeways/highways, but are you actually getting better results, or just feel you are getting better results by doing this?

This feature is most commercial gps because they don't know what the freeway is doing, but Waze "Might" and so using this feature seem counter productive to me.