Saving vehicle record to a file or database
The vehicle record outputs the attribute values for each vehicle as raw data in one row per time step. You can restrict the evaluation to vehicle classes and individual vehicles. Links and vehicle inputs must defined for the network and OD matrices for the dynamic assignment (Modeling links for vehicles and pedestrians), (Modeling vehicle inputs for private transportation), (Modeling traffic demand with origin-destination matrices)
For result attributes that contain data from routes or platooning, the vehicle record displays values for the end of the time step, i.e. for when the vehicle has traversed the marker of a routing decision and/or, if applicable, the lead vehicle of a platoon has left the Vissim network.
The vehicle record includes link data, if for links the attribute vehicle record has been selected (Attributes of links).
You can output the following data and data formats:
Output |
ASCII file |
MDB file |
Attribute file from attribute list |
---|---|---|---|
Aggregated data |
- |
- | |
Raw data |
*.fzp |
- |
- |
|
Tip: You can show many output attributes of the Vehicle record in parallel, also during the simulation, as a result list Vehicles In Network (Displaying vehicles in the network in a list). |
1. From the Evaluation menu, choose > Configuration > Direct Output tab.
2. In the Vehicle record 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 Vehicle record window opens.
5. Make the desired changes:
Element |
Description |
---|---|
Resolution |
Simulation resolution of time steps |
Including parked vehicles |
Only with the add-on module Dynamic Assignment. If this option is selected, vehicles in parking lots are also taken into account in the evaluation. |
Filters |
|
Attribute selection |
The Attributes button: Opens the window Vehicles In network: Select attributes. You can select attributes for the evaluation (Selecting attributes and subattributes for columns of a list). For import of the * .fzp file into the Autodesk 3DS MAX plug-in Civil View, the attributes and subattributes in the following table are relevant. Do not change the default settings specified in the Decimals column and the Format column, if you choose to import these attributes and subattributes. |
Relevant attributes and subattributes for Autodesk 3DS MAX plug-in Civil View:
Attribute\subattribute |
Default value of column |
|
---|---|---|
Decimals | Format | |
Simulation second |
2 |
Default |
Coordinates front |
3 |
Default |
Coordinates rear |
3 |
Default |
Vehicle type\Name |
0 |
Default |
if Vehicle type\Name does not exist, Autodesk 3DS MAX Civil View looks for Vehicle type\Number and then Vehicle type: |
||
Vehicle type\Number |
0 | Default |
Vehicle type |
0 | Default |
6. Confirm with OK.
7. Start the simulation (Running a simulation).
A *.fzp file is saved.
|
Notes:
|
Result of vehicle record evaluation
A vehicle record *.fzp may contain the following data:
Element |
Description |
---|---|
File |
Path and name of network file |
Comment |
Comment on simulation |
Date |
Time of evaluation |
PTV Vissim |
Version number, service pack number, build number |
Table | Vehicles In network (Displaying vehicles in the network in a list) |
Column names |
Column headers and units |
Data block |
One row each with the number of the vehicle for each simulation step and the attribute values The columns correspond to the sequence of the attributes in the selection. The corresponding add-on module must be installed for some of the listed attributes so that correct values can be recorded, for example, the add-on module Dynamic Assignment. |
|
Notes:
|
Your selection of attributes determines which attribute values are included. You may also display these result attributes in the Vehicles In Network list (Displaying vehicles in the network in a list).
Vehicle record example: file *.fzp
$VISION
* File: C:\Users\Public\Documents\PTV Vision\PTV Vissim 2024\Examples Demo\
3D - Complex Intersection Karlsruhe.DE\Karlsruhe 3D.inpx
* Comment:
* Date: 03.01.2024 12:23:33
* Application: PTV Vissim 2024.00-00* [253691]
*
*Table: Vehicles In Network
*
* SIMSEC: SimSec, simulation second (simulation time [s]) [s]
* NO: No, number (unique vehicle number)
* LANE\LINK\NO: lane\link\no., lane\link\number (unique number of the
link/connector)
* LANE\INDEX: lane\index, lane\index (unique number of the lane)
* POS: Pos, position (distance on the link from the start point of the link or
connector) [m]
* POSLAT: PosLat, Position (lateral) (lateral position at the end of the time step.
Value range 0-1: 0: at the edge of the right lane 0.5: in the middle of the lane
1: at the edge of the left lane)
* SimSec;No;Ln\Link\No;Ln\Index;Pos;PosLat * Simulation second;Number;Lanes\Link\Number;Lanes\Index;Position;
Position (lateral) *
$VEHICLE:SIMSEC;NO;LANE\LINK\NO;LANE\INDEX;POS;POSLAT
0.20;1;1;1;2.57;0.50
0.40;1;1;1;5.71;0.50
0.40;3;2;1;0.22;0.50
0.60;1;1;1;8.86;0.50
0.60;3;2;1;3.25;0.50
0.80;1;1;1;12.02;0.50
0.80;3;2;1;6.29;0.50
1.00;1;1;1;15.18;0.50
1.00;3;2;1;9.33;0.50
...
Superordinate topic:
Configuring evaluations for direct output
Information on editing:
Using the Direct output function to save evaluation results to files