Saving incident data to a file

Incident data can reveal modeling errors in the Vissim network, such as incorrectly configured conflict areas.

Ensure that the simulation parameters specify at least 10 time steps per simulation second for simulation resolution. This enables Vissim to detect collisions occurring within a single time step.

You can output the following data and data formats:

Output	Text file	Database file	Attribute file from attribute list
Aggregated data	-	-	-
Raw data	*.inc	-	-

Defining evaluation of the incident results

1. On the Evaluation menu, click > Configuration > Direct Output tab.

2. In the Incidents row, select the option Write to file.

3. You can change the time if you wish (Using the Direct output function to save evaluation results to files).

4. Click the More button.

The Detection of incidents window opens.

5. Make the desired changes:

Element

Description

Threshold

The threshold values apply both to the Incidents direct output and to the logging of incidents in the Vehicle network performance.

Note: To use the TTC and Severe deceleration evaluation, you must have a corresponding Automotive license.

TTC: The threshold value for Time To Collision is the time it takes for two vehicles to collide with each other. Vissim calculates the TTC based on the position of the vehicles, their trajectories, and their constant speed if the vehicles are within 100 m upstream of a conflict area during the simulation run. Only this area is relevant in Vissim for detecting potential incidents based on the TTC. Vissim takes vehicles driving in reverse into account. The TTC calculation in Vissim is based on SSAM Surrogate Safety Assessment Model and Validation: Final Report. Vissim calculates TTC in a calculation time step that is the minimum of 1/10 s and the simulation time step. The evaluation specifies the TTC value at these time intervals. Do not change the vehicle type during the simulation run if you have activated the incident evaluation or are logging incidents in the Vehicle network performance. Default value 1.5 s.
Harsh deceleration, default value: - 4.00 m/s2

OpenSCENARIO

Note: To export incidents to OpenSCENARIO, you must have a corresponding Automotive license.

Export incidents: If this option is selected, incident data are exported between vehicles in OpenSCENARIO XML *.XOSC files. This includes vehicles allocated to the Pedestrian category. OpenSCENARIO XML Standard 1.3.1. is supported.

Radius: Radius around the incident in which trajectories of all vehicles are recorded and exported to *.XOSC files. The position of the front edge of the vehicles is relevant. If two vehicles are involved in an incident, the position of the center point between the vehicles is relevant.
Time slot: Period around the incident in which vehicle trajectories are exported to OpenSCENARIO.
Collision, Harsh deceleration, TTC types: If this option is selected, the incident data of this type are exported.

The file name of each *.XOSC file exported is based on the following structure:

<IncidentType>_start<SSSS.SSS>_veh<Id1>_veh<Id2>_simRun<run>.xosc

Example: Collision_start237.400_veh12_veh38_simRun1.xosc

The Start time start<SSSS.SSS> of the incident is given in seconds.

The *.XOSC files are saved in theOpenSCENARIO folder in the working directory of the open *.INPX file.

Data on incidents involving vehicles from the mesoscopic simulation cannot be exported.

6. Confirm with OK.

7. Start the simulation (Running a simulation).

An *.inc file (Incidents protocol) is saved. If the file was created based on the simulation of a scenario, the file name contains the name of the scenario.

Result of incidents evaluation

The *.inc file containing incident data may include the following:

Element	Description
File	Path and name of network file
Comment	Optional comment from the simulation parameters
Date	Time of evaluation
PTV Vissim	Version number, service pack number, build number
Data block	Each row contains data for an incident and the two involved vehicles (1 and 2), separated by ';’. End time of the incident Start time of the incident Vehicle number of vehicle 1 Vehicle type of vehicle 1 Link vehicle 1 was on during the incident Lane vehicle 1 was in during the incident Position of vehicle 1 on the link Vehicle number of vehicle 2 Vehicle type of vehicle 2 Link vehicle 2 was on during the incident Lane vehicle 2 was in during the incident Position of vehicle 2 on the link Type of incident (incident type). May have the following value: Collision TTC: Time To Collision is the time it takes for two vehicles to collide with each other. Severe deceleration

*.inc file with incident data - example:

Incidents protocol

File:     C:\Users\Public\Documents\PTV Vision\PTV Vissim 2025\Examples Demo\3D - Complex Intersection Karlsruhe.DE\Karlsruhe 3D.inpx

Comment:   Karlsruhe 3D example

Date:     27.02.2025 17:47:46

Application: PTV Vissim 2025.00-05* [290294]

EndTime;StartTime;VehNo_Veh1;VehType_Veh1;Link_Veh1;Lane_Veh1;Position_Veh1;
VehNo_Veh2;VehType_Veh2;Link_Veh2;Lane_Veh2;Position_Veh2; IncidentType;

12.800;12.800;  19; 610; 16;  2;10.103;  20; 100; 16;  2;14.029; Collision;

14.000;13.700;  19; 610; 16;  2;10.455;  24; 100; 16;  3;9.598; Collision;

66.800;66.000;  67; 100;311;  2;8.062;  75; 100;10294;  1;3.571; Collision;

75.800;53.200;  11; 620;375;  2;8.850;  46; 610;375;  2;7.098; Collision;

76.300;53.300;  46; 610;375;  2;7.158;  51; 610;375;  2;5.415; Collision;

76.800;53.200;  51; 610;375;  2;5.310;  52; 620;375;  2;3.572; Collision;

77.700;77.000;  67; 100;311;  2;8.062;  93; 100;10294;  1;3.388; Collision;

78.900;78.200;  41; 620;311;  1;2.873;  93; 100;384;  1;0.961; Collision;

88.000;86.800;  91; 610;10207;  2;0.120; 131; 100;10047;  1;7.551; Collision;

97.900;96.500; 187; 100; 16;  3;7.180; 188; 100; 16;  2;6.318; Collision;