Developed to power Conveyal's web-based interface for scenario planning and land-use/transport accessibility analysis, R5 is our routing engine for multimodal (transit/bike/walk/car) networks with a particular focus on public transit
As title. I found that some returned results in r5r's 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.
As title. I found that some returned results in r5r's
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.