# Open-Meteo Global Weather and Climate Forecast Radar (`adaptive_nightmare/open-meteo-weather-radar`) Actor

Extract real-time weather observations, hourly and daily temperature forecasts, precipitation, wind speed, UV index, and weather codes across any global coordinates.

- **URL**: https://apify.com/adaptive_nightmare/open-meteo-weather-radar.md
- **Developed by:** [Darim Quraishi](https://apify.com/adaptive_nightmare) (community)
- **Categories:** Automation, Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.85 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Open-Meteo Global Weather and Climate Forecast Radar

Extract real-time weather observations and multi-day climate forecasts across global coordinates using Open-Meteo open weather datasets.

### Features

- Extracts live observations including air temperature, apparent temperature, relative humidity, atmospheric pressure, and wind speed.
- Generates multi-day daily forecasts covering maximum and minimum temperatures, UV index peaks, precipitation sums, and wind gusts.
- Translates WMO weather interpretation codes into plain descriptive text labels.
- Supports metric and imperial unit conversions for temperature, precipitation, and wind velocity.
- Operates via public REST endpoints with zero API tokens and zero proxy overhead.
- Delivers clean records formatted for export to JSON, CSV, Excel, or automated analytics workflows.

### Input parameters

- Latitude: Geographical coordinate between -90 and 90. Default is 40.7128.
- Longitude: Geographical coordinate between -180 and 180. Default is -74.0060.
- Forecast Days: Number of daily forecasts to retrieve, from 1 to 16 days. Default is 7.
- Temperature Unit: Scale for temperature values, choosing Celsius or Fahrenheit.
- Wind Speed Unit: Unit for wind speed, choosing km/h, m/s, mph, or knots.
- Precipitation Unit: Unit for rainfall volume, choosing millimeters or inches.
- Timezone: Coordinate based local detection (auto) or specific IANA timezone identifier.

### Output dataset fields

Each dataset record represents either a current observation or a daily forecast with the following properties:

- recordType: Type of record (current_observation or daily_forecast).
- location: Object containing latitude, longitude, elevation in meters, and timezone metadata.
- observationTime / date: ISO formatted timestamp or calendar date.
- weatherCode: Official World Meteorological Organization (WMO) code integer.
- weatherCondition: Human-readable weather description (such as Clear sky, Slight rain, or Thunderstorm).
- temperature / tempMax / tempMin: Numerical temperature readings calibrated to selected units.
- apparentTemperature: Heat index and wind chill perceived temperature.
- relativeHumidityPercent: Current humidity percentage from 0 to 100.
- precipitationSum: Accumulated rainfall and precipitation amount.
- uvIndexMax: Maximum daily UV solar radiation index.
- windSpeed / windSpeedMax: Wind velocity values.
- windDirectionDegrees / windDirectionDominant: Compass orientation in degrees.
- sunrise / sunset: ISO timestamps for astronomical solar events.
- scrapedAt: UTC timestamp when the data was extracted.

### Use cases

- Logistics planning: Monitor route conditions and storm alerts across distribution hubs.
- Agriculture operations: Track precipitation accumulations and frost risks for field management.
- Travel applications: Feed live destination forecasts into itinerary builders and trip calculators.
- Renewable energy analysis: Monitor solar irradiance and wind velocity indicators across geographical facilities.

# Actor input Schema

## `latitude` (type: `number`):

Geographical latitude coordinate (for example: 40.7128 for New York, 51.5074 for London, or 35.6762 for Tokyo).

## `longitude` (type: `number`):

Geographical longitude coordinate (for example: -74.0060 for New York, -0.1278 for London, or 139.6503 for Tokyo).

## `forecastDays` (type: `integer`):

Number of daily forecast records to generate (1 to 16 days).

## `temperatureUnit` (type: `string`):

Temperature scale for measurements.

## `windSpeedUnit` (type: `string`):

Unit of measurement for wind speed velocity.

## `precipitationUnit` (type: `string`):

Unit of measurement for rainfall and precipitation volume.

## `timezone` (type: `string`):

Timezone string or auto for coordinate based local timezone detection.

## Actor input object example

```json
{
  "latitude": 40.7128,
  "longitude": -74.006,
  "forecastDays": 7,
  "temperatureUnit": "celsius",
  "windSpeedUnit": "kmh",
  "precipitationUnit": "mm",
  "timezone": "auto"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("adaptive_nightmare/open-meteo-weather-radar").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("adaptive_nightmare/open-meteo-weather-radar").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call adaptive_nightmare/open-meteo-weather-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,adaptive_nightmare/open-meteo-weather-radar"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/C05ALZ0zlsEi996OY/builds/wy4J1O0864hy8ESgg/openapi.json