#BostonBusMap This app shows locations and predicts bus times in Boston and nearby cities, using GPS info from the MBTA. Please email [email protected] if you have any problem, and please report a crash if you see one! Twitter feed for bug updates: @bostonbusmap

#Basic usage

• choose a mode by clicking the button on the upper right corner. You can see all vehicles at once, vehicles for a single route, bus predictions for a single route, or only bus predictions on favorited stops
• choose a route by clicking the menu button and clicking "Routes". You can also type in the route in the search textbox
• click on a stop to show the next few buses that are driving by.
• click 'more info' to show more predictions for that stop
• click 'report problem' to report a problem with the predictions
• click the star in the popup (see screenshot) to mark a stop as a favorite
• choose a favorite stop by pressing the menu button and clicking "Favorite stops"
• center on your current location by clicking the menu button and choosing "My Location". The speed and accuracy of location information depends on your phone location settings. You can tweak those in Home -> Settings -> Location & Security
• draw the path along a route by clicking the menu button, going to Settings and selecting "Show route path"
• this app should work for all touchscreen devices that are Android 1.6 and up (which means pretty much all Android phones and tablets). Please let me know if something doesn't work.

#Development History The app started off with a few outdated decisions:

• I wanted it to perform well on the G1 so there were tight memory and speed constraints.
• It downloaded route data from NextBus into memory each time it was loaded. This quickly became unreasonable so the app was redesigned to ship all data with it (located in res/raw/databasegz). At first this was a compressed XML file because I wanted to import data using the same code as if I were downloading it over the web. Reading from XML and putting it in the database took a fair amount of time (although only once per app update) so this was changed to just ship a precalculated SQLite database with all route and stop data already in it. (Precalculation script is at tools/autogenerate.sh.)
• Various concurrency bugs led me to try to synchronize all relevant code points (badly), and later just make most things immutable.
• The database used to contain a SQLite blob with each route in a custom serialized format. Later I realized the space savings were small and the gains from being able to join data were huge.

#Build You'll need to git clone [email protected]:bostonbusmap/android-mapviewballoons.git. This project references that code to draw the mapview balloons.

You'll also need to download the MBTA's GTFS data, and unzip it into tools/gtfs.

Then, cd into the tools directory, then run autogenerate.sh to create and populate the database file, which gets copied to res/raw/databasegz. routeconfig.xml and routeLists come from data collected from nextbus.com for a particular transit agency. For the MBTA, see their developer website for how to get their subway and commuter rail info.

Otherwise this is a standard Android project. You might need to change the paths a little bit but you shouldn't need to install anything unexpected. Note that you may need a separate Google Maps API key to test with

#Branches

There are a few important git branches corresponding to different apps for different cities:

• master - where all code gets merged
• mbta - This is the same as master except with updated Hubway and MBTA-specific transit data.
• mta - This is master with a SIRI parser for New York's bus and Citibike feeds.
• la - This is master with MBTA-specific commuter rail and subway code removed, and with Los Angeles NextBus data added. This also changes the namespace and some of the graphics to fit the Los Angelbus app.
• toronto - Similar to la branch
• umich - This was branched off an early build of BostonBusMap. It focuses on the University of Michigan's bus system for Ann Arbor.