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
As title. I found that some returned results in detailed_itineraries() rather do a long boomerang transfer than walking across the station. See an example:
The left part of the trip shouldn't exist.
Zoom in:
The brown lines are OSM streets.
The user should alight at the blue stations and walk to the destination, but because the links are deemed impassable by pedestrians.
Not relevant but here is the result from Googlemap
Guess this is a data issue? But feels like the snapping rules are also one of the factors that caused this. Feel like large stations are more vulnerable to these kinds of errors.
The text was updated successfully, but these errors were encountered:
Hi @luyuliu . Thanks for reporting this. This seems like an important issue upstream in R5, specifically in the McRAPTOR routing algorithm used here. There is nothing we can do from the r5r side, so I would strongly suggest opening this issue in the R5 repo.
As title. I found that some returned results in
detailed_itineraries()
rather do a long boomerang transfer than walking across the station. See an example:The left part of the trip shouldn't exist.
Zoom in:
The brown lines are OSM streets.
The user should alight at the blue stations and walk to the destination, but because the links are deemed impassable by pedestrians.
Not relevant but here is the result from Googlemap
Guess this is a data issue? But feels like the snapping rules are also one of the factors that caused this. Feel like large stations are more vulnerable to these kinds of errors.
The text was updated successfully, but these errors were encountered: