Roads coloured by how freely traffic flows, plus live incidents, roadworks and closures, from official national road-authority data. One flag on the map, one extra unit per session.
A dispatch screen that shows why the van is late, a store locator that warns about the closed exit, a dashboard that colours the ring road. This is what the layer looks like once it is on.
Four levels, from free to jammed, computed per road segment from the measured speeds of the national road network. The geometry loads once; a small live-state file refreshes about once a minute and recolours the roads in place.
Watch it move on the map above
Planned works with their dates, live incidents and lane closures, restrictions and open shoulders, as markers or striped stretches of road. Tap one and the layer hands your code the plain GeoJSON feature.
What one event looks likeOne visitor, one map, traffic on, one hour
every refresh free
same pool as everything else
Traffic adds one unit to a map session, however long the visitor watches and however often the state refreshes. Same pool as maps, geocoding and routing; no traffic plan, no per-refresh metering.
See what a month costsimport { Map, config } from '@rijwind/sdk'; import '@rijwind/sdk/style.css'; config.apiKey = 'rw_live_•••'; const map = new Map({ container: 'map', center: [5.1, 52.1], zoom: 7, traffic: true, // roads take their colour, incidents appear }); map.enableTraffic(false); // or behind your own toggle
The SDK opens the session with the traffic grant, loads the road geometry, keeps the live state fresh and draws the incidents. Switch it on at construction or behind your own button at runtime.
Read the traffic guideIncidents, roadworks, closures, restrictions and open shoulders all arrive as GeoJSON features with the same handful of properties. Write the popup once and it holds for all of them, and for anything else that already speaks GeoJSON. This one is from tonight's file.
Everything a developer scans a product page for, in one place, without the adjectives.
Numbers as of September 2026, measured on the live layer.
Two things on top of the basemap. Flow: every monitored road segment coloured by how freely traffic is moving, in four levels from free to jammed, computed from measured speeds. Events: incidents, roadworks, closures, lane restrictions and open shoulders, as markers or as striped stretches of road, each with its details on tap.
From the official open data of the national road authority, normalised into one consistent schema. It is measured by the road network itself, not by tracking phones or navigation apps, so it is privacy-friendly by construction and needs no consent from anyone.
The Netherlands, today. The German motorway feed is wired up but not yet switched on for customers; it will appear on the same layer with no change to your code when it goes live. Other countries follow as their authorities publish usable open data.
The flow state refreshes about once a minute and the map recolours in place; there is no reload. Events are published as the authority publishes them, with the planned works carrying their start and end dates.
One extra unit per map session on top of the session itself, so a map with traffic on is two units for the hour, however often the state refreshes and however long the visitor watches. It comes out of the same monthly pool as maps, geocoding and routing. There is no separate traffic plan and no per-refresh metering.
No. Directions, matrices and isochrones are computed on the road network's free-flow speeds; the traffic layer is a live picture for people looking at a map, not an input to the router. If you need traffic-aware ETAs today, this is not the product for that, and we would rather say so than let you find out.
Yes. The roads and the events are ordinary MapLibre layers with the level and the event type as feature properties, so you can change the colours, hide the categories you do not need, or draw your own markers. The SDK's defaults are what you see on this page.
The layer draws plain GeoJSON features and hands them to your click handler unchanged, so anything on the map is yours to list, filter or link. A query API for events and history is not available yet.
Coverage stops at the Dutch border for now. Flow is measured on the monitored network, which is the motorways and the main roads: city streets carry events but not flow colours. Planned works occasionally outlive their real end date until the authority closes them. And the routing engine does not use any of this, see above.
In the European Union, end to end: the feeds are ingested on our own servers in the Netherlands and the layer files are served from a European CDN. No end-user location is collected to draw it.
The basemap the traffic sits on, in five colour variants.
Car, bike and pedestrian directions on the same key.
Travel times between many origins and destinations at once.
Rain, wind and temperature as layers on your map.
Everything reachable within N minutes, as a polygon.
One unit pool, one table, a cap you set.
One flag on the map. Ten thousand units a month free, and the same key covers maps, geocoding and routing.