# Real-life KML data

While [GPX files](/tacview/real-life-data/real-life-gpx-data.md) 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](https://www.foreflight.com/products/stratus/) 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](https://en.wikipedia.org/wiki/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](https://flightaware.com/) 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](https://en.wikipedia.org/wiki/Automatic_dependent_surveillance_%E2%80%93_broadcast) 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](https://tacview.net/features/comparison/).

### 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
<?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](/tacview/customization/terrain.md)

### Additional Uses

`KML` files are also a handy way to add static objects in Tacview world. See the [static objects documentation](/tacview/customization/static-objects.md) for more information.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://raia-software-inc.gitbook.io/tacview/real-life-data/real-life-kml-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.