back

by josephcsible·1y ago·view on hn ↗
> My understanding is that it computes the time simply as (estimated_end_time - start_time), and it determines the estimated_end_time as whenever you would reach your destination, which accounts for train schedules and walking time.

It does do that. But it moves start_time into the future, and that's what makes it not count the time of waiting for the train.

1 comments
I see what you mean, Google Maps recommends you start at a given time to get to the train it expects you to catch, accounting for walking time. I've only ever seen the start_time be a couple minutes in the future during regular hours (due to the aforementioned frequency of trains) so it's been very negligible.