The AccuWeather source loads weather data from AccuWeather into the Lake. Connect it with your API key, list the places you care about, and choose for each place whether it reads current conditions or a daily forecast. For the Lake's other weather source, see Connect Visual Crossing.
Creating a connection needs Add/Modify Lake Objects. See Who can do what in the Lake.
A collapsible Documentation panel sits beside the form; it shows the reference material published for this source type.
API Key takes your AccuWeather key and is required.
Locations lists the places this connection reads. Click Add to open a row with these fields:
| Field | What it sets |
|---|---|
| Name | Your label for the row, at least 3 characters. It must be unique among the rows, and it is kept in the loaded data. |
| Value | The place to look up, in the form the chosen type expects. |
| Location Type | How the value is read: City, City Autocomplete, Latitude/Longitude, IP Address or Postal Code (US/Canada). A new row starts as City. |
| API Type | Current Conditions (the default) or Forecast. |
| Forecast Period | Shown when API Type is Forecast: 1 Day (the default), 5 Days, 10 Days or 15 Days. |
Confirm the row with the save icon, or close it with the X to discard it. A saved row shows its name and its settings, with icons to edit or remove it. Until there is a row, the list reads "No locations added yet.".
A row is checked when you save it: its name cannot be empty ("Location name cannot be empty") and must be unique ("Location name must be unique"), and its value cannot be empty ("Location value cannot be empty").
When a table loads, each value is looked up through AccuWeather's location service for the chosen type, and the first match is used.
The connection offers one table, Forecast. Every location you list contributes rows to it: a row keeps the location Name and its Value, the Location Type, the API Type and the Forecast Period, with the service's full response as JSON in jsonValue. A load reads all the locations on the connection.
Tables from this connection can use only the Full Snapshot sync type; the other sync types are greyed out for them. See Choose a sync type.
Name, Code, API Key and at least one location. The form names what is missing, for example "API Key is required" or "Locations cannot be empty".
The API Type on the row decides, so you can mix the two across locations. Current Conditions reads the place's current conditions. Forecast reads a daily forecast for the Forecast Period you choose: 1 Day (the default), 5 Days, 10 Days or 15 Days. Forecast data is read in metric units.
City, City Autocomplete, Latitude/Longitude, IP Address and Postal Code (US/Canada). A new row starts as City.
Name is your own label for the row; it must be unique, it is at least 3 characters long, and it is kept in the loaded data. Value is what AccuWeather searches for with the chosen type.
No. Each row needs its own name. The form stops you with "Location name must be unique"; rename the row, or remove the other one.
No. When you open the connection for editing, API Key is filled in from the saved connection, hidden as dots. Replace it only when the key has changed.
Yes. Duplicate opens a copy with Name and Code empty and the API Key and Locations carried over. Give the copy its own name and code, then click Duplicate.
The connection is created: a notification reads Connection added successfully, the connection opens in its own tab, and its source panel opens beside the tree, ready for the import. See Import tables.
Open the connection from the Lake tree, then add, edit or remove rows under Locations and click Save. The form opens with the saved key and the location rows already in place.
One table, Forecast. Each row keeps the location Name and Value, the Location Type, the API Type and the Forecast Period, and the service's response as JSON in jsonValue. Every load reads all the locations on the connection.