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
Andrew Byrd edited this page Aug 20, 2014
·
1 revision
The issue is connectivity between OSM ways, or the "topology"
of the OSM data. Data that yields a good map for visual use is not
necessarily usable for routing. It's not sufficient for ways to overlap
or come near each other. They actually need to share a node for OTP to
pass from one way to the other. This allows us to distinguish between
bridges or flyovers and intersections.
Fortunately OSM is a user-editable dataset. You can just log in and
start fixing the pedestrian bridges. This is one of the most common
edits we need to do when deploying OTP for a new region.
The documentation on this wiki is outdated and should not be used
unless you are intentionally working with legacy versions of OpenTripPlanner. Please consult the current documentation at readthedocs