Add option to include arrivals more than 30 minutes out

[onebusaway]

Add option to include arrivals more than 30 minutes out

[paulcwatts]

This could definitely be integrated as well into a new trip details / extended arrivals activity. There's a lot to think about if I want to add all of these features.

[barbeau]

There are also a number of ideas on how to implement this from users on an OBA IdeaScale idea page as well.

This is important in Tampa since some routes have half-hour or even hour headways, and on these routes/stops the app has limited utility when only the next 35 minutes is shown to the user. Half-hour headways arrivals are removed from the user's view as well where there is more than a 5 minute delay.

Ideally we should try and coordinate with OBA iPhone too so we have some consistency (or borrow ideas ;) ) for how information is shown to the user.

[barbeau]

OBA iPhone devs just implemented a feature for this, I'll post a screenshot when the build goes out for testing.

[barbeau]

The current iPhone solution is to add a Load more arrivals button at the bottom of the arrivals list:

When tapped, the app hits the API again, increasing the minutesAfter parameter by 30. If there are more arrivals they are tacked onto the bottom of the list, with the Load more arrivals button remaining at the bottom:

If tapped again, minutesAfter is increased by 30 minutes again.

@paulcwatts Would you be ok with a similar solution for Android? If so I'll try to implement soon.

[paulcwatts]

That's fine with me. Eventually it would be nice to just provide a link to the stop schedule as well.

[barbeau]

Agreed, stop schedule link would be good too, I'm assuming in the context menu that pops up when tapping on the arrival time (this is where "route schedule" appears)? I'll open a separate issue for this, since at a glance I believe this requires another field in the Regions API for a base URL for the OBA website (which doesn't necessarily have the same base URL as the API).

[barbeau]

Well, as an alternative to directing to the OBA stop schedule page, there is a stop_url in the GTFS spec, but neither HART in Tampa nor Sound Transit populate it (and I'm assuming this means they don't have web pages per stop). I don't think the stop_url field is in the OBA REST API response either. So pointing at the OBA stop schedule page is probably the path of least resistance, assuming an agency has an OBA website.

[paulcwatts]

Sorry I wasn't clear, my comment was we could build some screens into the Android app that would consume the OBA Discovery APIs.

[barbeau]

Ah, gotcha. I'll update the other issue.

[barbeau]

@paulcwatts As far as the general style of the "Load More Arrivals" button, are you ok with the below? Any suggestions?

[paulcwatts]

I'd just have the text flat against the list item and have the entire list item be actionable.

[barbeau]

OK, so exact same as iPhone as shown earlier?
On Oct 17, 2013 6:35 PM, "Paul Watts" [email protected] wrote:

I'd just have the text flat against the list item and have the entire list
item be actionable.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/26#issuecomment-26558901
.

[paulcwatts]

Yeah, like that +1