Mega mapping failure troubleshooting guide

During the mapping process, failures such as upload failures or generation failures may occur. Most issues stem from poor quality of collected data. Strictly adhering to the requirements in the data acquisition documentation during data collection can prevent problems caused by incorrect device parameters or improper route planning. If you have followed the acquisition documentation strictly but still encounter issues during mapping, please refer to this document for further troubleshooting.

What is the normal mapping process

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

1. Data upload

   • GoPro collected panoramic data
   • Phone-collected EMP data

   Files collected by GoPro are relatively large (1 hour video, approximately 30 GB). Therefore, depending on network conditions, the upload duration may vary. After successful upload, you can view uploaded files in the operation column of the Mega Block mapping task. Verify that filenames and quantities match your local files. If data is consistent, the upload is correct. After successful upload, the mapping status may show queuing or generating. You can also play .LRV format videos online.

   

   Note

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

2. Trajectory generation

   The 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
   • Phone-collected EMP data

   To help users confirm whether the collected trajectory is normal, EasyAR provides trajectory preview functionality. For all GoPro data with completed mapping, the preview spatial trajectory function is available. You can check for 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 in Mega Block map generation, this stage takes relatively longer. After mapping completion, the task status will show task completed. You can also view the mapping report provided by EasyAR.

   • GoPro collected panoramic data
   • Phone-collected EMP data

   

GoPro mapping failure phenomena and solutions

Data upload failure

During data upload, two issues may occur due to network or data issues: If your network is poor, you may encounter stuck upload progress or network interruptions; If your collected data has problems, file detection will fail.

File upload failure

Typical manifestations: Upload progress stuck, rolling back, or network interruption prompts.

Why it happens: This is usually due to poor network conditions, which you can address yourself.

1. First try refreshing the page or relogging (avoid long login times)

2. Click re-upload: Select the data folder again and upload all files from scratch (suitable for early-stage failures).

3. Click continue upload: Select the last failed upload folder (files within must remain unchanged) to continue from where it failed.

   

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

Note

EasyAR highly recommends uploading mapping data in a good wired or wireless network environment. Using mobile data is not recommended as GoPro videos are large.

File detection failed

Typical prompts: XXX video is corrupted!, errors detected in the following files: XXX, XXX filename video frame rate setting error!

Why it happens: After video file upload, the EasyAR system performs quick validation to filter unqualified data early, reducing your waiting time. This may be due to non-compliant collection, SD card damage, or GoPro device issues.

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

   • Try re-uploading files copied from the GoPro memory card

   • Try uploading from another computer or browser

   • Collection might have experienced abnormal shutdowns; you should recollect

2. If XXX filename video frame rate setting error! appears

   • Follow the GoPro collection specifications to set the correct frame rate

Note

If refreshing the page still doesn't pass detection, you should recollect data following EasyAR's collection specifications.

Mapping failure

If you find generation failed in the Block mapping status, you can view the mapping failure report.

1. If check if input files are corrupted (possibly due to video glitches) appears, check video files for glitches.
2. If check if input files are corrupted (possibly due to abnormal shutdown or TF card recording stutter during shooting) [error time: xx s] appears, check for abnormalities near the error time.
3. If internal error, please report (possibly due to camera slipping, collision, rapid movement, passing through completely dark environments, or elevator use during shooting) appears, it might be due to camera slippage, collision, rapid movement, elevator use causing abnormal acceleration, or completely dark scenes in the collection route.
4. If check if input files are corrupted appears, play the collected video to check for abnormalities.
5. If server exception, try again later appears, wait and try mapping again later.

Tip

If internal error, please report appears in the mapping report, or if no reason is provided, please provide the mapping report to EasyAR staff.

Note

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

Phone mapping failure

Phone mapping usually has a high success rate. If it fails, first check:

• Did you stay in one place during collection?
• Is the ambient light sufficient?
• Was the camera blocked?

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

Problem feedback

If you have completed the above self-check and confirmed the data has no obvious quality issues (no glitches, no parameter errors), but mapping still fails, follow this standard process to report to the EasyAR team.

Problem handling and feedback

After identifying the real issue, collect and provide information as follows to help the technical team quickly locate and resolve it:

Feedback information

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

1. Mapping report: Download the mapping report in Mega development center format, containing task ID, error messages, etc.

   

2. Collection route plan: Provide screenshots or videos of the planned route for faster problem location.

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

Feedback handling expectation

Technical staff will review logs and raw data based on the mapping report to analyze possible causes:

• Severe collection violations (e.g., severe shaking, complete darkness): Need to recollect 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 fail, the R&D team will analyze whether the data represents an algorithmic blind spot (e.g., extreme weak textures) and evaluate if it can be resolved through algorithm iteration.