dbraughlr wrote:Among highways, it would be nice to have Waze calculate something like between Rapid City and Billings whether to follow I-90 or US-212. While most drivers might find I-90 faster, an individual driver who wants to go no more than 65 mph anyway might find that US-212 is faster. But it seems that Waze doesn't offer this fairly direct route. By Waze's calculations, using US-212 saves 44 miles but adds 4 minutes to the trip. In reality, someone who drives this route will average a higher speed across most segments because local traffic drags down the average speeds. Regardless, saving 44 miles can be worth 4 minutes.
I don't believe that combined traffic data on individual segments can solve a problem like this.
dbraughlr wrote:I did not see why it isn't the first alternate. It is a good route - an example of a route that Waze should not avoid. It is mostly straight highway. (I am not suggesting that 212 mH should be upgraded - only that Waze should consider it based on traffic data.)
Thortok2000 wrote:dbraughlr, the setting is 'fastest', not 'fastest unless we think there's a better way.' So 4 minutes makes the difference. =/ That's just kind of a limitation in the system.
daknife wrote:Take a look at this location what is the functional difference between the two roads? They are both built identically, one is part of a US hwy stretching from Canada to Mexico, the other is a State Hwy.
(I also admit to a slight dislike for the Major type because the color used in the App is too close to the heavy traffic color occasionally making it hard to tell at a glance whether that's a Major hwy ahead or a major traffic jam that I need to avoid.)
Users browsing this forum: Google [Bot], herrchin