Thortok2000 wrote:Essentially, my main problem with this system is that it's got two major flaws in my opinion. The first is that the routing system has a pretty high penalty for NOT using major highways and freeways when they are available. There are plenty of times where a 'shortcut' would more than likely be faster, but because it's not a US highway, Waze wants me to take the US highway as far as I possibly can before getting off it closer to my destination, assuming traffic is clear that day. Generally speaking, unless there's a traffic jam on every route that includes a major highway, then the only options I ever get are major highways, from the closest point to my starting position all the way to the closest point to my destination.
Except that doesn't actually happen in places typed to NFC+US/SR.
Every route shown takes multiple miles of Primary, the third option additionally uses 1.9 miles of Street that parallels a Major Highway (Colorado Blvd).
Current routing basically does what you'd like it to if:
1. The map is very well edited. This is still rarely the case outside of major metros.
2. The map has actual viable routes typed appropriately.
NFC seems to fit the routing model very well, and is what your State's DOT thinks the viable routes are. This is not an accident as Waze's routing model in the absence of historical and live speed data is based on the classification system of the time. This still matches fairly well with the current classification system which is a simplified version of the older one.