Inspiration

In typical weather websites, the weather is displayed chronologically, usually by hour/day/week. We noticed there is typically no filter to search for when a certain weather phenomenon is going to occur; the user must search for it manually. This causes individuals to have to browse through weather forecasts for an excess amount of time to find the weather they're searching for. Our inspiration for this project stems from the desire for a "reverse weather website" that could be much more time-efficient for tasks like event planning and much more.

What it does

WeatherFinder allows the user to choose from four weather types--rain, clouds, clear, and snow-- and displays the dates when the chosen weather will occur in the next eight days.

How we built it

First, we started by designing a website with HTML that would serve as the visuals for the WeatherFinder program. Next, we worked with JavaScript to implement the weather API and have the website perform the correct functions.

Challenges we ran into

Firstly, we ran into the issue of utilizing the weather API. We used the Open Weather Map API, and neither of us were familiar with using that type of API. Specifically, targeting the weather data produced by the API became an issue. Throughout our time coding, we had to learn how to implement it, since it was such a vital aspect of the project. Eventually, we were able to learn and succeed.

Secondly, time constraints were a challenge. We could not implement every single feature we wanted to include and had to sacrifice several ideas to finish on time.

Accomplishments that we're proud of

We were proud of being able to successfully incorporate the weather API into our project, as well as being able to filter through the weather and narrow down the dates a certain type of weather would occur.

What we learned

We furthered our knowledge on how to work with APIs, how to collaborate as a team, and exploring features of JavaScript we were otherwise unaware of.

What's next for WeatherFinder

In the future, we would like to implement some of the features we had to sacrifice for the sake of time, such as a feature that filters based on temperature, and a more polished website. Additionally, we would like to be able to access data from wherever a user is located, instead of solely from Rochester.

Share this project:

Updates