-
Our Logo
-
Latest Version
-
Example of database. You can see general progression from testing to needing help.
-
Snippet of our backend code for our application. We broke our code down into cases with the relevant information needed.
-
Output of our API that we built and used.
-
Figma Concept.
-
-
One of our teammates is a member of a service that SCU provides called SafeWalk. They dispatch walkers to walkees who don't feel safe walking to an area or back from an area to campus. One lament was that the service seems to be underutilized and in order to provide a bit of longevity, we wanted to automate the process as well as make it more efficient. The current system for SafeWalk makes it so that people have to call a dispatcher via a phone rather than a simpler application. Then they send a dispatcher from Benson to off campus. No only is there a lack of efficiency as phone calls are slow, but there is a logistical problem too. So we wanted to create an application that would help the end users better effectively use the service SCU provides as well as provide a possibility for data collection so that the service runs more efficiently over time.
For the tech break down, we run our application via a backend of PHP and MySQL to manage the database and information storage. We provide an API that we use ourself, but can also be exported out for other uses. This can be found in our /API folder on github.
We planned on using INRIX API to calculate projected human density with traffic data as it should be fair to assume that a there is a correlation between well trafficked areas and places of higher levels safety. We did this by calling INRIX's API for blocks and planned on combining it with other possible outlets. However, our base code for blocks never worked as intended because of problems listed in the following segment.
The idea behind this was to create generic points around the user so they can gauge population density as a possible factor in where they could stay to wait or whether they need help.
During this time, we ran into mainly front end development problems. For the most part, we were great with back end and had our APIs and backend requests already built within the first half of the time. However, we decided to use React.js. We were learning the thing from the ground up and approached many different problems that took time and some that we couldn't even solve. However definitely learned quite a bit about how to develop and approach frontend problems.
While we this was a bottleneck, we used what we have learned to make Figma prototypes so that continuing the project will be a lot easier.
What's next for SafeWalk.edu
We plan on implementing features that we have planned such as finishing the frontEnd code. We also plan on finishing INRIX and other API implementations because we were running into problems with our requests. If SafeWalk.edu collects enough data, it can be used to iterate itself to optimize the system of safewalk at SCU uses by clustering data like traffic history together to create central locations for efficiency.
Log in or sign up for Devpost to join the conversation.