fix forks exiting a ferry, resolves #3536 #3555
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
This PR introduces a problem introduced in our fork refactor (#3264) /cc @chaupow
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:
fork
entries is obvious due to the road class (the fork handler is currently miss-used to give better instructions thanturn 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
Requirements / Relations
none