osrm-backend/include
Daniel J. Hofmann 86fd04e556 Improves lane handling for subsequent going straight, resolves #2625
Before we only worked on subsequent quick turns, as in:
`right, right` keeps the user on the rightmost lanes.

This changeset modifies the logic to work on any subsequent steps
that are "quick" and have lane information we can constrain later.

Because we do not have a from-lane => to-lanes mapping we take the
lanes left and right of the turn lanes into account when heuristically
assigning the leftmost / rightmost lanes.

There are some edge cases where this still does not give us the optimal
solution but it gets close to what is actually possible at the moment
without having a lane mapping in post-processing.

References:
- https://github.com/Project-OSRM/osrm-backend/issues/2625

fix rebase
2016-09-07 12:17:36 +02:00
..
contractor Fix platform-independent data in data files 2016-06-20 22:45:40 +02:00
engine Improves lane handling for subsequent going straight, resolves #2625 2016-09-07 12:17:36 +02:00
extractor Improves lane handling for subsequent going straight, resolves #2625 2016-09-07 12:17:36 +02:00
osrm Exposes osrm::exception for client usage, resolves #2813 2016-09-01 09:12:35 +02:00
server Use mmap instead of read - it's a lot faster here. 2016-06-27 17:24:30 -07:00
storage expose lanes as enums, adjusted for comments 2016-06-27 11:12:02 +02:00
util Improves lane handling for subsequent going straight, resolves #2625 2016-09-07 12:17:36 +02:00