Rain radar, temperature, wind, gusts, pressure and cloud from five open European sources, one file per model run, drawn on the GPU. No tile server, no key for the data, free on every plan.
A rain layer over a delivery map, wind over a sailing planner, a two-day forecast for the spot someone just clicked. This is what the files look like once a map is drawing them.
Colour fields, wind particles, arrows, isobars and plain grid values, each a MapLibre layer you can toggle, scrub through time and animate. The rain radar refreshes every five minutes with a two-hour nowcast.
The five sources
The same file that paints the map answers a point query: read one column of the grid and you have two days of temperature, rain and wind for that spot, without a second API.
Try it on the map aboveOne map session, every weather layer on
five sources, every variable
on your own map: no key at all
On a Rijwind map the weather layers add nothing to the session: one unit, whatever you switch on. On your own map they need no key at all, because the files are served openly.
See what a month costsimport { VaneDataset, ColormapLayer, ParticlesLayer } from '@rijwind/vane'; const ds = await VaneDataset.openLatest( 'https://weather.rijwind.com/knmi_harmonie_nl_latest.json', ); map.addLayer(new ColormapLayer({ id: 'temp', dataset: ds, variable: 'temperature' })); map.addLayer(new ParticlesLayer({ id: 'wind', dataset: ds })); // any MapLibre map: no key, no tile server, one file per model run
The file format, the reader, the render modes and the ingest pipeline are all Vane, the open-source project we started: PMTiles, but for gridded weather data. Apache-2.0, on any MapLibre map.
Vane on GitHubA single public file lists every source, its newest run, its grid and how to decode each variable. Your map reads it, follows the pointer to the latest run, and never hard-codes a filename. This is the Dutch model's entry, as served tonight.
All open data from the European weather services, licensed CC BY 4.0. Every run is ingested, repackaged and served openly from weather.rijwind.com. Use the files in your own project; a credit is appreciated.
| Source | Coverage | Grid | Updates |
|---|---|---|---|
| KNMI Harmonie | Netherlands + North Sea | 2 km | hourly, 60 h ahead |
| KNMI rain radar | Netherlands + North Sea | 1 km | every 5 min, +2 h nowcast |
| DWD ICON-D2 | Central Europe | 2.2 km | every 3 h, 48 h ahead |
| DWD ICON-EU | Europe | 7 km | 4× daily, 120 h ahead |
| ECMWF IFS | Global | 25 km | 4× daily, 240 h ahead |
Data © KNMI, DWD and ECMWF, CC BY 4.0. Grid sizes and cadences as published by the sources, September 2026.
Everything a developer scans a product page for, in one place, without the adjectives.
Numbers as of September 2026, read from the live catalogue.
Temperature, rain, wind (as particles and as arrows), wind gusts, sea-level pressure as isobars and cloud cover, from five open sources: the Dutch national model and rain radar, two German models for central Europe and Europe, and the global European model. Pick a source top-right, toggle layers at the bottom, scrub the time slider, click anywhere for a point forecast.
From the open-data programmes of the European weather services: KNMI, DWD and ECMWF, all under the CC BY 4.0 licence. Every model run is ingested within minutes of publication, repackaged into one file, and served from our CDN. The radar nowcast updates every five minutes.
As fresh as the source. The Dutch model runs hourly and looks 60 hours ahead, the radar every five minutes with a two-hour nowcast, the German models every three to six hours, the global model four times a day out to ten days. The catalogue carries the exact run time and publish time of every source, so your map can show its own age.
A forecast is one compact file on a CDN with every variable and every timestep inside. The map asks for exactly the byte ranges it needs with HTTP range requests and draws them on the GPU as MapLibre layers: colour fields, particles, contours. Static hosting plus range requests, nothing running in the middle.
Yes, on any MapLibre map. Install the open-source Vane library, open the latest run from weather.rijwind.com and add the layers you want. The files are served openly, so no API key is involved; a 'weather data hosted by Rijwind' credit is appreciated, and the CC BY attribution to the source is required.
Not yet as a one-liner. Today you add the Vane layers to a Rijwind map the same way you would to any MapLibre map, which is a few lines. A weather option on the SDK's map is planned; there is no date on it.
Nothing extra. On a Rijwind map the weather layers add no units to the session, on every plan including Free. On your own map there is no key and no bill at all. It runs on Vane, the open-source project we started, and is a showcase of what open data plus a CDN can do.
The same file that paints the map answers a point query client-side: read one column of the grid and you have the full series for that spot, which is what the click-for-forecast panel does. There is no separate point-forecast API; if you need one server-side, the files are plain enough to read from any language.
The global model is 25 km per grid cell, so it is a synoptic view, not a local forecast: for street-level detail you want the national and regional models, which cover the Netherlands and central Europe only. There is no historical archive yet, only the latest runs, and no severe-weather warnings or lightning. It is a rendering of the models as published, not a forecast product of our own.
The files are served from a European CDN and the pipeline runs on our own servers in the Netherlands. The map itself does nothing but fetch bytes: no account, no cookies, no tracking.
The basemap under the weather, in five colour variants.
Congestion and incidents as a layer on your map.
Relief, contours and 3D terrain for the outdoors.
Car, bike and pedestrian directions on the same key.
A map as a picture, in an email or a PDF.
One unit pool, one table, a cap you set.
The layers you just played with, on any MapLibre map, from open files on a CDN. The same key covers maps, geocoding and routing when you get to them.
