Traffic-specific properties

Traffic incidents should be sent as LINE object, but could also be POINT as fallback if no linear data is available.

ElementRequiredData Type

Description

errorYesString

930: General Traffic Map Feedback
931: Traffic Event missing (add)
932: Traffic Event with incorrect info (modify)
933: Traffic Event not exist (delete)
934: Traffic Event verified (confirmation)

referenceIdsNoString[]

Reference IDs of the traffic incident.
Only valid for error codes 932, 933 and 934

domainYes (only for error codes 930 and 931)Object

Traffic Request structure with the following attributes encoded.

↳ subTypeYesInteger

Specific information about the incident type as described below

↳ severityYesNumber

Value from 0 (no restriction) to 100 (full closure) as described below

↳ revNoBoolean

Specific direction, default is false.

↳ headingNoNumber

Heading unit in decimal degrees (0-359) clockwise from the north.

Incident subType CodeDescription
1Roadblock
2Construction
3Event
4Accident
5Disabled Vehicle
6Object in the Roadway
7Lane Closure
Incident TypesSeverity

Description

Roadblock/Closure100

Complete closure/restriction on road. Road is not navigable.

Accident<100

% of road blocked. If there are 4 lanes on a road and one lane is blocked due to accident then value is 25.

Roadworks/Construction<100

% of road blocked. If there are 4 lanes on a road and two lane is blocked due to roadwork then value is 50.

Accident or Roadworks/ Construction0

Default
When user isn’t sure about the % of road blocked by the incident.