KIEDY BUS open-source passenger information

KIEDYBUS is a local deployment of OneBusAway for polish market done by goEuropa

KIEDY BUS what we started with 1) No timetables - created GTFS timetables 2) No GPS data - created service to obtain XML with lat/lon/timestamp 3) No link between trip/block id and vehicle_id - created bus dispatcher webapp to link that data

KIEDY BUS how it works 1) Data from GPS and dispatcher systems goes to receiver & HornetQ queue system 2) Data is fed to Transitime along with GTFS 3) OBA is using GTFS-RT produced by Transitime 4)Android app, iPhone app and Webapp use OBA API

KIEDY BUS what we’re using 1) OneBusAway Transit Data Bundle Federation Webapp [no change to code] 2) OneBusAway Api Webapp [no change to code] 3) OneBusAway Webapp [no change to code] 4) OBA Android [includes search by stop, translation, slight mods to menu] 5) OBA iOS [ includes translation, slight mods to menu]

KIEDY BUS work on webapp 1) Started with modified version of InstaBus

2) Working on a new webapp in Java 3) Demo of old and new webapp

KIEDY BUS our planned work 1) Searching by stop in Android app user types in stop name (i.e. station) request to kiedybus api (i.e. stop_api?name=station) listing all stops for agency /stop_ids_for_agency… request to /stops w/ with matching stop id, getting name of stop matching stop names are displayed to user 2) Access to schedules in Android app request to stops_for_route request for chosen stop to schedule_for_stop parsing and displaying the response

KIEDY BUS our planned work ●

Standard procedure: fork of onebusaway-application-modules and android app adding search by stop and schedules view to api adapting android app to use extended api pull request back to OBA

KIEDY BUS additional plans ●

Buses equipped with LCD screens will display a sidebar with:

●

Router number + trip headsign

●

Upcoming stops

●

We already do it in other city (not using OBA)

KIEDY BUS thanks ! goEuropa Polska Wojciech Kulesza Tel. +48 609 689 230 [email protected]