> 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/windows/project/rover/cameras/camera-processing-settings.md).

# Camera Processing Settings

The Processing tab allows for adjustment of the images used for colorization:

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

It is advisable to **Use Intervals** (bottom right) which enables only imagery recorded within a processing interval. You can also disable images manually by unselecting them with the **checkbox** next to the filename.&#x20;

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

{% hint style="info" %}
Colorization time can be reduced by disabling images that won't be needed for colorization. This is especially true when colorizing with depth maps, as one depth map must be created for every enabled image, which can add considerable processing time with large data sets. It's also recommended to use intervals to deliberately select which images to use for during camera calibration.&#x20;
{% endhint %}


---

# 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/windows/project/rover/cameras/camera-processing-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.