Inspiration
From the Capital One Nessie API, we wanted to use the data to help find locations of overused and underused ATMs to optimize the decisions of ATM placements.
What it does
It shows current ATM locations as well as a heat map describing customer transaction frequency to give insights for future ATM locations.
How we built it
We used JSON API request to extract the data and inputted it into a Google Maps API to create heat maps and markers for better data visualization.
Challenges we ran into
Working with artifical API data made the insights on our map harder to find. Should the data for the customer transactions be real, we could find areas of high and low transaction frequency to gain more useful insights.
Accomplishments that we're proud of
We were able to create an easy-to-use and easy-to-understand data visualization using multiple languages and APIs.
What's next for Capital One ATM Location Optimizer
We hope to be able to use real customer data in order to gain valuable insights on ATM placements. Furthermore, we hope to develop algorithms to find exact optimized locations for the ATM placements.
Built With
- capital-one-nessie-api
- google-maps
- javascript
- python
Log in or sign up for Devpost to join the conversation.