-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linker should not snap to streets in tunnels #1434
Comments
If only it were so easy. Stations are often in tunnels, and GTFS data doesn't tell us which OSM level the station is at. If we create a preference for snapping to surface streets, in places like http://www.openstreetmap.org/node/40532724#map=19/45.51062/-122.71650 the GTFS stop would be connected to the surface walking paths instead of the underground platforms. One solution here is to make the OSM data more clear by adding a way for the transit platform and connecting it to the proper street/sidewalk. OTP has a strong preference for connecting transit stops to ways tagged as transit platforms. |
At least we should decrease the tendency to snap to tunnels with (only) car access. In some places it is impossible to set starting/ending point within a pedestrian plaza, since OTP always snaps to parking access tunnels/garages underneath it, creating long detours to connect to the walkable network. In the above case, probably the best thing to do is to tag it correctly in OSM in order to get the preference as a platform. |
Also keep in mind that there's a difference between the code that links GTFS stops to the street network and the code that selects a location in the street network based on geographical coordinates. |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days |
Currently when starting a journey above a tunnel, the linker sometimes snap the starting position to it.
The text was updated successfully, but these errors were encountered: