Table of Contents

Mega mapping service

Spatial mapping is the core of Mega cloud services, positioned as the central hub in the entire Mega workflow. It receives captured data from the physical world and outputs digital assets required for application development.

The following diagram shows the position of spatial mapping in the entire Mega workflow:

flowchart LR

A[Data capture] --> B>Build Mega Block map] --> C[Mega localization]

Feature introduction

EasyAR Mega adopts a fully cloud-based automated processing pipeline. Developers don't need to run any complex mapping algorithms locally. By simply uploading compliant video data, the cloud cluster can automatically complete the following tasks:

  • Feature extraction: Identify key visual features in the environment (such as corners, textures).

  • Spatial reconstruction: Calculate 3D spatial coordinates of feature points to generate spatial data.

  • Loop closure detection: Automatically identify path loops to eliminate accumulated errors.

  • Georeferencing: Align local coordinate systems to the global geographic coordinate system using GNSS data.

  • Multi-map fusion: Support merging multiple independent capture areas into a complete map (for large-scale scenes).

Block mapping process

Organize mapping tasks by creating and managing mapping projects. Successful mapping generates Blocks.

flowchart LR

A[Mapping project] --> B[Mapping task] --> C[Mapping result Block]
  • Mapping project: Used to organize and manage related mapping tasks
  • Mapping task: Performs specific mapping operations
  • Block: The final product of successful mapping

Different types of mapping tasks

Depending on your scene size and capture strategy, Mega provides four types of mapping tasks. Create the appropriate task type based on your actual situation:

Regular single-map task

  • Applicable scenarios: Small to medium-sized scenes, single capture covering the entire scene
  • Typical cases: Single-floor malls, restaurants, single-floor offices, exhibition halls, parks, etc.
  • Capture device: GoPro Max 1st gen panoramic camera
  • Steps: Create a regular single-map task

Large-scale multi-map fusion task

  • Applicable scenarios: Extra-large scenes, multi-floor scenarios, interconnected multi-zone scenes
  • Typical cases: Large shopping centers (connecting floors), commercial districts (connecting indoor/outdoor), university campuses (connecting multiple buildings), etc.
  • Capture device: GoPro Max 1st gen panoramic camera
  • Steps: Create a large-scale multi-map fusion task

Small-area mobile capture task

  • Applicable scenarios: Small-scale scenes, compact spaces
  • Typical cases: Rooms, shops, exhibition booths, etc.
  • Capture device: iPhone / ARCore Android phones
  • Steps: Create a small-area mobile capture task

Object mobile capture task

  • Applicable scenarios: Single objects
  • Typical cases: Exhibits, equipment, merchandise, etc.
  • Capture device: iPhone / ARCore Android phones
  • Steps: Create an object mobile capture task

Mapping status explanation

In the Developer Center Block mapping interface, you'll see real-time status of mapping tasks. Understanding these statuses helps assess task progress:

Mapping status Description Recommended action
Under review Manual video review in progress Wait for review completion
Queued Waiting for server resources Wait for server allocation
Processing Server processing ongoing Wait for mapping completion
Completed Mapping finished View mapping results
Failed Mapping failed Troubleshoot failure

View mapping results

After mapping completes, further inspect results to confirm if they meet requirements.

Troubleshooting failed mappings

When mapping tasks fail, troubleshoot using these methods:

  • Check mapping report: View mapping report and find solutions based on report information.
  • Reference troubleshooting: Consult the Mapping failure troubleshooting guide for common solutions.
  • Contact technical support: If unresolved, contact EasyAR staff and provide the JobID from the mapping report for quick issue identification.

Next steps