View the mapping report
This article details how to view the mapping report, including the report content, viewing methods, and steps to handle mapping failures, helping users quickly identify and resolve issues.
Mapping report content
The mapping report provides detailed information, including input data details and output result statistics, to help users understand mapping quality and data completeness.
Input content
The input content for the mapping report includes the following information:
- Number of videos: The number of video files uploaded in the collection task.
- Total collection duration: The total duration of the videos, in seconds.
- Collection time: The start time of the collection task.
- Collection device firmware version: The firmware version number of the collection device.
- Mapping version: The system version number used to generate the mapping results.
Output content
The output content of the mapping report includes the following information:
- Collection route length: the total length of the route recorded during the collection process, in meters.
- GPS: whether the collection task includes GPS data.
- Dense face count: the number of mesh faces generated during the mapping process.
- Dense texture: the number of generated mesh textures.
- JobID
- BlockID: click to view detailed Block information.
- Top-down screenshot: displays a top-down view of the mapping results for quick assessment of the mapping effect.
View the mapping report
After completing the mapping task, you can view the mapping report in the following ways to understand the detailed information of the mapping results.
View the mapping report after successful mapping
After the task is successfully completed, click the Mapping report button to view the mapping-related information.
View mapping failure report
If the mapping task fails, click the
Mapping failure reportbutton to view the task information and failure reason.
Check the files yourself based on the error code 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
During the mapping process, various errors may be encountered. Below are common mapping failure error codes and their explanations, helping you quickly locate and resolve issues.
| error code | failure reason |
|---|---|
| 10x | Check if the input file is corrupted |
| 102 | Check if the input file is corrupted (possibly caused by screen tearing in the video file) |
| 103 | Check if the input file is corrupted (possibly due to abnormal shutdown, or lag during recording on the TF card) [Video error time: xxs] |
| 20x | Internal error, please provide feedback |
| 201 | Internal error, please provide feedback (possibly caused by the camera slipping, colliding, experiencing rapid displacement, passing through a completely dark environment, or elevator movement during shooting) |
| 30x | Internal error, please provide feedback |
| 40x | Internal error, please provide feedback |
| 50x | Server exception, try again later |
Related topics
- View mapping results