What is BloomBus?
BloomBus is an initiative to build a system for tracking and displaying the locations of shuttle buses owned and run by Bloomsburg University (and the C.G.A.) across the several loops that they run.
Last updated
BloomBus is an initiative to build a system for tracking and displaying the locations of shuttle buses owned and run by Bloomsburg University (and the C.G.A.) across the several loops that they run.
Last updated
BloomBus is comprised of 3 main software components:
BloomBus-Tracker — An Android app to be installed as on the mobile devices assigned to each shuttle driver, which when open will continuously publish location updates for a shuttle on the selected route to the database.
BloomBus-Client — The user-facing web app that allows students and other people on campus to select between shuttle loops and available shuttles, and see their locations on a map.
BloomBus-Server — A Node.js server, which acts as a monitor for the real-time events that occur on the database. For example, when a shuttle's position is updated, the server will see if any other shuttles have not been updated within a certain timeout, and if they haven't, their record will be removed from the database.
The database is currently the Firebase Realtime Database, which uses a pub-sub model for writing and listening to live changes in shuttle positions.
BloomBus-Server, as well as a few complementary services are run on an on-campus virtual machine.
TileServerGL - Serves the vector tiles for Client's basemap
Traefik - A reverse proxy that directs incoming traffic to the virtual machine to the individual services running on it
OpenRouteService - For getting calculations of estimated walking time between 2 points, for example
BloomBus began as a student project in 2015 through the Bloomsburg University ACM student chapter with a student, Dan Pany, who had the idea for the hardware that the tracking system would be based upon. He envisioned connecting an Adafruit GPS module to an Arduino microcontroller, in addition to an XBee radio transmitter, and using the 3 in tandem to receive GPS data, parse GPS data, and transmit GPS data (respectively). This system would also involve an XBee radio receiver connected over a USB connector to a server that would receive the GPS data, then upload it in a particular format onto a real-time database (Google's Firebase).
Another student, Rio Weber, began working with Pany on the BloomBus project primarily acting as the applications developer to provide the real-time database and user-facing application that displays the shuttles' coordinates. The 2 students conducted an independent study within the Digital Forensics program to work on a functioning prototype for this system. Their work is thoroughly documented in the document found here.
Unfortunately, the advertised range of 2 miles for the XBee radios was far greater than the experimental results found as Pany and Weber worked on conducting tests of the system. The results of these test can be found on page 13 of their aforementioned report.
In the 2018 Spring semester, another student, Nelson Maher, who had previous formal training with the PA National Guard in radio telecommunications and networking, had significant interest in the project, and proposed replacing the more expensive and radio-based system with a wifi based system utilizing ESP8266 chips — thumb-drive sized boards that have an onboard wifi chip and open source firmware that allows for the use of a framework called MicroPython. MicroPython allows for a subset of Python to be executed on the board's internal memory, and Maher quickly created a script that received in the same GPS data from the Adafruit module as before, parsed it, and uploaded it to Firebase. Thanks to the modularity of Weber's user-facing application, it continued to function exactly as previously expected. However, this system is intended to backpack off of the university's wireless network infrastructure, which is certainly spotty, especially along a route such as the campus loop where there is not a strong need for wireless coverage. This limitation also restricts the scope of the project's coverage to only the Campus Loop shuttle buses.
John Gibson, began working on this project in the 2018 Fall semester as an independent study under the advisement of Dr. Robert Montante, with the goal of having a more complete prototype of the system that could be proposed to the C.G.A. for official adoption.
His plan for having a more simplified and dependable system for this project to stand on would involve replacing the previous 2 proposed tracking hardware systems with instead using mobile phones assigned to each shuttle bus driver. The reasons for this proposal include:
A mobile device can easily be plugged in to the shuttle bus and charged via the bus' 12V socket
It provides an excellent GPS built into the phone
Is capable of maintaining a significantly more dependable 4G connection with mobile networks
Can provide an intuitive interface for the bus drivers can interact
As a result, the project was architected into three primary software components as described above.
