Open-Meteo Weather Forecast Scraper
parseforge/open-meteo-forecast-scraper
OtherAutomation
Scrapes weather forecasts from Open-Meteo for a given latitude and longitude. Returns each forecast interval as a flat row with temperature, precipitation, wind, and other weather variables.
- Total users
- 2
- Monthly active
- 1
- Total runs
- 45
- Bookmarked
- 0
- Rating
- Not rated yet
- Last modified
- 12 days ago
Overview
Open-Meteo Weather Forecast Scraper
Scrape weather forecasts from Open-Meteo for any location on Earth, up to a million per run. Get hourly and daily temperature, precipitation, wind, and more in a flat row. No API key, no registration, no rate limits.
Weather APIs often require sign-ups, API keys, and strict rate limits that block bulk collection. This Actor reads the public Open-Meteo forecast feed directly, letting you pull structured weather data for any latitude and longitude pair. It returns a clean, flat dataset ready for analysis, modeling, or storage.
| Who uses it | What they scrape Open-Meteo for |
|---|---|
| Data scientists | Building weather-dependent machine learning models with bulk historical forecast data. |
| Logistics planners | Pulling forecast data for multiple warehouse or route coordinates to anticipate disruptions. |
| Agricultural analysts | Collecting precipitation and temperature forecasts for crop yield prediction across farm locations. |
| Event organizers | Monitoring wind and temperature forecasts for outdoor venues in the days ahead. |
What it does
This Actor collects weather forecasts from Open-Meteo for a given latitude and longitude and returns each forecast interval as a flat row.
- ๐ Coordinate-based targeting: provide a latitude and longitude to get the forecast for that exact point.
- ๐ Flexible volume control: set a maximum number of forecast intervals to collect, from a single point up to one million rows.
- ๐ Structured flat output: each forecast interval becomes one row with all weather variables, ready for CSV, JSON, Excel, or XML export.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Open-Meteo data
๐พ Monitor crop-critical weather.
An agricultural analyst pulls temperature and precipitation forecasts for 50 farm coordinates each morning to update irrigation and harvest schedules.
๐ Plan logistics around storms.
A dispatcher collects wind and precipitation forecasts for distribution center locations to reroute trucks before severe weather hits.
๐ Train weather-dependent models.
A data scientist collects a million forecast intervals across multiple cities to build a feature store for a demand-forecasting model.
๐ช Decide on outdoor event safety.
An event manager checks wind gust and temperature forecasts for a venue coordinate to decide whether to set up tents or delay gates.
Why choose this scraper
| What you get | |
|---|---|
| No API key required | Reads the public Open-Meteo endpoint directly with no account or registration. |
| Bulk collection | Collect up to a million forecast intervals in a single run for large-scale analysis. |
| Fixed schema | Every run returns the same flat structure, so your downstream pipelines never break. |
| Free and open data | Open-Meteo provides its forecasts under a free license, and this Actor adds no extra cost beyond Apify platform usage. |
How it compares
This Actor focuses on bulk forecast collection by coordinates with a configurable row limit, while the other Open-Meteo scrapers on Apify offer different input methods or data types.
| Feature | ParseForge | Open Meteo Scraper | Weather Forecast API | Open-Meteo Weather Forecast Scraper |
|---|---|---|---|---|
| Coordinate-based input | Yes | Not listed | Yes | Yes |
| City name input | Not listed | Not listed | Yes | Not listed |
| Configurable max rows per run | Yes, up to 1,000,000 | Not listed | Not listed | Not listed |
| Historical weather data | Not listed | Yes | Not listed | Not listed |
| Current conditions | Not listed | Yes | Yes | Yes |
| No API key required | Yes | Yes | Yes | Yes |
Configure the run
Drive the Actor with a latitude and longitude pair, and set a maximum number of forecast intervals to cap the dataset size. The Input tab lists every parameter.
A first run with the defaults:
{
"latitude": "52.52",
"longitude": "13.41",
"maxItems": 10
}
A larger pull:
{
"latitude": "52.52",
"longitude": "13.41",
"maxItems": 200
}
Pricing
Pay-per-result: $0.005 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.50 |
| 1,000 results | $5.00 |
| 10,000 results | $50.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Open-Meteo Weather Forecast Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Open-Meteo through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/open-meteo-forecast-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that your latitude and longitude are within valid ranges (-90 to 90 for latitude, -180 to 180 for longitude) and that the coordinates point to a location on land or near shore where Open-Meteo provides forecast data.
Why does the run fail immediately?
Ensure both latitude and longitude fields are filled in. They are required inputs. Also verify the values are plain numbers in decimal degrees, not city names or addresses.
Why are some weather variables missing in my output?
Open-Meteo returns all available variables for the requested coordinates. If a variable is absent, it may not be computed by the weather model for that specific location or forecast horizon.
Why did I get fewer rows than my maxItems setting?
The Actor collects up to the number of forecast intervals you set, but if the Open-Meteo endpoint returns fewer intervals for the requested location and model, the dataset will be smaller.
Why are the coordinates reversed in my output?
Double-check that you entered latitude in the latitude field and longitude in the longitude field. Swapping them will produce forecasts for a different location, possibly in an ocean or uninhabited area.
FAQ
| Question | Answer |
|---|---|
| Do I need an API key or account to use this? | No. This Actor reads the public Open-Meteo endpoint, which requires no API key, no registration, and no authentication. |
| What weather variables does the forecast include? | The dataset includes temperature, precipitation, wind speed and direction, humidity, pressure, cloud cover, and more, depending on the Open-Meteo model output for the requested coordinates. |
| Can I get forecasts for multiple locations in one run? | Each run targets a single latitude and longitude pair. To collect forecasts for multiple locations, run the Actor once per coordinate set, or use Apify's actor orchestration to loop over a list of coordinates. |
| Is the data hourly or daily? | Open-Meteo provides both hourly and daily forecast intervals. The output rows reflect the granularity available from the endpoint for your requested parameters. |
| How many forecast days ahead can I get? | Open-Meteo typically provides forecasts out to 16 days, though the exact horizon depends on the weather model selected. The Actor collects whatever the endpoint returns. |
| Can I get historical weather data with this Actor? | This Actor is designed for forecast data. For historical weather, you would need an Actor that calls Open-Meteo's historical API endpoint. |
| What output formats are supported? | You can export your dataset to CSV, JSON, Excel, or XML from the Apify platform after the run completes. |
| Is there a rate limit? | Open-Meteo's public endpoint does not enforce rate limits, and this Actor does not add any artificial throttling beyond what the platform requires for fair use. |
| What coordinates format should I use? | Use decimal degrees. For example, 52.52 for Berlin's latitude and 13.41 for its longitude. The valid range is -90 to 90 for latitude and -180 to 180 for longitude. |
| Can I use city names instead of coordinates? | This Actor requires latitude and longitude. You can geocode city names to coordinates using a separate geocoding Actor or service before passing them here. |
Related actors
Browse the full ParseForge collection for more scrapers.
๐ Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
โ ๏ธ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Open-Meteo. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
Input
| Field | Type | What it does | Default |
|---|---|---|---|
| latitude required | string | Required. Latitude of the location in decimal degrees (for example 52.52 for Berlin). Range -90 to 90. | 52.52 |
| longitude required | string | Required. Longitude of the location in decimal degrees (for example 13.41 for Berlin). Range -180 to 180. | 13.41 |
| maxItems | integer | Maximum number of forecasts to collect per run. | 10 |
Pricing
from $4.52 per 1,000 results
| Charged for | What it is | Price each |
|---|---|---|
| result | Single result in the default dataset. | $0.00452 to $0.005 |
Tiered: the lower figure is the price on a higher Apify plan. Billing and the free credit live on Apify.
API
One POST returns the dataset directly. Same shape for every scraper in the library, so swapping the slug is the only change.
curl -X POST "https://api.apify.com/v2/acts/parseforge~open-meteo-forecast-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"helloWorld": 123
}' Examples
Input that runs as-is.
{
"helloWorld": 123
} Reviews
No reviews yet. Be the first.
Issues
We build and maintain this scraper, so a problem with it comes to us. Report it on the Apify listing and the thread stays attached to the scraper where the next person can find it: open an issue.
Broken and urgent, or you would rather not post in public? Write to parseforge@protonmail.com and it reaches the people who wrote it.
Related scrapers
Run Open-Meteo Weather Forecast Scraper on Apify All scrapers
