3 ms·
I've had this exact same issue a lot as well! I tend to walk way faster than google assumes I should. Maybe one suggestion I could think of, would be a risk sc
by graypegg 2y ago
I've had this exact same issue a lot as well! I tend to walk way faster than google assumes I should.
Maybe one suggestion I could think of, would be a risk score. Given a set of segments, which transfers are the most "risky"? (From those departures, arrivals and transfer estimates, how bad would the impact be going forward from missing a transfer?)
The main thing I get from Google Map's estimates is an indication that something has changed. If google gives me a route I wouldn't expect, it's normally because some trains/busses have been removed from the schedule today/running slow. Without forcing a route on you, it would be nice to have it hint at the fact that I'll be catching the last train that hour, thus making segments before it "riskier", scaled by how often they arrive + how long my transfer time is + how out of sync they are from the next segment's departures.
- twocentstudios 2y ago> Maybe one suggestion I could think of, would be a risk score. I like this idea a lot. If I were to do a full-featured routing app concept using an API to get route proposals, I think it'd be possible to supplement each proposal with a risk score the way you describe. > The main thing I get from Google Map's estimates is an indication that something has changed. Great point here.
- toast0 2y ago> Without forcing a route on you, it would be nice to have it hint at the fact that I'll be catching the last train that hour, I've seen this in google maps routing where it will say 'next bus/train in N minutes (or Day and time if this was the last one for the day)'