A way to get bus routes via both OCCT and Broome county buses in binghamton (or both)

Find a file

Pagwin ab4e669f55 seemingly finished state		2024-02-18 08:27:47 -05:00
BBB_frontend	seemingly finished state	2024-02-18 08:27:47 -05:00
migration	giving up on db schema in favor of prototyping	2024-02-17 16:21:59 -05:00
src	seemingly finished state	2024-02-18 08:27:47 -05:00
.dockerignore	frontend is coming toegether just need to put it all toegether	2024-02-18 01:09:12 -05:00
.gitignore	finished the basic api as far as building is concerned but might be buggy	2024-02-17 22:26:33 -05:00
Cargo.lock	swapped tokio for async std and realized I never implemented fetching stops	2024-02-18 04:15:42 -05:00
Cargo.toml	swapped tokio for async std and realized I never implemented fetching stops	2024-02-18 04:15:42 -05:00
docker-compose.yml	stalled on docker nginx curfuffle	2024-02-18 03:02:19 -05:00
Dockerfile	stalled on docker nginx curfuffle	2024-02-18 03:02:19 -05:00
README.md	seemingly finished state	2024-02-18 08:27:47 -05:00

BinghamtonBetterBus

Currently just an api to get the best bus route from point a to point b, currently building frontend

to run you need a file called GOOGLE_API_KEY in the dir the app is run in which has access to the routes api

TODO:

test with BC buses
Make buttons change color to indicate toggle
Prevent buses from going backwards
make time estimate accurate (beyond hack divide by 3)
Change api to give a not shitty poly line for Broome county buses
Trim poly lines down to the bit between bus stops
Fix the UI so console and alert aren't needed
refactor to work within docker and setup within docker-compose
make route checking more advanced with better walking heuristic
make route checking more advanced by allowing multiple factors with multiple weights including
- walking time (don't remove it)
- bus travel time
- layover time
- ultimate arrival time
use a DB via SeaORM to avoid spaming APIs
use info in db to try and predict bus schedules in future