Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix forks exiting a ferry, resolves #3536 #3555

Merged
merged 1 commit into from
Jan 12, 2017
Merged

Conversation

MoKob
Copy link

@MoKob MoKob commented Jan 11, 2017

Issue

This PR introduces a problem introduced in our fork refactor (#3264) /cc @chaupow

screen shot 2017-01-11 at 11 22 13

The error occurs on this node where a ferry enters a fork.

I cannot pin-point the exact location in the code that is responsible for this change, but I think it might be related to road-classification comparisons.

I've fixed multiple locations in the code:

  • the fork detection does not trigger on invalid mode combinations anymore
  • in the fork handler, we don't assign a suppressed-turn if it should turn out one of the fork entries is obvious due to the road class (the fork handler is currently miss-used to give better instructions than turn straight for both turns).

Possible additional changes could be to incorporate the layer of the road, since we here see an intersection that technically is no intersection. I don't know how serious this problem is, though? Is this something worth ticketing? (Single Intersection with ferry, two roads, different layers of the ferry exiting).

Tasklist

  • add regression / cucumber cases (see docs/testing.md)
  • review
  • adjust for comments

Requirements / Relations

none

@MoKob MoKob added this to the 5.5.3 milestone Jan 11, 2017
@TheMarex TheMarex changed the title fix forks exiting a ferry, resolves https://github.com/Project-OSRM/osrm-backend/issues/3536 fix forks exiting a ferry, resolves #3536 Jan 11, 2017
@MoKob MoKob modified the milestones: 5.5.4, 5.5.3 Jan 12, 2017
@MoKob MoKob merged commit c1f833c into master Jan 12, 2017
@MoKob MoKob deleted the fix/ferry-suppression branch January 12, 2017 08:58
MoKob pushed a commit that referenced this pull request Jan 17, 2017
raymond0 added a commit to raymond0/osrm-backend that referenced this pull request Feb 24, 2017
Merge commit '54ab5373cf9b883f1d791182f218c33a2b5bd22b' into develop-ultimaterides-buildmain-integration

* commit '54ab5373cf9b883f1d791182f218c33a2b5bd22b': (23 commits)
  Fix tests - backported changes need old namespace.
  Update changelog and version for 5.5.4
  fix emitting invalid turn types, now surfacing due to changes in obvious detection
  Changelog Item for Project-OSRM#3561
  Added missing backward_speed for cycleways
  cherry-pick Project-OSRM#3555
  Fix possible division by zero by clamping latitude to 85.05°
  Adjusted number of `nodes` in `annotation`, resolves Project-OSRM#3515
  Update version and CHANGELOG for 5.5.3.
  Backport NumLanesToTheRight/NumLanesToTheLeft to support 6ea9f9f
  fix coordinate assertion for walking profile with steps
  Remove assertions that could be triggered by bad data. (Project-OSRM#3469)
  Make a hard reset of named barrier mutexes on signal
  Fix copying vector on std::sort comparator (Project-OSRM#3504)
  Consider number of lanes to cross, resolves Project-OSRM#3025.
  Make Travis buildit.
  Update changelog and version.
  Revert "Smarter search radius formula for map matching"
  Revert "Fix capture"
  Revert "Hardcode search radius parameters"
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants