Weather · Forecast

Hub-height wind field

Wind speed and direction at 100 m on a one-degree grid across Texas and its surroundings — the field itself, to be drawn rather than charted. The grid runs past the state line on purpose: a particle advected to the edge of its data dies there, and thinning flow along a border reads as weather when it is not. Data by Open-Meteo, CC-BY-4.0.

openmeteo-wind-fieldevery 3 hours · 1h rows168 entities
G_325_0975
6.8m/s
2026-09-19 23:00 UTC
G_295_0955
7.2m/s
2026-09-19 23:00 UTC
G_335_1015
7.2m/s
2026-09-19 23:00 UTC
Read from the Dryos API and cached for an hour; the stream itself updates every 3 hours.

What is in it

Updates
every 3 hours · 1h rows
Entities
168 entities — G_325_0975, G_295_0955, G_335_1015…
Source timezone
UTC — every timestamp Dryos serves is UTC
Coverage
31 August 2026 to now
Rows held
1,395,072
Primary key
cell, interval_start_utc, source_published_at_utc

What it measures

Every value, its unit, and what the source means by it.

  • Wind speedm/s

    Forecast wind speed at 100 m — turbine hub height.

    wind_speed_100m_ms
  • Wind direction°

    The compass bearing the wind blows from, at 100 m. The direction the air travels is the opposite of this.

    wind_direction_100m_deg

Columns

Exactly what a request answers with, read from the API rather than written here.

ColumnTypeDescription
interval_start_utcrequiredtimestampStart of the hour the values describe, UTC.e.g. 2026-08-31T12:00:00Z
cellrequiredstringGrid cell id, encoding its own position: G_315_1005 is 31.5°N, 100.5°W — tenths of a degree, west positive.e.g. G_315_1005
wind_speed_100m_msrequirednumberForecast wind speed at 100 m, metres per second. Hub height, so this is the field that matters for wind generation.e.g. 8.7
wind_direction_100m_degrequirednumberDirection the wind blows FROM at 100 m, degrees from north — the meteorological convention. A vector pointing where the air is going is the reverse of this, and that flip is where the sign gets lost.e.g. 165
latrequirednumberLatitude of the reading, degrees north. Published by the source, not inferred: this is where the instrument is or the point that was sampled.e.g. 30.19
lonrequirednumberLongitude of the reading, degrees east of Greenwich.e.g. -97.67
source_published_at_utcrequiredtimestampThe vintage: which issue of the forecast this row belongs to. The same hour appears once per issue, and the newest is the current view.e.g. 2026-08-31T13:00:00Z
collected_at_utcrequiredtimestampWhen Dryos collected this row, UTC. Stamped by the platform, not the collector.e.g. 2026-08-31T13:02:00Z

Read it

Public, read-only, no key and no sign-up. Relative times stay relative, so a URL keeps working.

The newest rows

shell
curl "https://api.dryos.ai/v1/datasets/openmeteo-wind-field/query?node=G_325_0975&limit=12"

The catalogue entry — every column, its type and the source

shell
curl "https://api.dryos.ai/v1/datasets/openmeteo-wind-field"

Full parameters — bucketing, aggregation, filters and search — are on the API reference.

Ask an agent

The same stream through the Model Context Protocol, so Claude, ChatGPT, Cursor or any MCP client can query it directly.

shell
claude mcp add --transport http dryos https://api.dryos.ai/mcp

Then ask:

What has Wind speed been at G_325_0975 over the last 24 hours, and when did it peak?

Setup for every client is on the MCP server page.

How this stream is checked

  • Pulled straight from Open-Meteo (CC-BY-4.0) — no reseller in between — and compared against that file before it is served.
  • Null means the source did not report it — never zero.
  • A reading lands every 3 hours; the interval timestamp is the start of the interval, in UTC.
  • Every weather timestamp is UTC at the source and at Dryos.

Related streams