osrm-backend

OSRM can be augmented with your traffic data. https://github.com/Project-OSRM/osrm-backend/wiki/Traffic It works quite well.

If you track the vehicles every day and collect the location data, you can easily augment the Open Source Routing Machine to give you traffic accounted estimates.[0] Combined with some Kalman filters you'd get almost perfect estimates when live. Of course, this is for a use case where you have similar routes every day, this allows you to really tune the Kalman filters. 0: https://github.com/Project-OSRM/osrm-backend/wiki/Traffic

PSA: Open Source Routing Machine (OSRM) was largely abandoned by its maintainers. Several of us are working to reboot it, so if you enjoy map data and/or graph theory and have C++ skills, this would be a great project to work on. https://github.com/Project-OSRM/osrm-backend/ (Reboot discussion at https://github.com/Project-OSRM/osrm-backend/issues/5209)

> 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. 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 ov