osrm-backend/include
Daniel J. Hofmann d53c267129
Be more aggresive classifying Roundabout Intersections.
Roundabout Intersections are roundabouts with up to four ways and turn
angles which makes the turns obvious, e.g. as in:

```
    *
    *
* *   * *
    *
    *
```

but not

```
     *
    *
* *   *
    * *
     * *
```

For Roundabout Intersections we issue instructions such as
"turn <direction>" instead of "take the <nth> exit".

At the moment we have a limit on the radius for these Roundabout
Intersections of 5 meters. Which fails to classify a wide range of
Roundabout Intersections in the US (with the US-wide streets).

This changeset removes the Roundabout Intersection radius limit:

- if the roundabout is larger than a threshold and is named we classify
  it as a rotary

- if the roundabout matches our criteria for Roundabout Intersections
  we classify it as a Roundabout Intersection

- else fallback to plain old Roundabout

There is a second issue with determining a roundabout's radius.
But that's for another pull request (tracking in #2716).

References:
- https://github.com/Project-OSRM/osrm-backend/issues/2716
2016-08-18 10:50:32 +02:00
..
contractor Fix platform-independent data in data files 2016-06-20 22:45:40 +02:00
engine Static checks for guidance array sizes. 2016-08-12 18:52:54 +03:00
extractor Be more aggresive classifying Roundabout Intersections. 2016-08-18 10:50:32 +02:00
osrm Format with clang-format 3.8 2016-05-27 21:05:04 +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 Warn on unused return values in guidance code, resolves #2686. 2016-08-03 12:26:07 +02:00