View mapping report
This article details how to view the mapping report, including report content, viewing methods, and troubleshooting steps when mapping fails, helping users quickly locate and resolve issues.
Mapping report content
The mapping report provides detailed information, including input data details and output result statistics, helping users understand mapping quality and data completeness.

Input content
The input content of the mapping report includes the following information:
- Video count: Number of video files uploaded in the collection task.
- Total collection duration: Total duration of videos in seconds.
- Collection time: Start time of the collection task.
- Collection device firmware version: Firmware version number of the collection device.
- Mapping version: System version number used to generate mapping results.
Output content
The output content of the mapping report includes the following information:
- Collection route length: Total recorded route length during collection in meters.
- GPS: Whether the collection task contains GPS data.
- Dense face count: Number of mesh faces generated during mapping.
- Dense texture: Number of generated mesh textures.
- JobID
- BlockID: Click to view Block details.
- Top-down screenshot: Displays a top view of mapping results for quick assessment.
View mapping report
After the mapping task is completed, you can view the mapping report through the following methods to understand detailed information about the mapping results.
View mapping report after successful mapping
After the task completes successfully, click the Mapping report button to view mapping-related information.

View mapping failure report
If the mapping task fails, click the
Mapping failure reportbutton to view task information and failure reasons.

Check files independently based on error codes and feedback information.
If the report does not clearly indicate the failure reason, click the
Download reportbutton, contact EasyAR staff, and provide the mapping failure report.

If no mapping report is generated, contact EasyAR staff and provide the task ID.

Mapping failure error codes
Various errors may occur during mapping. Below are common mapping failure error codes and their explanations to help quickly locate and resolve issues.
| Error code | Failure reason |
|---|---|
| 10x | Check if input files are corrupted |
| 102 | Check if input files are corrupted (possibly due to video file glitches) |
| 103 | Check if input files are corrupted (possibly due to abnormal shutdown or TF card lag during recording) 【Video error time: xxs】 |
| 20x | Internal error, please provide feedback |
| 201 | Internal error, please provide feedback (possibly caused by camera slippage, collision, rapid movement, passing through dark environments, or taking an elevator during shooting) |
| 30x | Internal error, please provide feedback |
| 40x | Internal error, please provide feedback |
| 50x | Server exception, retry later |
Related topics
- View mapping results