Inspiration
We were hanging out at the Socam Apartments and wanted to get to our club: Rutgers Formula Racing, but we didn't know the bus route and path to take in order to get there. Our only option was to meticulously look at each bus stop and route on transloc to figure out the path and transfers we needed to take. I thought, "it would be so nice to have an app/website that you can put in two locations around Rutgers and have it calculate which bus stop to take, which stops to transfer, and which stop to get off at".
What it does
The project is the barebone program necessary to calculate the bus stops, buses, and transfers. It also calculates the estimated time of trip and mileage of the trip.
How we built it
We used javascript to build a graph with bus stop vertices and bus route edges and implemented Google Maps API and Google Distance Matrix API to compute locations of bus stops, mileage, and time it will take to reach the destination.
Challenges we ran into
- Making the edges be the bus routes connecting the bus stops (vertices).
- Implementing the location of the user and the location of the final destination.
Accomplishments that we're proud of
- Tying the bus routes with the associated edges of the graph.
- Implementing the Google Maps API to know the location of each source/destination.
- Implementing the Google Distance Matrix API to track the time of trip and distance of the trip.
What we learned
- Usage of Google APIs
- Usage of Google Cloud
- Graphs on Javascript
What's next for SVF Bus Stop Calculator
- Tracking user location.
- Locating the nearest bus stop to the user.
- Locating the nearest bus stop to the destination.
- Implementing a GUI.
- Streamlining the transfer system.
Log in or sign up for Devpost to join the conversation.