Global forecast providers operate at 10–25 km resolution.
At that scale, orographic channelling, coastal sea-breeze, and valley shadow effects are invisible.
In Central Europe — where the Alps, Dinaric Alps, and Carpathians create complex local flow regimes — this is a structural problem. Across a portfolio of wind and solar assets, forecast errors compound into six- and seven-figure annual losses.
Wind power scales with the cube of wind speed. Solar scales with cloud timing at minute resolution. Forecast errors don't scale linearly — they amplify.
A 10 km grid cell averages the wind farm on the ridge with the valley 8 km below. Our 1.5 km grid resolves individual valleys, lake-effect zones, and coastal gradients — the scale where weather actually matters for generation.
A single JSON REST endpoint delivers irradiance components, hub-height wind, and grid-security parameters for any coordinate in our coverage area. No GRIB parsing. No log-law extrapolation. No separate irradiance decomposition library. Ready out of the box.
For tracking arrays and tilted systems, a single GHI value is insufficient. DNI/DHI separation drives plane-of-array irradiance. Clearsky index is the standard ML feature for short-term PV forecasting. Both are derived server-side, delivered ready-to-ingest.
| Variable | API name | Unit | Why it matters for PV |
|---|---|---|---|
| Global horizontal irradiance · GHI | shortwave_radiation | W/m² | Fixed-tilt PV generation baseline. |
| Direct normal irradiance · DNI | direct_normal_irradiance | W/m² | Tracker PV & CSP — the value that matters once panels follow the sun. |
| Diffuse horizontal irradiance · DHI | diffuse_horizontal_irradiance | W/m² | Low-light and overcast performance; plane-of-array calcs. |
| Clearsky GHI | shortwave_radiation_clearsky | W/m² | Ineichen-Perez reference — enables clearsky-index nowcasting. |
| Clearsky index | clearsky_index | 0–1 | GHI / GHIcs — standard feature for PV forecast ML models. |
| Cloud cover (layered) | cloud_cover_low/mid/high | % | PV ramp detection; overcast vs partial cloud discrimination. |
DNI / DHI derived server-side via DIRINT decomposition (Perez et al. 1992). Clearsky GHI uses Ineichen-Perez with monthly Linke turbidity climatology from SoDa.
Most APIs ship 10 m wind and force operators to extrapolate via the log law — which breaks down in stable nocturnal conditions, exactly when wind farms generate hardest. Our WRF models emit wind on height-above-ground levels directly.
| Variable | API name | Fleet / use |
|---|---|---|
| Wind @ 80 m | wind_speed_80m | V80-class, older fleet |
| Wind @ 120 m | wind_speed_120m | V126, N131 modern onshore |
| Wind @ 180 m | wind_speed_180m | Tall onshore, offshore |
| Direction at hub | wind_direction_*m | Turbine yaw control |
| Shear exponent α | wind_shear_exponent | Custom hub extrapolation |
Thunderstorms, high winds, and icing drive most weather-caused outages on the grid. MeteoAPI exposes the physical precursors so you can pre-position crews and curtail controllably — not reactively.
# Hybrid solar + wind site · Austrian Alps, 47.23 N / 15.67 E curl "https://meteoapi.eu/api/v1/forecast" \ --get \ --data-urlencode "latitude=47.23" \ --data-urlencode "longitude=15.67" \ --data-urlencode "hourly=shortwave_radiation,direct_normal_irradiance,diffuse_horizontal_irradiance,\ shortwave_radiation_clearsky,clearsky_index,\ wind_speed_80m,wind_speed_120m,wind_speed_180m,\ wind_direction_120m,wind_shear_exponent,\ temperature_2m,cloud_cover,thunderstorm_probability" \ -H "X-API-Key: met_your_key_here"
| Factor | Global providers · e.g. ECMWF API | MeteoAPI.eu |
|---|---|---|
| Resolution in Alpine / Dinaric terrain | 5–10 km | 1.5–3 km |
| Models blended per forecast | 1 | Up to 14 |
| Hub-height wind | 100 m only (some) | Native 80 / 120 / 180 m + shear exponent α |
| Irradiance components | GHI only (most) | GHI + DNI + DHI + clearsky GHI + clearsky index |
| Uncertainty signal | Paid ensemble add-on | Implicit from model spread — included |
| EU data residency | Not guaranteed | Yes · Croatia / EU only |
| Response format | GRIB2 / NetCDF | Clean JSON REST · CORS · OpenMeteo-compatible |
We propose a structured pilot against your existing forecast provider: