Bustracker: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
[[File:Bustracker Framed.jpeg|300px|thumb|right|Bustracker showing nearby stops and their upcoming buses!]] | [[File:Bustracker Framed.jpeg|300px|thumb|right|Bustracker showing nearby stops and their upcoming buses!]] | ||
| Line 13: | Line 11: | ||
Contributions welcome! The code is located on git (https://git.devhack.net/devhack/bustracker). | Contributions welcome! The code is located on git (https://git.devhack.net/devhack/bustracker). | ||
To request a missing stop or route to be added, make a pull request with the right modifications (bustracker/data.py) or ask its maintainers Cleeb and Maia. | |||
Latest revision as of 00:18, 20 December 2024
bustracker is a framed e-ink display that shows upcoming transit departures from surrounding bus stops. It is powered by an Raspberry Pi hidden behind the frame. Right now, it's in a frame and hung next to the bulletin board in the Hub.
Technical
Under the hood, bustracker is powered by the Puget Sound OneBusAway API (and uses OneBusAway stop IDs in the code). It then renders a black-and-white image using Python's PIL library and sends it to the e-ink screen via the Raspberry Pi's GPIO pins.
The Raspberry Pi connects to the wlan0 WiFi and should be reachable as bustracker2.core.devhack.net.
Contributions welcome! The code is located on git (https://git.devhack.net/devhack/bustracker).
To request a missing stop or route to be added, make a pull request with the right modifications (bustracker/data.py) or ask its maintainers Cleeb and Maia.