Project Summary

The weather model will provide the team with a variety of weather information on the route throughout the day. Information such as temperature, predicted precipitation, and wind, is used by other models to help with their decisions. It also provides an idea to the team on if weather could have a negative impact on the racing ahead or if the team will have to trailer through a storm.

Goals

• Obtain weather data along the race route on a day to day basis

• Have predicted weather data for up to two to three days in advance

• Be alerted to bad weather in advance

...

• Meteorological weather maps on the visualization dashboard (think weather channel maps showing precipitation)

• Quantify the impact of winds

Inputs

The weather model will take in a set of longitude and latitude values that will refer to locations along the race route for the day.

Outputs

Spreadsheet with the following:

• Latitude/longitude location

• Time

• Temperature → Forwarded to Solar Model

• Wind

• City

• Precipitation

Specifications

Selected API: OpenWeather

Note: OpenWeather can only query one location and has a limited number of calls per day. ETS currently uses a cloud server that will ping OpenWeather along their route as they drive and retrieves the data from the server. Our implementation will be more direct, but we cannot predict the upcoming weather very accurately (fallback will be the full route weather data pulled beforehand)

Current Roadmap Overview/Solar + Weather Intersect

• Will need a directory for solar, weather API calls/parsing

  • Solar API: Solcast [STRAT-95 DOC]

• Good point of reference is routemodel => common.py, speedlimits.py, routes.py, elevations.py
  -- > how they built a query, parse data from query, stored API key/handled error

...