> For the complete documentation index, see [llms.txt](https://support.senterasensors.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senterasensors.com/home/fieldagent-mobile-ios/60-second-guides/wind-turbine-locations.md).

# Wind Turbine Locations

Learn how to see Wind Turbines near a Field.

{% hint style="success" %}
Wind Turbine locations are only provided for planning purposes.

**The pilot in command is always responsible for all on-site assessments.**&#x20;
{% endhint %}

***

## Motivation

* I want to adhere to flight safety [guidelines](https://www.faa.gov/uas).
* I want to avoid filing an [incident](https://www.faa.gov/faq/when-do-i-need-report-accident) during my flight.&#x20;

***

## Requirements

You must have a [data connection](https://support.senterasensors.com/home/fieldagent-mobile-ios/requirements/apple-devices.md#general) to view turbine locations.

***

## Steps

From the Home Screen:

1. Tap on the field you want to review.
2. From the top-right options, tap on the Map Layers button.
3. Under the Infrastructure section, tap on the Wind Turbines toggle to enable it.

Once enabled, the app will display a set of map annotations for each turbine nearby. You can tap on the annotations to view details about the turbine information.

<figure><img src="https://3961074089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZgxcabwSCSKC3cebaIwD%2Fuploads%2FUvswQULRZg9x9PbyctKc%2FWind%20Turbines.gif?alt=media&amp;token=789052c8-3e8f-4b2b-8257-fdcdd0cd49f2" alt=""><figcaption><p>Wind Turbine Locations</p></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.senterasensors.com/home/fieldagent-mobile-ios/60-second-guides/wind-turbine-locations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
