Tacview

Here is an example of csv file from real-life. Please see below for a detailed list of the fields officially supported by Tacview.

You need at least Tacview Standard. Then simply use the file-open command from the main menu to load your file.

The main limitation is that the data of only one aircraft (or any other battlefield unit) can be stored in each .csv file. For now, it is not possible to describe data for multiple aircraft within one file. However you can merge multiple files coming from different sources to replay them all at once in Tacview using the appropriate command. For example: You can open two .csv flight-recordings coming from two different aircraft, at once in Tacview, to see both aircraft flying together in the same world.

You can specify the following metadata in each .csv file name:

• The first part is the NATO name of the corresponding aircraft
• The second – optional – part is the name of the pilot (in parenthesis)
• The third – optional – part is the color of the aircraft [in brackets]

Here in an example of two typical .csv files you could open together:

• Mirage 2000C (Fahrenheit) [Green].csv
• F-14A (Maverick & Goose) [Blue].csv
• A-4E (Viper) [Red].csv

Even if other units may be recognized and supported by Tacview, your data should be always stored in the metric system, and angles expressed in degrees. Here is the list of data (columns headers) supported:

• Time: Time expressed in either Coordinated Universal UTC YYYY-MM-DDThh:mm:ssZ time format, or the offset in seconds since the beginning of the flight
• Longitude: Longitude in degrees (negative for west, positive for east)
• Latitude: Latitude in degrees (negative for south, positive for north)
• Altitude: ASL altitude in meters
• Roll (deg): Roll in degrees (clockwise orientation: positive when rolling to the right, negative to the left)
• Pitch (deg): Pitch in degrees (positive when the aircraft is pointing to the sky, negative when pointing to the ground)
• Yaw (deg): Orientation in degrees relative to the true north

Tacview smartly detects the separators used in your .csv files. However, for best results it is suggested to stick to the following convention:

• Coma , to separate data
• Point . for decimal numbers mark
• Double quotes "{/mono} surrounding strings containing comas

Here is an example of a properly formatted file:

Time,Longitude,Latitude,Altitude,Roll (deg),Pitch (deg),Yaw (deg)
0.00,-116.6847222,32.72722222,34,-0.11536,-0.14832,295.76
4.00,-116.6847222,32.72722222,34,0.36255,-0.26917,295.25
8.00,-116.685,32.72722222,35,0.42297,-0.2417,297.27