> 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/customizing-annotations-fine-tune-annotations-for-operational-precision.md).

# Customizing Annotations: Fine-Tune Annotations for Operational Precision

### Annotation Fields

Each annotation includes several editable fields to help describe and locate the point more accurately:

* **Name**: Identify the annotation clearly for your team
* **Description**: Add purpose or notes related to the point of interest
* **Group:** Groups and sub-groups let you keep annotations tied to a region, a mission phase, a piece of equipment, or any other structure that fits your operation.
* **Latitude & Longitude**: View precise placement on the map
* **Altitude (AGL)**: Define the vertical height above ground level for better 3D context

<figure><img src="/files/L4Df6xqmOIRKtu0Ax0mA" alt="" width="288"><figcaption><p>Annotation editor showing name, description, coordinates, and AGL altitude options</p></figcaption></figure>

### Icon Selection

You can now choose from a wider set of default icons that visually represent common mission elements (e.g. hazard, fire, alert, etc.).

Additionally, upload your own **custom SVG icons** to match internal symbols or workflows:

1. In the Annotations panel, click on **Icons**

<figure><img src="/files/3NE1IdSMq5QaxhW0imHs" alt=""><figcaption></figcaption></figure>

2. Click on **Upload** to select a custom icon (maximum 5 icons allowed)

<figure><img src="/files/AGU3Vljk6Km6GiCdD3IS" alt="" width="288"><figcaption><p>Icon selection menu showing default and custom icon options</p></figcaption></figure>

### Color Palette

Annotations now support an expanded range of color options. Use these to categorize or prioritize annotations based on status, severity, or mission type

### Tips for Customization

* Use color consistently across teams to build familiarity
* Standardize icon sets across projects for easy identification
* Include relevant context in descriptions to reduce back-and-forth during missions