Real-life KML data

While GPX files recorded by GPS are great for a first flight analysis, they lack important data like aircraft attitude. In that domain, nothing come close to the new generation of devices available on the market today.

For example, the Stratus 2S is convenient and offers accurate flight data recording including – not only your position – but also your aircraft complete attitude (roll, pitch and yaw). With such device, after each flight, all you have to do, is to export your data in the widely supported KML (Keyhole Markup Language) file format and load it in Tacview to review accurately your performances and exact trajectories!

You should give a try and experiment with FlightAware flight recordings from real-life. Just open a flight and click on the little Google Earth icon to export the data. Do not forget that you can merge and review multiple flights at once in Tacview! Please note that because of ADS-B limitation, takeoffs and landings are often not recorded in FlightAware.

The use of each specific device is beyond the scope of this article. However, many modern devices are offering an option to record and export tracking data in the universal KML file format. With most devices, all you have to do, is to connect your it to a computer and import the KML files of your choice. Open the file in Tacview using the File → Open command and merge additional files using the File→Merge command.

Support of KML files is a feature of Tacview Standard.

Aircraft Name and Color

It is relatively easy to change the aircraft name and color using a program like Google Earth. You can also manually create and edit the corresponding XML fields using a text editor. Here is a sample of the fields used to change the flight/aircraft appearance in Tacview:

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/kml/ext/2.2">
	<Document>
		<name>FlightAware ✈ UAL1881 ✈ 30-Nov-2015  ✈ KIAD - KSFO</name>
		<Style id="trackStyle">
			<LineStyle>
				<color>ffDB9034</color>
			</LineStyle>
		</Style>
		<Placemark>
			<name>A320</name>
			<description>KIAD - KSFO</description>
			<gx:Track>...</gx:Track>
		</Placemark>
		<ExtendedData>
			<Data name="source">
				<value>FlightAware</value>
			</Data>
			<Data name="GPSModelName">
				<value>ADS-B</value>
			</Data>
			<Data name="flightTitle">
				<value>KIAD - KSFO</value>
			</Data>
			<Data name="pilotName">
				<value/>
			</Data>
			<Data name="tailNumber">
				<value>UAL1881</value>
			</Data>
			<Data name="pilotNotes">
				<value/>
			</Data>
		</ExtendedData>
	</Document>
</kml>

Real Telemetry Data vs. Trajectory Data Only

It is important to understand that Tacview needs real telemetry data to do proper analysis. Some programs and GPS are exporting KML files which are literally just drawings of your aircraft trajectory. While these files can be displayed in Google Earth for example, they cannot be used for a real debriefing. These files will be rejected by Tacview.

Terrain Textures and Terrain Elevation

To add terrain textures and terrain elevation files, see the customization - terrain documentation

Additional Uses

KML files are also a handy way to add static objects in Tacview world. See the static objects documentation for more information.