Opened 4 years ago

#1205 new enhancement/feature request

Take into account the cost/expense of turns in routing

Reported by: tylla Owned by: KaZeR
Priority: minor Milestone:
Component: core Version: git master
Severity: normal Keywords: turn, cost
Cc:

Description

Currently there are scenarios where Navit calculates strange routes. The logical route would be this: http://osrm.at/79y where the route that Navit calculates is this: http://osrm.at/79z (I had to insert a waypoint, because osrm calculates the other route:-)

I suppose this is because Navit doesn't take into account the 3 turns needed to complete the route and it calculates that going on the higher level roads would yield faster route. But in this case this isn't true, the distance is bigger, and with the 3 turns it is really slower.

The turns' costs should be taken into account when calculating a route. The higher the turn degree, the higher the cost. This way this could integrate #77 by automatically including a high cost for a U-turn. Further a left turn could have even higher cost than a right turn (naturally in left-driving countries it should go inverse).

Change History (0)

Note: See TracTickets for help on using tickets.