Mega mapping failure troubleshooting guide

During the mapping process, failures such as upload failures or generation failures may occur, mostly due to poor-quality collected data. Strictly adhere to the requirements in the data collection documentation during data collection to avoid issues caused by incorrect device parameters or improper route planning. If you have followed the collection documentation carefully but still encounter problems during the mapping process, please refer to this document for further troubleshooting.

What is the normal mapping process

The mapping process of EasyAR Mega Block mainly consists of several steps: data upload, trajectory generation, localization map, and dense map generation.

1. Data upload

   • GoPro-collected panoramic data
   • EMP data collected by phone

   The files collected by GoPro are relatively large (1 hour of video, approximately 30 GB in size), so the upload duration may vary depending on the network conditions. After successful upload, you can view uploaded files in the operation bar of the Mega Block mapping task. You need to verify whether the filenames and quantities match your local files. If the data is consistent, the upload is correct. After successful upload, the mapping status may display queued or generating, and you can also play .LRV format videos online.

   

   Note

   During the data upload process, the uploaded data will also be validated. This process is relatively fast. If no errors are reported, you can ignore this process.

2. Trajectory generation

   The EasyAR Mega Block mapping system needs to recover the trajectory during data collection, which may take some time. If the mapping process is normal, you can view the mapping trajectory in Block mapping after trajectory generation or mapping completion.

   • GoPro-collected panoramic data
   • EMP data collected by phone

   To help users confirm whether the collected trajectory is normal, EasyAR provides a trajectory preview function. For all completed GoPro data mapping, the preview spatial trajectory function is provided. You can check for any missing data based on the spatial trajectory.

   

   For outdoor-collected data, EasyAR also provides the preview GPS trajectory function.

   

3. Mega Block map generation

   Due to the high computational load of Mega Block map generation, this stage takes relatively longer. After mapping is completed, the task status will display task completed. You can also view the mapping report provided by EasyAR.

   • GoPro-collected panoramic data
   • EMP data collected by phone

   

GoPro mapping failure phenomenon and handling solution

Data upload failed

During the data upload phase, two issues may arise due to network or data issues: if your network is poor, you may encounter problems such as stuck upload progress or network interruptions; if the data you collected is problematic, file verification will fail.

File upload failed

Typical symptoms: Upload progress gets stuck, rolls back, or prompts a network interruption.
Why it happens: This is usually due to poor network conditions, which you can address yourself.

1. First, try refreshing the page or logging in again (to avoid prolonged login sessions).

2. Click Re-upload: Reselect the data folder and start uploading all files from the beginning (suitable for failures early in the upload process).

3. Click Continue upload: Select the data folder from the last failed upload (do not modify files in the folder), and resume uploading from the point of failure.

   

4. Network optimization: Keep the browser window active during upload. Do not close the browser, refresh the page, or click other menus during the upload process. Ensure a stable network connection and avoid other high-bandwidth activities.

Note

EasyAR highly recommends uploading mapping data in a stable wired or wireless network. Using mobile data is not advised, as GoPro videos are relatively large in size.

File detection failed

Typical prompts: XXX video is corrupted!, The following files detected errors: XXX, XXX filename video frame rate setting is incorrect!

Why it happens: After uploading video files, the EasyAR system performs a quick inspection to filter out unqualified data in advance, reducing your waiting time. It may be due to non-compliant collection or issues caused by SD card damage or GoPro device problems.

1. If XXX video is corrupted! or The following files detected errors: XXX appears

   • Try re-copying the file from the GoPro memory card and uploading it again.

   • Try uploading from another computer or browser.

   • The collection may have experienced abnormal shutdowns, etc. You should recollect the data.

2. If XXX filename video frame rate setting is incorrect! appears

   • Please set the correct frame rate according to the GoPro collection specifications.

Note

If refreshing the page still does not pass the detection, you should recollect the data according to EasyAR's collection specifications.

Mapping failure

If you encounter Generation failed in the Block mapping status, you can check the Mapping failure report.

1. If Check if the input file is corrupted (possibly due to video file glitches) appears, you need to check if the video file has glitches.
2. If Check if the input file is corrupted (possibly due to abnormal shutdown or TF card recording lag during shooting) [Video error time: xx s] appears, you need to check if there are any abnormalities near the error time in the video.
3. If Internal error, please provide feedback (possibly due to camera slipping, collision, rapid movement, passing through a completely dark environment, or taking an elevator during shooting) appears, it may be due to the camera slipping, colliding, or experiencing rapid movement during the collection process, the collector taking an elevator resulting in abnormal acceleration, or the collection route containing completely dark scenes.
4. If Check if the input file is corrupted appears, you need to play the collected video with a video player to check for any abnormalities.
5. If Server error, please try again later appears, please wait for a while and try mapping again.

Tip

If the mapping report shows Internal error, please provide feedback or the mapping report does not indicate any reason, please provide the mapping report to EasyAR staff.

Note

If the mapping report provides the video error time and your input consists of multiple video segments, please calculate the corresponding video error time point yourself.

Mobile phone mapping failed

Mobile phone mapping usually has a high success rate. If it fails, please check the following first:

• Whether you stayed in the same place during collection
• Whether the ambient light is sufficient
• Whether the camera is blocked

If the collection is confirmed to be correct but still fails, please provide the mapping report to EasyAR staff.

Issue feedback

If you have completed the above self-check and confirmed that the data itself has no obvious quality issues (no screen distortion, no parameter errors), but mapping still fails, please follow the standard process below to provide feedback to the EasyAR team.

Summarize the above issues and emphasize the self-check again. If mapping still fails after the self-check, proceed with the feedback.
Then describe how to provide feedback and how we will resolve it (e.g., advanced mapping, etc.).

Issue handling and feedback

After identifying the real problem, please collect information and provide feedback in the following way, so the technical team can quickly locate and fix it:

Feedback information

To help the technical team quickly locate the issue, please provide the following information:

1. Mapping report: Download the mapping report in Mega Developer Center format, which includes the task ID, error messages, etc.

   

2. Collection planning route map: Provide screenshots or videos of the collection plan to help identify the issue more quickly.

Package the above materials and send them to the EasyAR technical support contact.

Feedback handling expectations

Technicians will review the mapping report, check logs and raw data, and analyze possible causes:

• Severe collection violations (e.g., severe shaking, completely dark): requires re-collection according to specifications
• Algorithm parameter adaptation issues: we will enable advanced mapping mode, adjust cloud parameters, and attempt to regenerate the Block map for you

If conventional parameter adjustments are ineffective, the R&D team will intervene to analyze whether the data falls into a specific scenario's algorithmic blind spot (e.g., extreme weak texture) and assess whether it can be fixed through algorithm iteration.