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
For instance, right now to go from West Newton to Longwood, it recommends going from the Worcester Line to the Orange Line then the Green Line, when you could make the same trip by walking from Lansdowne to Kenmore with one transfer.
There are a good handful of stations within walking distance of each other (Copley/Back Bay being the classic example) for which a walking transfer would save a lot of time, especially in a world where there's no fare penalty for leaving the system to do so. To add this to the Explorer, we'd probably want to gather (from Google Maps or similar) a set of walking distances between reasonably close stations (<=0.25mi?) and seed neighbor stations into the initial search states.
We should be mindful of wheelchair++ users when launching this feature — taking into account hostile street design, elevator access, etc. when including/excluding station pairs and finalizing walk times.
The text was updated successfully, but these errors were encountered:
From Ethan on slack:
There are a good handful of stations within walking distance of each other (Copley/Back Bay being the classic example) for which a walking transfer would save a lot of time, especially in a world where there's no fare penalty for leaving the system to do so. To add this to the Explorer, we'd probably want to gather (from Google Maps or similar) a set of walking distances between reasonably close stations (<=0.25mi?) and seed neighbor stations into the initial search states.
We should be mindful of wheelchair++ users when launching this feature — taking into account hostile street design, elevator access, etc. when including/excluding station pairs and finalizing walk times.
The text was updated successfully, but these errors were encountered: