> 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/camera-settings.md).

# Camera Settings

Camera settings can be modified by clicking the camera in the left banner:

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

## Camera Triggering Options

Camera triggering method can be configured here. The following options are available:&#x20;

{% hint style="warning" %}
Sensor activation polygons will apply to camera sensors. Ensure that your selected camera triggering method agrees with any sensor activation polygons (i.e. if triggering by position, and a sensor activation polygon is active, ensure that all camera trigger positions are within the sensor activation polygon).&#x20;
{% endhint %}

### Distance

This method will trigger at a specified distance interval (e.g. 10 m). Specifically, this method uses INS distance (i.e. distance as determined through GNSS and IMU). This method may perform poorly in challenging GNSS environments.&#x20;

### Following

Trigger after a different camera is triggered, with some time delay specified. Useful for staggering image recording of several cameras.&#x20;

### Interval

Trigger cameras at a user-specified time interval.&#x20;

### Passive

This method is used when cameras are triggered externally, via some other means or software.&#x20;

### Point In View

SpatialExplorer can trigger a camera based on a 3D point being in view of the camera. This feature relies on the camera being properly configured and calibrated (correct camera transforms, correct focal length, and other intrinsic properties).&#x20;

3D trigger positions can be loaded from points in a KML file. To accomplish this, first load a KML into the Project as a Geometry. Then you can load this KML as trigger positions:

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

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

### Vehicle Position

Trigger the camera when the vehicle (INS position) is near some location. Load vehicle positions from a KML, similar to the Point In View documentation shown above.&#x20;

### Wheel Sensor

This method will trigger at a specified distance interval (e.g. 10 m). This method uses odometer distance readings, from a wheel sensor, to measure traversed distance. This method is preferred to the standard, INS distance triggering method when GNSS conditions are poor.&#x20;


---

# 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/camera-settings.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.