Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Seattle Hackathon (March 20-22, 2015) - Feature Ideas #353
There's a transit hackathon coming up next month in Seattle, and I thought it'd be great to put together a list of cool features participants could build on top of OBA as part of it. Here's more info on the hackathon itself: http://hackthecommute.seattle.gov/2015/01/13/hackthecommute/
No dependencies that I can think of:
Requires data loading changes: (may be obviated by #311, but tbd)
Depends on having a functioning OTP installation:
From Reddit and Seattle Transit Blog
If you have additional suggestions, please add them to this list or to the comments below.
Ideas for Android:
All Android development should be based on the current OBA
There are many other issues marked with "Enhancement" tags, but the above is the top list of items I think match best with a hack-a-thon.
changed the title from
Hackathon Feature Ideas
Seattle Hackathon (March 20-22, 2015) Feature Ideas
Feb 9, 2015
referenced this issue
Feb 23, 2015
I'm reading through ideas on reddit and Seattle Transit Blog - here they are for others to consider:
I'm currently fascinated by crowdsourcing of information so I pitched an idea around crowdsourcing transit data and a number of other individuals jumped onboard. Think Waze for transit riders. Initially we focused it on tracking when buses are full with the option to later expand it to include ghost buses, accidents, breakdowns, reroutes, alerts, etc. Essentially the idea is the try and collect information the agencies are not yet providing, on events that may result in a passenger not being able to get on their bus. We made some progress but obviously a lot of work would be required to actually roll this into OBA. Specifically this would require backend changes or another backend and as you know getting Sound Transit to update their backend software is unlikely in the near future. It likely would be easier to setup another backend for this feature (at least initially - similar to StopInfo) and it sounds like there may be some Microsoft resources to help support that. You can see our work at https://github.com/OneBusAwaze/OneBusAwaze. Would love to hear your thoughts on getting this rolled in to OBA. We didn't place in the top 5 but had there been a crowd favorite seems we would have had a good chance - many people voiced their support for such a feature.
Worth noting many other projects tried to utilize data from OBA in one way or another. In particular one that looked very closely related to OBA was revamping the digital signs that show when the next bus is coming. http://hackthecommute.seattle.gov/2015/03/25/hack-the-commute-recap has a list of all the projects and repos.
Candace here, from Hack the Commute – would love to help keep this moving
On Sat, Apr 4, 2015 at 1:54 AM, Ben Bodenmiller email@example.com
Cool! Yeah, crowd-sourced elements would be great in OBA. For reference as this further evolves, you might want to check out Moovit and Tiramisu Transit - those are the two existing transit apps that I'm aware of that have major crowd-sourcing components.
I'd suggest posting info about the project to the OBA developers group (https://groups.google.com/forum/#!forum/onebusaway-developers) so its more visible in the context of the community. I agree that setting it up so the backend is separate from the core onebusaway-app-modules is good to get started.