get_traffic_messages

Get traffic messages (veimeldinger) from Vegvesen's DATEX II feed - roadworks, road closures, incidents, ferry disruptions, reduced speed and lane restrictions on Norwegian roads. Newest first.

Direct GET

For navigating agents: open the HTML page with parameters in the URL. The result is fetched and displayed without screenshots or form filling.

https://allemannsdata.com/wiki/kilder/vegvesen/get_traffic_messages/?road_number={road_number}&situation_type={situation_type}&lat={lat}&lon={lon}&radius_km=50&include_planned=false&limit=30&offset=0

Replace {road_number}, {situation_type}, {lat}, {lon}, {radius_km}, {include_planned}, {limit} with values. Remove unused optional parameters from the URL.

For software and dashboards: Read the operation descriptor. The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/vegvesen/get_traffic_messages?road_number={road_number}&situation_type={situation_type}&lat={lat}&lon={lon}&radius_km=50&include_planned=false&limit=30&offset=0.

ParameterRequirementJSON typeDescription
road_numberoptionalunionFilter to one road, e.g. "E16", "F42", "RV150" (Ev/Rv/Fv prefixes are normalized, so "Fv. 42" also works).
situation_typeoptionalunionFilter on message type. Main types: MaintenanceWorks, ConstructionWorks (roadworks), RoadOrCarriagewayOrLaneManagement (closures/lane control), SpeedManagement, ReroutingManagement, GeneralNetworkManagement, Accident, VehicleObstruction, EnvironmentalObstruction, AnimalPresenceObstruction, InfrastructureDamageObstruction, PublicEvent, TransitInformation (ferry). Sub-types also match, e.g. "roadClosed", "roadworks", "ferry", "rockfalls", "temporaryTrafficLights".
latoptionalunionWGS84 coordinate to search around.
lonoptionalunionWGS84 coordinate to search around.
radius_kmoptionalnumberSearch radius when lat/lon is given (default 50).
include_plannedoptionalbooleanFalse (default) returns only messages active right now; True also includes announced future works/closures.
limitoptionalintegerMax messages to return, 1 to 100 (default 30).
offsetoptionalintegerNumber of list items to skip; default 0.
Generated JavaScript, Python and response structure

Use JSON when the user requests code, machine-readable data, value extraction or further computation. Use the HTML GET page to identify the correct source and verify parameters.

Example for generated JavaScript and Python

https://allemannsdata.com/wiki/api/v1/kilder/vegvesen/get_traffic_messages?road_number={road_number}&situation_type={situation_type}&lat={lat}&lon={lon}&radius_km=50&include_planned=false&limit=30&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/vegvesen/get_traffic_messages?road_number={road_number}&situation_type={situation_type}&lat={lat}&lon={lon}&radius_km=50&include_planned=false&limit=30&offset=0";
const response = await fetch(url);
if (!response.ok) {
  const failure = await response.json();
  throw new Error(`${failure.error.code}: ${failure.error.message} ${failure.suggestion}`);
}
const result = await response.json();
const data = result.data;

Python without additional packages

import json
from urllib.request import urlopen

url = "https://allemannsdata.com/wiki/api/v1/kilder/vegvesen/get_traffic_messages?road_number={road_number}&situation_type={situation_type}&lat={lat}&lon={lon}&radius_km=50&include_planned=false&limit=30&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "vegvesen",
  "operation": "get_traffic_messages",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "..."}
}
Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

Type: string. Filter to one road, e.g. "E16", "F42", "RV150" (Ev/Rv/Fv prefixes are normalized, so "Fv. 42" also works).
Type: string. Filter on message type. Main types: MaintenanceWorks, ConstructionWorks (roadworks), RoadOrCarriagewayOrLaneManagement (closures/lane control), SpeedManagement, ReroutingManagement, GeneralNetworkManagement, Accident, VehicleObstruction, EnvironmentalObstruction, AnimalPresenceObstruction, InfrastructureDamageObstruction, PublicEvent, TransitInformation (ferry). Sub-types also match, e.g. "roadClosed", "roadworks", "ferry", "rockfalls", "temporaryTrafficLights".
Type: decimal number. WGS84 coordinate to search around.
Type: decimal number. WGS84 coordinate to search around.
Type: decimal number. Search radius when lat/lon is given (default 50).
Type: yes/no. False (default) returns only messages active right now; True also includes announced future works/closures.
Type: integer. Max messages to return, 1 to 100 (default 30).

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the get_traffic_messages lookup

  1. Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
  2. Check types, units, limits and ID formats in the parameter table.
  3. Follow linked results to canonical pages before combining sources.

Misreading to avoid: An empty list means "no results for this lookup". An error message or unavailable source does not mean the data does not exist.

Source-specific next step

Go to the source page for other operations. Use the JSON template only after the HTML result shows that the parameters and source are correct.