Calculate the best route based on both shorter time and distance. Not just one of them.
I prefer the fastest way, but only when it is reasonable.
I can never trust the option automatically suggested for me and I always find myself checking the routes. In many cases I switch to the second option.
For example:
Option 1: 49 minutes, 58 Km
Option 2: 50 minutes, 47 Km
I would rather spend 2% more time than spend 21% more fuel...
Most people would prefer spending another minute in this case. Why do we always have to bother going to the routes to find out.
The user can select his preference for either shortest or fastest way but I want the fastest way that is still reasonable.
Let us define the time/distance trade-off we prefer, or at least define a reasonable hard-coded default.
-
Liran Friedman commented
שלום,
רציתי לנסות ולהציע הצעה קטנה לשיפור.
כרגע, הגדרות הניווט מאפשרות בחירה בין אופן חישוב מסלול הקצר ביותר או המהיר ביותר.אף אחת מבין השניים היא לאו דווקא האופטימלית ביותר בכל מצב.
מה שהכי מעניין זה באיזה מסלול ייקח הכי פחות זמן להגיע ולפעמים צריך לעשות הלוך ושוב בין ההגדרות הללו על מנת לבחור באיזו דרך אני אגיע הכי מוקדם בפועל.לכן, חשבתי להציע אופן חישוב מסלול משולב אשר יציג את המסלול עם זמן ההגעה המוקדם ביותר על סמך 2 אפשרויות חישוב המסלול הקיימות, הן המהיר והן הקצר.
-
Bart Youngblood commented
I agree. There needs to be a more significant amount of time saved based on the total length of the trip before it defaults to one that results in a significantly longer route. I, too, find myself checking the routes before I go to make sure I'm not driving an extra 4-5 miles just to save (on average) 1 minute of driving time.
An easy way to solve this would for the routing server to look at the average time and distance of all three choices. If the shortest time wise is also the longest distance and exceeds the next fastest route by a certain percentage of the average route length BUT saves a significant amount of time (15-20%) over the average travel times, then it will still take the longer route. However, if the time saved is insignificant, it will take the next fastest route.
Simply put, saving 1 minute on a 30 minute drive isn't significant enough to make me want to drive even 2-3 miles longer. Same goes for some of the really odd routes it suggests at times to avoid making left hand turns (going straight through, pulling a u-turn, then turning right at the desired intersection, for example). Instead of simply basing route choice off of a fixed amount of time, it needs to be tied to the time saved as a percentage of the total route time.
-
Mathews commented
Very true, I think , it is best to by your experience of the Roads - Traffic Patterns.
Some roads are taken by slow drivers, Some roads are faster, though they pass thru construction zones.
Waze has never saved me a lot of time. Compare it to Garmin - it just about does the same. The only advantage, it will find you back roads. Well, then your knowledge of the area can surpass this and you would be a better judge of the suggested route--- will going through a back-alley with 6 - 8 Stop Signs, and getting stuck in a long traffic light.... Hmmmm.
Waze very difficult to understand... and difficult to keep up with.@Revital Ferster I like your point.... Sometime the time saving is so insignificant... . On most occasions Waze shows a big time saving, and as you near the destination - it say Oops!! traffic is building up and shows a BOLD RED LINE.. as if I never knew.
But yes, Thanks to Waze i learned all the back roads of toronto really well. Don't use the app anymore. It is plain confusing, and it like having a nagging backseat driver.
I am not driving an Ambulance or an emergency services vehicle. -
James commented
Absolutely. Every single morning Waze presents me with 3 options:
1) 25 miles, 30 minutes
2) 15 miles, 32 minutes
3) 16 miles, 32 minutes.
It always defaults to option 1. Route calculation should take into account time and distance. -
Mathews commented
This is a wonderful idea.
-
G commented
Go back to the old way of finding the best routes, avoiding traffic, and estimating arrival times. The last few weeks have given bad information on all three items. I now use my car navigation because it's working MUCH better than Waze. Waze used to be better.
-
Bill commented
Waze is supposed to remember if you repeatedly take a different route (ignoring and letting it recalculate). I find it may still override me it if it thinks it finds a faster route. I sometimes see this is I go my usual way for late afternoon, but at midnight for example.
-
Revital Ferster commented
An hour ago I got these options (luckily I checked the routes):
Waze best option: 45 minutes , 50 Km , toll road
Second best: 51 minutes, 23 KmDefault route indeed saves 6 minute (11%) but is more than twice as long, and moreover, you have to pay.
Would most people prefer to pay more than twice as much, (fuel+toll) just to arrive 6 minutes earlier? A smarter algorithm would have probably switched these two options.
-
Arturo Flores commented
So WAZE select the faster or nearest way to take, but sometimes the difference between my preferred road and others is just 1 minute, what if user can select the fastest way considering certain period of time, according with what the users consider acceptable? i.e. 5 minutes for me is ok if I can use the road I like
-
Alon Avni commented
Calculate best route using also known future traffic jams.
Correct me if i'm wrong but waze calculates best route by using current status of trafic (according to reports). But if I know that an hour from now, a traffic jam will occur, waze can know it also by collecting data of repeated jams of previous days.