> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Meteostat as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/meteostat

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Meteostat connector syncs weather observations, station metadata, and climate normals into the PostHog data warehouse, so you can analyze them alongside your product data.

## Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

Sync historical weather and climate data for weather stations from the Meteostat JSON API (hosted on RapidAPI). Get a free API key by subscribing to the [Meteostat API listing](https://rapidapi.com/meteostat/api/meteostat/) on RapidAPI - the free plan includes 500 requests per month.

Meteostat has no account-scoped list of stations, so list the [weather station IDs](https://meteostat.net) you want to sync. To sync point-based weather for any geographic coordinates, also add your locations.

You'll be asked for:

-   **RapidAPI key**
-   **Weather station IDs** - Comma-separated list of Meteostat station IDs. Up to 25 stations.
-   **Locations** - Optional. Coordinates for point tables, separated by semicolons or new lines. Write each one as `latitude,longitude` with an optional elevation in meters (for example, `43.6667,-79.4,113`). Up to 25 locations.
-   **Unit system** - Choose between Metric (°C, mm, km/h), Imperial (°F, in, mph) and Scientific (K, mm, m/s).

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

The station and point time series tables (Hourly, Daily, Monthly, PointHourly, PointDaily, PointMonthly) support incremental sync. The metadata and normals tables (Stations, Normals, PointNormals) are full refresh only.

## Configuration

| Option | Description |
| --- | --- |
| `RapidAPI key` **Type:** password **Required:** True |  |
| `Weather station IDs` **Type:** text **Required:** True | Comma-separated list of Meteostat station IDs. Up to 25 stations. |
| `Locations` **Type:** textarea **Required:** False | Optional. Locations for the point tables, separated by semicolons or new lines. Write each one as latitude,longitude with an optional elevation in meters, for example 43.6667,-79.4,113. Up to 25 locations. |
| `Unit system` **Type:** select **Required:** True |  |
| `Start date` **Type:** text **Required:** False | Earliest day to sync (YYYY-MM-DD). Defaults to 2015-01-01 to keep the initial sync within a typical RapidAPI free-tier quota. |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `Hourly` | Historical hourly weather observations for a station, with gaps optionally filled by statistically optimized model data. | Incremental, Full refresh | time | — |
| `Daily` | Historical daily weather statistics for a station, aggregated from observations and model data. | Incremental, Full refresh | date | — |
| `Monthly` | Historical monthly weather statistics for a station, aggregated from hourly observations, daily records, and model data. | Incremental, Full refresh | date | — |
| `Stations` | Meta data for each configured weather station, including its names, country, region, identifiers, location, time zone, and data inventory. | Full refresh | — | — |
| `Normals` | Climate normals for a station: long-term monthly averages of weather observations, with twelve rows (one per month) for each reference period. | Full refresh | — | — |
| `PointHourly` | Historical hourly weather observations for a geographic location, interpolated from nearby weather stations, with gaps optionally filled by model data. | Incremental, Full refresh | time | — |
| `PointDaily` | Historical daily weather statistics for a geographic location, interpolated from nearby weather stations. | Incremental, Full refresh | date | — |
| `PointMonthly` | Historical monthly weather statistics for a geographic location, interpolated from nearby weather stations. | Incremental, Full refresh | date | — |
| `PointNormals` | Climate normals for a geographic location: long-term monthly averages, with twelve rows (one per month) for each reference period. | Full refresh | — | — |

## Troubleshooting

-   If the connection fails with an authorization error, the rapidAPI key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
-   If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
-   If a point table fails with "No locations configured", add at least one location in the source settings. Point tables require coordinates to sync.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.