# CameraSnap Reports

CameraSnap creates a report, which gives the user insight into how accurate the calibration is. 

The most comprehensive metric in the report is the **Average Pixel Offset**. This metric expresses the average of all approach distances in pixels (normally approach distance is expressed in meters). This is helpful for comparing calibrations between different data sets (with different GSDs) and different cameras. 

<figure><img src="/files/5ZKS3YO6hBpXHXr4wYL7" alt=""><figcaption><p>Average pixel offset is computed for each receptor of the Ladybug5+ camera, except for the upwards facing receptor 5. </p></figcaption></figure>

**Generally, you should try to achieve an Average Pixel Offset less than 1.00 pixels for all receptors.**

### **Match Web**

The match web displays which images shared a feature match.&#x20;

If you have issues with your calibration, apparent due to a high Average Pixel Offset or poor colorization, ensure that the match web displays ample matches between images with overlapping content:

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

In the case of a sparse match web, you may have an imagery offset issue. If imagery is stored on external storage (SD card or laptop, external to the lidar system), it's possible that indexing images with their time stamps may be offset, and images are incorrectly georeferenced in the project. Check that the imagery content generally matches the lidar content at that location.&#x20;


---

# Agent Instructions: 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:

```
GET https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/toolbars/workflow/camera-snap/camerasnap-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.