Is elevation change considered in routing?
Are lots of turns/curves considered in routing?
If not, is it possible to implement this?
Example: You have 2 routes from point A to B. Route1 has 100km, no turns, no elevation change, real travel time 70 minutes. Route2 has 99km, but lots of turns and big elevation change (hill area), real travel time 115 minutes. Would the navigator prefer Route2, because it is shorter? (speed limits are constant for both routes all the time from A to B)
According to my experience, the Navigator does not consider this and makes ineffective routing through hill area. Especially Balkan teritory. Where some terrible roads across high passes were prefered instead of little bit longer and straiter roads around the big mountain ranges. Navigator calculated several minutes better time across high pass, but the reality was very different. The travel time was usualy 1,5 to 2 times longer.
Are lots of turns/curves considered in routing?
If not, is it possible to implement this?
Example: You have 2 routes from point A to B. Route1 has 100km, no turns, no elevation change, real travel time 70 minutes. Route2 has 99km, but lots of turns and big elevation change (hill area), real travel time 115 minutes. Would the navigator prefer Route2, because it is shorter? (speed limits are constant for both routes all the time from A to B)
According to my experience, the Navigator does not consider this and makes ineffective routing through hill area. Especially Balkan teritory. Where some terrible roads across high passes were prefered instead of little bit longer and straiter roads around the big mountain ranges. Navigator calculated several minutes better time across high pass, but the reality was very different. The travel time was usualy 1,5 to 2 times longer.
