Now we have 2 route options: shortest and fastest.
There are no doubts how shortest is calculated.
Fastest route is somehow tricky as I have noticed. It is truly fastest intracity routing. A quite regulary drive routes more than 100km. This makes difference. Routing server tries to avoid driving through cities. This is completly wrong and I most of the time ignore directions to take highway. Driving through cities is faster always even in congestion time. I know it is a lot harder but it's worth that. Some have noticed that this routing preference change ocurs roughly on 10km route. I can presume that this is done to preserve routing server resources as there are a lot more road segments per distance in cities than countryside.
I read soon Waze infrastrucure will be capable of dealing with additional work. My suggestion is to rename route "fastest" to "easy" and make new one "fastest" routing option that routes through cities even for longer drives.
Now we have 2 route options: shortest and fastest.
There are no doubts how shortest is calculated.
Fastest route is somehow tricky as I have noticed. It is truly fastest intracity routing. A quite regulary drive routes more than 100km. This makes difference. Routing server tries to avoid driving through cities. This is completly wrong and I most of the time ignore directions to take highway. Driving through cities is faster always even in congestion time. I know it is a lot harder but it's worth that. Some have noticed that this routing preference change ocurs roughly on 10km route. I can presume that this is done to preserve routing server resources as there are a lot more road segments per distance in cities than countryside.
I read soon Waze infrastrucure will be capable of dealing with additional work. My suggestion is to rename route "fastest" to "easy" and make new one "fastest" routing option that routes through cities even for longer drives.
What do you think about this?