You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use RoutingCostTravelTime, the route.leftRelation() and route.rightRelation() return None for the lane change lanelet, even though the next lanelet is part of the shortest path and graph.left() and graph.right() correctly return it. This problem does not occur with RoutingCostDistance.
Thanks for reporting this and for the script to reproduce the bug! I'll look into it when I have the time.
What I already found is that it is not directly related to RoutingCostTravelTime, it is more a bug that is somehow related to the routing cost index being nonzero. E.g. if you instanciate the routing graph like this, you will find that it is now RoutingCostDistance at index 1 that doesn't work:
When I use RoutingCostTravelTime, the route.leftRelation() and route.rightRelation() return None for the lane change lanelet, even though the next lanelet is part of the shortest path and graph.left() and graph.right() correctly return it. This problem does not occur with RoutingCostDistance.
Test code:
Map file:
tartu_demo.zip
The text was updated successfully, but these errors were encountered: