> For the complete documentation index, see [llms.txt](https://docs.flytbase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flytbase.com/in-flight-modules/annotations/importing-annotations-from-kml-and-kmz.md).

# Importing Annotations from KML and KMZ

### Why use Imports?

Whether your annotations originate from mission planners, GIS platforms, or previous project templates, importingallows you to:

* Reuse legacy data without manual recreation
* Standardize mission zones and POIs across teams
* Maintain consistency across multi-platform workflows

### KML/KMZ import behavior

FlytBase supports `.kml` and `.kmz` imports for annotations. For annotation imports, the file should contain supported annotation geometry, such as point data used to create annotation markers on the map.

KML/KMZ files created in GIS tools or third-party mission planners may contain different geometry types, such as paths, polygons, or multiple placemarks. These files may not always import as annotations.

{% hint style="info" %}
Annotation imports and mission imports are different workflows. KML/KMZ files used for annotations are imported from the **Annotations** panel, while KML files used for Path Missions must be imported from the supported mission planning workflow.
{% endhint %}

### Unsupported or incorrect KML files

A KML file may fail to import if it contains unsupported geometry or multiple independent shapes.

Examples of unsupported structures include:

* Multiple shapes
* Multiple separate paths
* Multiple polygons
* Multiple placemarks with independent geometries
* Geometry that does not match the selected import workflow

When this happens, FlytBase may reject the file and show an upload error. For example, if multiple shapes are detected, the file is not imported and no annotation or mission geometry is created.

{% hint style="info" %}
FlytBase does not automatically merge multiple shapes or choose one shape from the file. Make sure the file contains only the geometry supported by the workflow you are using.
{% endhint %}

### How to Import

1. Navigate to the Annotations panel in your FlytBase dashboard.

<figure><img src="/files/MzTqnojT4jaRtC1emhXG" alt=""><figcaption><p>Annotations Option on the FlytBase Dashboard</p></figcaption></figure>

2. Click on <img src="/files/UwrcQ6H2Poho1TbguQ1D" alt="" data-size="line">  **→ Import**

<figure><img src="/files/wpybvysoH0BjYWNG4g6C" alt=""><figcaption><p>Option to Add and Import the Annotations</p></figcaption></figure>

3. Select a .kml or .kmz file from your system

<figure><img src="/files/0nr0Jr2GqY6Upj7tQnWA" alt=""><figcaption></figcaption></figure>

4. Once uploaded, the annotations will populate in the panel

### Supported Formats

Ensure your files meet the following criteria:

* File types: .kml or .kmz only
* Geometry types: Points (for annotation markers)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.flytbase.com/in-flight-modules/annotations/importing-annotations-from-kml-and-kmz.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.