Open karenzshea opened 6 years ago
@karenzshea @oxidase I believe this edge is not marked correctly - it should not be marked segregated. With the logic in place from #5040 it should not negatively impact directions for the 5.17 release. @dnesbitt61 was reviewing Valhalla classification. We should be able to make sure segregated edge does not intersect with roundabout
Valhalla does not classify it as an internal intersection edge (not segregated) due to the outbound turn degree being classed as "nearly straight" - turn degree = 347. However, I would also agree that any edge that connects to a roundabout (either entering or exiting) should not be marked as segregated.
This issue seems to be stale. It will be closed in 30 days if no further activity occurs.
While debugging https://github.com/Project-OSRM/osrm-backend/issues/5039 I noticed that in a request like
when stepping through the steps vector in post-processing, the segment that enters the roundabout is classified as
is_segregated
@oxidase suggested that in segregated intersection classification a check that the segments are part of a rotary or roundabout could avoid misclassification here. The segment in this example above ^ is not technically part of the roundabout, but the following steps after it have roundabout instructions.
Questions
cc @dgearhart @kdiluca