> For the complete documentation index, see [llms.txt](https://docs.phoenixlidar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/toolbars/rover/rover-settings-and-profiles/sensors.md).

# Sensors

The Sensors tab is used to implement sensor activation polygons and hide sensors from certain profiles:

<figure><img src="/files/YC4lsXEuoPodeWYG0LE3" alt=""><figcaption></figcaption></figure>

## Enabled Sensors

Sensors can be unchecked here, which will disable them in the profile. This is useful for systems which have both an aerial camera and a panoramic, mobile-mapping camera.&#x20;

## Sensor Activation Polygon

**Sensor Activation Polygons** are used to automatically enable and disable sensors based on the vehicle position. Sensors will be enabled if the vehicle is within the polygon, and disabled when the vehicle is outside of the polygon. This is useful for preventing collection of unnecessary data.&#x20;

Any polygon loaded into the project as a [Geometry](/spatialexplorer-8-and-9/user-interface/windows/project/geometry.md) can be used as a sensor activation polygon. Load a KML geometry using **File->Open**, then select to load the KML as a Geometry:

<figure><img src="/files/AM0kAOpvWB5zeYwoJSka" alt=""><figcaption></figcaption></figure>

Ensure that the polygon correctly displays in the main view. Consider enabling a **Terrain** base map:

<figure><img src="/files/5n78fVwrN1pPBHKVAeRB" alt=""><figcaption></figcaption></figure>

Next, in the **Sensors** tab of **Rover Settings**, load polygons from the geometry:

<figure><img src="/files/xrPj3amCIJALDTEo3Cqe" alt=""><figcaption></figcaption></figure>

Once loaded, you will see a **SpatialRover** geometry in the project window:

<figure><img src="/files/pQ76Efg0Qr6KQ2bJmlnV" alt=""><figcaption></figcaption></figure>

The sensor activation polygon will appear as a feature in the **SpatialRover** geometry. You can view features of a geometry by clicking the **Properties** button:

<figure><img src="/files/hLeFKfscQZr8hFXFW92D" alt=""><figcaption></figcaption></figure>

With the sensor activation polygon loaded, the system will now automatically control the Sensors window, setting sensors to ACT when inside the polygon, and to OFF when outside of the polygon:

<figure><img src="/files/duFufE7WKQHOz88jw4FN" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Sensor activation polygons will remain on the system until cleared by the user. Sensor activation polygons stored on the system apply to all [rover profiles](/spatialexplorer-8-and-9/user-interface/toolbars/rover/rover-settings-and-profiles.md#profiles) on the system.&#x20;
{% endhint %}

To clear any sensor activation polygons on the system, click the **Clear** button in the **Sensors** tab:

<figure><img src="/files/lBbKqvNNHXc2r8RYKMIs" alt=""><figcaption></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 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.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/toolbars/rover/rover-settings-and-profiles/sensors.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.
