Front end application request:

GET /api/v1/forecast?location=denver,co
Content-Type: application/json
Accept: application/json

• GET verb
• /api/v1 namespace
• /forcast uri
• location=CITY,STATE_CODE_ETC query param appended to uri
• Content-Type in header
• Accept in header

Response:

{
  "data": {
    "id": null,
    "type": "forecast",
    "attributes": {
      "current_weather": {
        "datetime": "2020-09-30 13:27:03 -0600",
        "temperature": 79.4,
        etc
      },
      "daily_weather": [
        {
          "date": "2020-10-01",
          "sunrise": "2020-10-01 06:10:43 -0600",
          etc
        },
        {...} etc
      ],
      "hourly_weather": [
        {
          "time": "14:00:00",
          "wind_speed": "4 mph",
          "wind_direction": "from NW",
          etc
        },
        {...} etc
      ]
    }
  }
}

The response data should contain exactly these elements and nothing more:

• a data attribute, under which all other attributes are present:
  • id, always set to null
  • type, always set to “forecast”
  • attributes, an object containing weather information:
    • current_weather, holds current weather data:
      • datetime, in a human-readable format such as “2020-09-30 13:27:03 -0600”
      • sunrise, in a human-readable format such as “2020-09-30 06:27:03 -0600”
      • sunset, in a human-readable format such as “2020-09-30 18:27:03 -0600”
      • temperature, floating point number indicating the current temperature in Fahrenheit
      • feels_like, floating point number indicating a temperature in Fahrenheit
      • humidity, numeric (int or float), as given by OpenWeather
      • uvi, numeric (int or float), as given by OpenWeather
      • visibility, numeric (int or float), as given by OpenWeather
      • conditions, the first ‘description’ field from the weather data as given by OpenWeather
      • icon, string, as given by OpenWeather
    • daily_weather, array of the next 5 days of daily weather data:
      • date, in a human-readable format such as “2020-09-30”
      • sunrise, in a human-readable format such as “2020-09-30 06:27:03 -0600”
      • sunset, in a human-readable format such as “2020-09-30 18:27:03 -0600”
      • max_temp, floating point number indicating the maximum expected temperature in Fahrenheit
      • min_temp, floating point number indicating the minimum expected temperature in Fahrenheit
      • conditions, the first ‘description’ field from the weather data as given by OpenWeather
      • icon, string, as given by OpenWeather
    • hourly_weather, array of the next 8 hours of hourly weather data:
      • time, in a human-readable format such as “14:00:00”
      • temperature, floating point number indicating the current temperature in Fahrenheit
      • wind_speed, string, in miles per hour
      • wind_direction, string, check wikipedia for how to convert this numeric value
      • conditions, the first ‘description’ field from the weather data as given by OpenWeather
      • icon, string, as given by OpenWeather

Requirements:

• Endpoint needs to use the city and state from the GET request’s query parameter and send it to MapQuest’s Geocoding API to retrieve the latitude and longitude for the city. Use of the MapQuest’s Geocoding API is a hard requirement.
• Retrieve forecast data from the OpenWeather One Call API using the latitude and longitude from MapQuest.
• Testing should look for more than just the presence of attribute fields in the response. Testing should also determine which fields should NOT be present. (don’t send unnecessary data)

Consume the OpenWeather One Call endpoint

Endpoint:
GET https://api.openweathermap.org/data/2.5/onecall
Request Headers:

Content-Type: application/json
Accept: application/json

Request params:
?lat=LATTITUDE&lon=LONGITUDE&exclude=minutely,alerts&units=imperial&appid=API_KEY

• Create Weather service object
• Add in VCR
• Happy Path Tested

Consume the MapQuest Geocoding API endpoint to turn a location into lat and long coordinates.

Endpoint:
POST http://www.mapquestapi.com/geocoding/v1/address
Request Headers:

Content-Type: application/json
Accept: application/json

Request body (JSON):

{
    "location": "LOCATION",
    "options": {
        "thumbMaps": false,
        "maxResults": 1,
        "intlMode": "AUTO"
    }
}

• Create Geocoding service object
• Add in VCR
• Happy Path Tested

Render the README in browser if a user tries to visit the root in browser.

What if the destination cannot be reached in 8 hours or by driving?

What if data is missing?

Currently, the user may register the same email multiple times if it is not exactly the same case as when they registered the first time.

• Downcase the email when registering a user to the DB
• Downcase the email when searching for a user in the DB
• Add testing to verify that the user cannot register multiple times with the same email in different cases

Currently, Unsplash returns images that may not necessarily have relevant subject matter. Improve the Unsplash API call to request landscape or related photos of the location.