Linking Meteostat as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Meteostat connector syncs hourly, daily, monthly, and more 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
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- 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 on RapidAPI - the free plan includes 500 requests per month.
Meteostat has no account-scoped list of stations, so list the weather station IDs you want to sync.
You'll be asked for:
- RapidAPI key
- Weather station IDs: comma-separated list of Meteostat station IDs. Up to 25 stations.
- 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_attimestamp). 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 for a full explanation of how each mode works and how to choose between them.
All Meteostat tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
RapidAPI keyType: password Required: True | |
Weather station IDsType: text Required: True | Comma-separated list of Meteostat station IDs. Up to 25 stations. |
Unit systemType: select Required: True | |
Start dateType: 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 | — |
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 your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.