> There's no way to optimize for minimizing left turns
Any decent road routing engine does take into consideration a "turn penalty" and makes left turns more costly then right, among other things. E.g. see the Valhalla docs (Mapbox's routing engine):
> Turn type - whether the turn is a left turn, right turn, or is crossing another road. The cost applied to the turn type also needs to know if driving is done on the left side or right side of the road. While left turns are generally more costly in the US than right turns, the opposite holds in UK.
With routing applications there are many configurable parameters, rather than providing too many options and risking overwhelming the user some of these things are simply baked into the ETA calculation.
Any decent road routing engine does take into consideration a "turn penalty" and makes left turns more costly then right, among other things. E.g. see the Valhalla docs (Mapbox's routing engine):
> Turn type - whether the turn is a left turn, right turn, or is crossing another road. The cost applied to the turn type also needs to know if driving is done on the left side or right side of the road. While left turns are generally more costly in the US than right turns, the opposite holds in UK.
https://github.com/valhalla/valhalla/blob/716fd6e99ab6f271b6...
OSRM also does this, but slightly differently: https://github.com/Project-OSRM/osrm-backend/wiki/Traffic#tu...
---
With routing applications there are many configurable parameters, rather than providing too many options and risking overwhelming the user some of these things are simply baked into the ETA calculation.