Traffic signs and accessibility map (NDW)

Base URL

https://wegkenmerken.ndw.nu/api/rest/static-road-data/traffic-signs/v4

Endpoints 5

• GET/current-stateThe current state: every sign as a GeoJSON feature (or CSV), updated daily. With a filter it is filtered live, including today's changes. Without a status filter only placed signs (PLACED).
• GET/eventsAll published changes, oldest first, at most 100 at a time; read on with offset (timestamp).
• GET/collectionsThe supported coordinate reference systems (CRS84 and RD, EPSG 28992).
• GEThttps://wegkenmerken.ndw.nu/api/images/{id}Photo of the sign (JPEG, ~14 kB); the address is in imageUrl.
• GEThttps://opendata.ndw.nu/verkeersborden_actueel_beeld.csv.gzThe whole current state as a file: CSV (235 MB zipped) or GeoJSON in RD (_rd.geojson.gz, 228 MB) and in degrees (_wgs84.geojson.gz, 236 MB). Once a day around 12:05.

The APIs of this source 1 · from the provider's documentation from the description

Filtering from the description

Each condition is its own query parameter; combinations act as AND. Exact match, no wildcards.

Parameters 11

Fields per sign (current-state, GeoJSON properties) 15

Limits and pitfalls

• current-state has no paging: without a filter you get the whole country. rvvCode=A1 alone is 97 MB, Amsterdam 56 MB. Always filter, or use the download file. experience
• events: at most 100 per call (limit=101 returns 400). tested
• No key and no documented rate limit; filtered requests answered within 0.1 seconds. tested
• The documentation still mentions data.ndw.nu and the parameter names rvv-code and road-section-ids. The OpenAPI specification and the working API use wegkenmerken.ndw.nu/api with rvvCode and roadSectionId. The old v1 addresses on data.ndw.nu return 404. tested
• An unknown parameter is silently ignored (foo=bar simply returned 73 signs). A typo in a filter name therefore quietly returns the unfiltered, much larger response. tested
• events has no publication timestamp in the response, even though offset works on it. Keep the time of your last call yourself and read on from there; an event may then arrive twice. tested
• In events the structure differs from current-state: location.wgs84.latitude, location.road.roadSectionId, location.county.code, details.imageUrl. current-state is flat. tested
• Join roadSectionId to the NWB (wvk_id), but mind nwbVersion: road sections change between NWB versions. experience
• wegkenmerken.ndw.nu has no robots.txt (the web app returns its start page for every path); data.ndw.nu redirects robots.txt to a page with Disallow: /. That is why we did not call the accessibility map. tested

Try it HTTP 200 · 386 ms · 16 Oct

https://wegkenmerken.ndw.nu/api/rest/static-road-data/traffic-signs/v4/current-state?rvvCode=C22a&countyCode=GM0363

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "id": "061dc8bb-f323-48d7-bc5b-a03e6fa9187c",
      "geometry": {
        "type": "Point",
        "coordinates": "…"
      },
      "properties": {
        "validated": "n",
        "rvvCode": "C22a",
        "zoneCode": "ZB",
        "status": "PLACED",
        "textSigns": [
          {
            "type": "EMIS",
            "text": "[[c22a3]]"
          },
          {
            "type": "EMIS",
            "text": "[[c22a9]]"
          }
        ],
        "placement": "L",
        "side": "W",
        "bearing": 274,
        "fraction": 0.9918174,
        "drivingDirection": "T",
        "roadName": "Jan Vroegopsingel",
        "roadSectionId": 600980960,
        "nwbVersion": "2026-05-01",
        "countyName": "Amsterdam"
      }
    },
    {
      "type": "Feature",
      "id": "087aa8eb-2990-498e-af72-e185d1dfd664",
      "geometry": {

Shortened response, saved at harvest time. Click the URL for the real, current response.