Saving incident data to a file

Note: You must have an automotive license.

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 discharge record 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.  Confirm with OK.

5.  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
  • PET: Post Encroachment Time, near collision
  • 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;