-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
I accidentally found a bug with car routing:

If start is nearest to an intersection where CAR has no permission to drive this intersection will be used as starting point because you can walk on it (and bikeWalkingRequirements is used to test permissions) and path finding will fail, because car permission on path is false. Probably connected with #1130.
The source of a problem is in TraversalConstrucor when initializing bike/walking requirements.
Everything starts in GetClosestVertex where pedestrian/bycicle corner is found. Which is intended but reqs.canBeTraversed returns True so this corner is used. Which it shouldn't because CAR permission is false.
Path can be traversed because reqs has CAR mode which in canBeTraversed returns false as it should but hasBikeWalkingRequirements is true and path can be walked/biked so canBeTraversed returns true and this corner is used.
End point which is also in the middle of no car area is found correctly.