We’re using GraphHopper to power Ithaca Transit, a local transit navigation app. One of our users had an issue where they wanted to go from a bus stop to another location, and nearly all of the routes suggest to walk across a busy street to another bus stop, even though a bus is about to come to the bus stop they are at.
I tried digging into what could be causing this bug. It might be a bug with switching from inbound to outbound. Other mapping apps that are mentioned below have some trouble with this specific case too.
Google Maps and Moovit both default to this (incorrect) routing, but both include a “less walking” option that solves the problem. Transit (not us, another mapping app) defaults to the better routing; I did not look to see what setting may affect this there. In my view, “less walking” should be default for a bus app, and there should be an “allow more walking” option.
It might help debug this specific issue by download the app and interacting with our transit schedules. This problem concerns the TCAT bus service, specifically Route 11. Below are the instructions to reproduce it.
A user wants to go from [Stop] South Hill Business Park to [Stop] Ithaca Commons - Seneca St.. They were getting recommendations from multiple apps to walk across the street to [Stop] Ithaca College - Alumni Circle instead of just waiting at that location for the bus to come.
Google Maps also does returns results like these, but just some of the time. For Friday’s at 11:31 AM depart time, both Google and Ithaca Transit give the same result. They identify it’s quickest to walk across the street to catch the soonest bus in the area. However, at 11:42 AM departure time, Google uses the bus that comes to South Hill Business Park, while we still suggest walking across the street. The only route we serve that has a user catching a bus directly from South Hill Business Park is at 2:09 PM, after suggesting several routes that all involve not taking the bus right at the start location.
Please let me know if I can provide any other information about this issue, especially if this is a bug on our end or in GraphHopper.