...

Specifications

Selected API: OpenWeather

Current Roadmap Overview/Solar + Weather Intersect

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

• 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

First major task: what do we need from the API?

• What information is needed + how do we convert this into energy data when parsing API response?

• Solar -> power across energy cell, day, solarArray; adapt existing as needed!

• Weather -> solarCell for the efficiency decrease ; otherwise, precipitation and wind speed, wind direction info is kept but not used directly from energy

Second Q: How are we calling mid-race?

• Multiple calls + in the future (we're moving along the route, so can we make a call at some future location given our expected time of arrival at this location - so a couple hours from now)

• (strictly optional) How can we make the calls efficiently? Are we worried about blocking main thread?

• With all this information, how are we saving into some form -> Emma Wai (Deactivated) will create a chart of potential points, lat, lon, city names (hopefully you can create city IDs in a table if necessary) -> try API requests that will fill this table

Suggested table format:

• [time, lat, long, city ID/name], temperature, temperature correction, wind speed, wind direction, precipitation, energy from solar, energy once corrected

• solar: energy from solar, energy once corrected (optional -> energy per cell)

• weather: temperature, temperature correction, wind speed, wind direction, precipitation

Inputs: [table], solar API, weather API
Outputs: table