Incident

Defines known types of incidents.

Each incident may or may not have specific set of data, depending on it’s kind

Holds information about traffic codes.

Represents the impact of the incident on local traffic.

Incident identifier

The kind of an incident

This value is set to nil if kind value is not supported.

Short description of an incident. May be used as an additional info.

Date when incident item was created.

Date when incident happened.

Date when incident shall end.

Shows severity of an incident. May be not available for all incident types.

Provides additional classification of an incident. May be not available for all incident types.

Breif description of the subtype. May be not available for all incident types and is not available if subtype is nil

The three-letter ISO 3166-1 alpha-3 code for the country the incident is located in. Example: “USA”.

The two-letter ISO 3166-1 alpha-2 code for the country the incident is located in. Example: “US”.

If this is true then the road has been completely closed.

A long description of the incident in a human-readable format.

The number of items in the lanesBlocked.

Information about the amount of congestion on the road around the incident.

A number between 0 and 100 representing the level of congestion caused by the incident. The higher the number, the more congestion there is. A value of 0 means there is no congestion on the road. A value of 100 means that the road is closed.

List of roads names affected by the incident.

Alternate road names are separated by a /. The list is ordered from the first affected road to the last one that the incident lies on.

Contains list of ISO 14819-2:2013 codes

See https://www.iso.org/standard/59231.html for details

A list of lanes, affected by the incident

nil value indicates that lanes data is not available

The range of segments within the overall leg, where the incident spans.

Map of traffic code attributes to values.