FCDOutput
The FCD (floating car data) export contains location and speed along with other information for every vehicle in the network at every time step. The output behaves somewhat like a super-accurate high-frequency GPS device for each vehicle. The outputs can be processed further using the TraceExporter tool for adapting frequency, equipment rates, accuracy and data format.
Instantiating within the Simulation#
The simulation generates this output when setting the option --fcd-output <FILE>. <FILE> is the name of the file the output will be written to. Any other file with this name will be overwritten, the destination folder must exist.
By default, fcd-output is enabled for all vehicles and persons in the simulation with output in each simulation step. Using device assignment options or parameters (i.e. --device.fcd.probability 0.25) the set of vehicles which generate fcd output can be reduced. The output period can be set by using option --device.fcd.period <TIME>. To delay output (i.e. until some warm-up time has passed), the option --device.fcd.begin <TIME> may be used.
Generated Output#
The generated XML file looks like this:
<fcd-export>
<timestep time="<TIME_STEP>">
<vehicle id="<VEHICLE_ID>" x="<VEHICLE_POS_X>" y="<VEHICLE_POS_Y>" angle="<VEHICLE_ANGLE>" type="<VEHICLE_TYPE>"
speed="<VEHICLE_SPEED>"/>
... more vehicles ...
</timestep>
... next timestep ...
</fcd-export>
The values without a tick in the "On" column need to be enabled explicitly and the ones without a tick at "Meso" are not available for the mesoscopic simulation.
| Name | Type | On | Meso | Description |
|---|---|---|---|---|
| timestep | (simulation) seconds | x | x | The time step described by the values within this timestep-element |
| id | id | x | x | The id of the vehicle |
| x | m or longitude | x | x | The absolute X coordinate of the vehicle (center of front bumper). The value depends on the given geographic projection. With the option --fcd-output.utm, the value is given in UTM coordinates, taking the network offset into account. If the network has no TUM projection (check the line containing "location netOffset" in the network file), you need to reprojected it, e.g. using netconvert. With the option --fcd-output.geo, the longitude is given (WGS84). |
| y | m or latitude | x | x | The absolute Y coordinate of the vehicle (center of front bumper). The value depends on the given geographic projection. With the option --fcd-output.utm, the value is given in UTM coordinates, taking the network offset into account (see the info above regarding the projection issue). With the option --fcd-output.geo, the lattitude is given (WGS84). |
| z | m | (x) | x | The z value of the vehicle (center of front bumper). Note: This value is only present if the network contains elevation data |
| angle | degree | x | x | The angle of the vehicle in navigational standard (0-360 degrees, going clockwise with 0 at the 12'o clock position) |
| type | id | x | x | The name of the vehicle type |
| speed | m/s | x | x | The speed of the vehicle |
| speedVec | m/s | x | x | The speed vector of the vehicle:speed_x,speed_y |
| pos | m | x | x | The running position of the vehicle measured from the start of the current lane. |
| lane | id | (x) | The id of the current lane (only available in microsimulation). | |
| edge | id | (x) | x | The id of the current edge (only available in meso). |
| slope | degree | x | x | The slope of the vehicle in degrees (equals the slope of the road at the current position) |
| signals | bitset | The signal state information (blinkers, etc) | ||
| acceleration | m/s2</sup | The longitudinal acceleration | ||
| accelerationLat | m/s2</sup | The lateral acceleration (only with enabled sublane model) | ||
| accelerationVec | m/s2 |