# Darksky

Information note **Darksky is supported by the Singer community**   
This integration is powered by [Singer's](https://www.singer.io/) Darksky tap. For support, [visit the GitHub repo](https://github.com/singer-io/tap-darksky) or [join the Singer Slack](https://singer-slackin.herokuapp.com/).

## Darksky feature snapshot

A high-level look at Stitch's Darksky (v1) integration, including release status, useful links, and the features supported in Stitch.

| **STITCH** |  |  |  |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on January 3, 2020 | **Supported by**<br><br>the Info icon<br><br>Indicates if the integration is supported by Stitch or the Singer community. | [Singer Community](https://www.singer.io/) |
| **Stitch plan**<br><br>the Info icon<br><br>The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**<br><br>the Info icon<br><br>Indicates if the integration is available as a source in Stitch Connect. | the Success icon<br><br>This version of the integration is available via the API.<br><br><br>Available |
| **Singer GitHub repository** | [singer-io/tap-darksky](https://github.com/singer-io/tap-darksky) |  |  |
| **REPLICATION SETTINGS** |  |  |  |
| **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **Table-level reset**<br><br>the Info icon<br><br>Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Remove icon<br><br>Table-level resets are not supported for this integration. Resets are only supported at the integration level.<br><br><br>Unsupported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**<br><br>the Info icon<br><br>Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon<br><br>Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.<br><br><br>Unsupported |
| **DATA SELECTION** |  |  |  |
| **Table selection**<br><br>the Info icon<br><br>The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Remove icon<br><br>Table selection is not supported for this integration. All available table and fields will be automatically selected for replication.<br><br><br>Unsupported | **Column selection**<br><br>the Info icon<br><br>The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Remove icon<br><br>Column selection is not supported for this integration. All available columns in tables set to replicate will be selected.<br><br><br>Unsupported |
| **Select all**<br><br>the Info icon<br><br>Indicates if the integration supports selecting all available tables and columns. | the Remove icon<br><br>As this integration doesn't support table or column selection, all available tables and columns are automatically replicated.<br><br><br>Unsupported |  |  |
| **TRANSPARENCY** |  |  |  |
| **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**<br><br>the Info icon<br><br>Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**<br><br>the Info icon<br><br>Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |

## Connecting Darksky

### Step 1: Retrieve your Darksky secret key

1. Log into your Darksky API account [here](https://darksky.net/dev/).
2. On your account home page, your Secret Key is available at the top of the page. You will use this Secret Key to add your integration.

### Step 2: Add Darksky as a Stitch data source

1. [Sign into your Stitch account](https://app.stitchdata.com/).

2. On the Stitch Dashboard page, click the **Add Integration** button.

3. Click the **Darksky** icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch Darksky” would create a schema called `stitch_darksky` in the destination. **Note**: Schema names cannot be changed after you save the integration.

5. In the **Language** field, enter the language code. Ex: ‘en’ for English, ‘es’ for Spanish, and ‘fr’ for French. For a full list of available language codes, check the `Request Parameters` section of the [Darksky API documentation](https://darksky.net/dev/docs#forecast-request).

6. In the **Location List** field, enter the latitude and longitude of the the locations to be returned for weather forecast information. The locations must be semi-colon deliniated. Ex: `<latitude>,<longitude>` is an accepted value for a single location, and `<latitude>,<longitude>;<latitude>,<longitude>; ... etc` is accepted for multiple locations.

7. In the **Secret Key** field, paste your Darksky secret key that you retrieved in [Step 1](https://help.qlik.com/en-US/stitch/integrations/saas/darksky#secret-key).

8. In the **Units** field, enter the measurement system to be returned for weather forecast information. Ex: ‘us’ for Imperial Units, and ‘si’ for International System of Units. For a full list of available measurement systems, check the `Request Parameters` section of the [Dark Sky API documentation](https://darksky.net/dev/docs#forecast-request)

### Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Darksky integration. This means that data **equal to or newer than this date** will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Darksky’s default setting of **1 year**. For a detailed look at historical replication jobs, check out the [Syncing Historical SaaS Data](https://help.qlik.com/en-US/stitch/replication/syncing-historical-saas-data-resetting-replication-keys) guide.

### Step 4: Create a replication schedule

Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.

In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Darksky integrations support the following replication scheduling methods:

* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)

* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)

* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage.

### Initial and historical replication jobs

After you finish setting up Darksky, its **Sync Status** may show as **Pending** on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a **Pending** status indicates that Stitch is in the process of scheduling the initial replication job for the integration. **This may take some time to complete.**

Information note

**Initial replication jobs with Anchor Scheduling**

If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.

#### Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.

## Darksky table reference

Information note

**Schemas and versioning**

Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.

The schema and info displayed below is for **version 1** of this integration.

This is the latest version of the Darksky integration.

Information note

**Table and column names in your destination**

Depending on your destination, table and column names may not appear as they are outlined below.

For example: Object names are lowercased in Redshift (`CusTomERs` &gt; `customers`), while case is maintained in PostgreSQL destinations (`CusTomERs` &gt; `CusTomERs`). Refer to the [Loading Guide](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info.

### forecast

The `forecasts` table contains weather conditions for a particular date and location. The locations are determined by the locations entered into the **Locations** field in Stitch.

**Note**: The units data points are returned in is determined by the value entered into the **Units** field in Stitch. For example: If `us` is entered, data will be returned in Imperial units.

| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Keys ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | forecast\_date<br><br>latitude<br><br>longitude |
| **Replication Key ![](https://help.qlik.com/en-US/stitch/images/replication/replication-key-icon.svg)** | forecast\_date |
| **Useful links** | [Darksky documentation](https://darksky.net/dev/docs#overview "Opens in new tab: Darksky documentation")<br><br><br>[forecast schema on GitHub](https://github.com/singer-io/tap-darksky/blob/master/tap_darksky/schemas/forecast.json "Opens in new tab: forecast schema on GitHub")<br><br><br>[Darksky API method](https://darksky.net/dev/docs#time-machine-request "Opens in new tab: Darksky API method") |

forecast table schema

| **daily**<br><br><br>OBJECT<br><br>This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.<br><br>Click to expand daily<br><br><table> <tr> <td> <p> <strong>								apparent_temperature_high							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								apparent_temperature_high_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								apparent_temperature_low							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								apparent_temperature_low_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								apparent_temperature_max							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								apparent_temperature_max_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								apparent_temperature_min							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								apparent_temperature_min_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								cloud_cover							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								dew_point							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								humidity							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								icon							</strong> </p> <p>							STRING													</p> </td> </tr> <tr> <td> <p> <strong>								moon_phase							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								precip_accumululation							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								precip_intensity							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								precip_intensity_max							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								precip_intensity_max_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								precip_probability							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								precip_type							</strong> </p> <p>							STRING													</p> </td> </tr> <tr> <td> <p> <strong>								pressure							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								summary							</strong> </p> <p>							STRING													</p> </td> </tr> <tr> <td> <p> <strong>								sunrise_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								sunset_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								temperature_high							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								temperature_high_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								temperature_low							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								temperature_low_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								temperature_max							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								temperature_max_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								temperature_min							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								temperature_min_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								uv_index							</strong> </p> <p>							INTEGER													</p> </td> </tr> <tr> <td> <p> <strong>								uv_index_time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								visibility							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								wind_bearing							</strong> </p> <p>							INTEGER													</p> </td> </tr> <tr> <td> <p> <strong>								wind_speed							</strong> </p> <p>							NUMBER													</p> </td> </tr> </table> |
| --- |
| **end\_time**<br><br><br>DATE-TIME |
| **flags**<br><br><br>OBJECT<br><br>This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.<br><br>Click to expand flags<br><br><table> <tr> <td> <p> <strong>								nearest_station							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								sources							</strong> </p> <p> </p> <p>ARRAY																																</p><div><button><div>This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.</div></button></div> <p></p> </td> </tr> <tr> <td> <p> <strong>								units							</strong> </p> <p>							STRING													</p> </td> </tr> </table> |
| **forecast\_date**<br><br><br>DATE-TIME |
| **hourly**<br><br><br>OBJECT<br><br>This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.<br><br>Click to expand hourly<br><br><table> <tr> <td> <p> <strong>								data							</strong> </p> <p> </p> <p>ARRAY																																</p><div><button><div>This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.</div></button></div> <p></p> <div> <button>Click to expand data</button><div> <div> <div><div><table> <tr> <td> <p> <strong>								apparent_temperature							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								cloud_cover							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								dew_point							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								humidity							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								icon							</strong> </p> <p>							STRING													</p> </td> </tr> <tr> <td> <p> <strong>								ozone							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								precip_intensity							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								precip_probability							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								precip_type							</strong> </p> <p>							STRING													</p> </td> </tr> <tr> <td> <p> <strong>								pressure							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								summary							</strong> </p> <p>							STRING													</p> </td> </tr> <tr> <td> <p> <strong>								temperature							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								time							</strong> </p> <p>							DATE-TIME													</p> </td> </tr> <tr> <td> <p> <strong>								uv_index							</strong> </p> <p>							INTEGER													</p> </td> </tr> <tr> <td> <p> <strong>								visibility							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								wind_bearing							</strong> </p> <p>							INTEGER													</p> </td> </tr> <tr> <td> <p> <strong>								wind_gust							</strong> </p> <p>							NUMBER													</p> </td> </tr> <tr> <td> <p> <strong>								wind_speed							</strong> </p> <p>							NUMBER													</p> </td> </tr> </table></div></div></div> </div></div> </td> </tr> <tr> <td> <p> <strong>								icon							</strong> </p> <p>							STRING													</p> </td> </tr> <tr> <td> <p> <strong>								summary							</strong> </p> <p>							STRING													</p> </td> </tr> </table> |
| **latitude**<br><br><br>NUMBER |
| **local\_date**<br><br><br>STRING |
| **longitude**<br><br><br>NUMBER |
| **offset**<br><br><br>NUMBER |
| **start\_time**<br><br><br>DATE-TIME |
| **timezone**<br><br><br>STRING |