Closed mattwigway closed 8 years ago
It may be that we're not properly combining the non-transit search with the transit search.
One bug: we were always calculating travel time based on walk distance in bike-to-transit mode, which obviously is nonsensical.
This should be fixed. I'll run another multipoint job to confirm.
Confirmed fixed.
Increasing the bike speed on the request can cause decreases in accessibility, clearly a bug:
Additionally, switching from walk to transit to bike to transit can cause decreases in accessibility. It may be that we're using a slower walk speed when walking a bike, or because we're taking into account turn costs even in the walk search when doing the bike search.