This should be extended by a global configuration option to hide all arrival times.

@barbeau I’ve got the basics of this working, any preferences towards stop vs global config (or both)?

I’m not really sure global is the way to go since a lot of buses tend to depart as they arrive at most stops and would get filtered out if “hide arrivals” were selected.

@sjgllghr Thanks for working on this! I agree that in my experience stop-specific filters would be best. I was thinking that we'd handle this similarly to "Filter routes" option in the overflow menu when looking at a stop, something like "Filter arrival/departures", with a dialog "Show" with single-select radio button options:

• Both
• Arrivals only
• Departures only

...with "Both" being the default.

@alexforencich Are there certain scenarios where you were thinking that a global configuration option to hide all arrivals would be useful? I see this as problematic as for most stops only arrivals are shown, where as arrivals are what you want to filter out at specific stops like in the original post. So setting a global option of "Hide arrivals" would hide them at many stops where you need them. And, it's not always straightforward to figure out which stops only have arrivals for specific route directions, as IDs and headsigns can change at a stop.

The problem is there is no way to differentiate between "arrival" and "arrival with immediate departure" right now. At a bus terminal, "arrival" is ambiguous because it might leave right away, or it might not leave until the next departure time which could be 30 min later. Or it could be going out of service. Or it could be the last stop for that bus and therefore doesn't pick up anybody. I don't care about what time the bus arrives, I only care about the time the bus will be leaving. It is possible that there is no way to solve this without some data plane reworking, though, which may not be possible.