Inspiration
We saw that Inrix’s fuel station API could be used to retrieve the price of fuel at each gas station. We originally thought to display the fuel prices of each station on a map for users, giving them the freedom to choose which station would be most cost-effective. Further, we expanded this idea by displaying different options to users and computing the monetary and environmental costs of going to each fuel station. This would allow the user to compare the options of going to each station in a convenient and efficient manner depending on their priorities.
What it does
FuelFocus is an innovative solution blending Google Maps and Inrix APIs with our unique algorithm to address fuel expenses and environmental concerns. It offers users three distinct routes to their destination, each including a gas station. What sets FuelFocus apart is its ability to show both the cost and carbon emissions for each route, empowering users to make informed decisions based on their financial and environmental priorities. This technology not only helps in saving money but also contributes to reducing the carbon footprint, one journey at a time.
How we built it
FuelFocus employs a comprehensive approach to optimize route planning. Initially, it uses the Fuel Station API to gather data on the locations and prices of nearby gas stations. To determine if these stations fall within a specified radius around the planned route, the system applies midpoint and Pythagorean theorem calculations. Once identified, the Routing API is used to map out routes to all the gas stations within this radius. The program then calculates the fuel cost for each of these routes, selecting and returning the three most cost-efficient options. Finally, these routes are displayed to the user through the Google Maps API, providing a clear and convenient visualization of the options.
Challenges we ran into
Challenge 1: Because our radius was in a large urban area, our fuel station API would need to be called for every gas station which would result in an overwhelming amount of API calls which would make for a time-consuming process for our users. If we had access to a database of the routes, we would be able to submit a single SQL query for a more time-efficient operation
Challenge 2: We had originally built our frontend application using React.js but weren’t able to integrate the Google Maps API. We were not able to access the Maps API due to a CORS error. Once we realized this, we opted for a different route, converting our React code to HTML and CSS. After this, we were able to properly implement the Google Maps API. In retrospect, we had realized there had been a more practical solution to resolving the CORS error without changing the language of our frontend, although we learned several lessons from this particular challenge.
Accomplishments that we're proud of
Accomplishment 1: Although this started as a very simple idea of displaying the prices of different gas stations on a digital map, we expanded the capabilities of our project by using our prior knowledge of Dijkstra's Algorithm, calculus, and other computer science algorithms to culminate our program’s logic.
Accomplishment 2: Using the three walls of whiteboards in our classroom, we mapped and visualized our program from start to finish to allow ourselves to convey our ideas, ask questions, and provide feedback to each other effectively.
What we learned
In this project, we successfully connected our frontend platform with the backend architecture. We developed skills in executing API calls without exceeding the rate limit. Our work involved the practical implementation of algorithms into our backend processes. This experience helped turn theoretical concepts learned in the classroom into tangible, real-world solutions
What's next for FuelFocus
Building on our carbon emissions tracking, we plan to develop a comprehensive dashboard that leverages these analytics to capture data about fuel consumption patterns, fuel expenses, and carbon emissions generated from each trip. This dashboard will not only display data but also offer insights into local driving behaviors, providing a clearer understanding of their environmental impacts in different areas. This project has something to offer to every driver in one way or another, further pushing for a greater demand for more companies to use Inrix’s traffic analytics. We have come a long way, but we collectively understand that there is always room for improvement. Ultimately, everything that's now considered great was once merely good. With the help of much-needed pioneers pushing for a greener, safer, and smarter future, we cannot be complacent.
Log in or sign up for Devpost to join the conversation.