Table of Contents

Create single-map mapping task

This article details the complete workflow for single-map mapping tasks, including task creation, data upload, and mapping process explanation, helping users standardize the entire operation of single-map mapping tasks.

Create single-map task

After creating a project, click Manage to enter the mapping task management interface. Click the Single-map task button in the upper right corner, enter the task name in the pop-up dialog, select the mapping version and data format (recommended to use the latest version). After completing the form, click Confirm add to create a new single-map task.

Create single-map task

Note
  1. One mapping task corresponds to one complete data collection within the project.
  2. If data collection and upload are performed by external personnel, after creating the task, notify relevant personnel to upload data according to the specified process.

Task naming rules

Task names should be concise and follow these naming rules:

  1. If collection area names are clearly different, use the area abbreviation directly (e.g., "Changtai Plaza");
  2. If there are duplicate area names, add a number after the area abbreviation to distinguish (e.g., "Zhouzhuang-Area 1").

Data preparation

Before starting the mapping task, ensure collected spatial data meets requirements and is organized/stored according to specifications. The following details data collection equipment and file naming/storage/structure specifications.

Data collection and export

Use panoramic cameras to collect spatial data. Refer to these for device configuration and collection essentials:

Data folder naming

Each collection area requires a main folder named with the full pinyin of the province/city + the full pinyin of the scenic/commercial area name + area number. For example: shanghaiwaitan1.
Note: Folder names can only contain Chinese characters, English letters, numbers, and hyphens (-). Special characters are not allowed.

Data storage location

The main folder should be set on the local hard drive of the computer (not recommended on the system drive). Copy the collected data from the TF memory card to the main folder for organization. It is advised to check available capacity in advance before copying to ensure stable final file upload.

Data file structure specification

  • Each main directory folder must contain two subdirectories: lowres and 360.
    lowres folder: Stores LRV files generated during collection in the area.
    360 folder: Stores 360 files generated during collection in the area, with names corresponding one-to-one with LRV files.
  • Note: Unnecessary data (e.g., videos generated during practice operations, abandoned videos from incorrect operations during collection) should not be uploaded.
  • After organizing data files for a single area, the file structure should appear as shown below.
    Data upload file directory

Data file naming specification

GoProMax naming specification

  • 1 Named as: Video middle number
    Video middle number: The device automatically segments videos every 8GB during recording, so multiple video segments may be generated after collecting one area. Arrange video segments in ascending order based on the middle number (e.g., 01, 02, 03, 04 for four segments).
  • 2 Named as: Video end number
    Video end number: Normally, videos generated within the same area share the same end number.
  • Filename format: GS prefix + video middle number starting from 01 consecutively + identical video end number
  • Special case: If the battery or memory card is replaced during collection, the middle and end numbers of videos captured after resuming will differ from those before the interruption. However, they belong to the same area and should be placed under the same main folder. It is recommended to record the start time for each collection session to facilitate quick data partitioning during organization.
  • If filenames do not comply with this specification, unpredictable issues may occur during mapping. Even if mapping succeeds, the data may be unusable.

Upload data

Click Upload data, select corresponding options in the pop-up window. See below for specific option descriptions:

Single-map upload data

Data location

Depending on the data source and storage method, you can choose any of the following methods to upload data:

  • New local data
  • Mapping with uploaded data
  • Aliyunpan link

Collect data

Click Select, choose the main data directory folder (refer to the specific mapping data file structure below), then click Upload.
Upload new local data

EIF data

  • EIF data is specialized test data in Mega for remote debugging and simulated positioning. It verifies Mega effects remotely and supports simulated positioning during remote development, collected via specified tools. For detailed collection methods, refer to EIF data collection guide.
  • In the upload data pop-up, EIF data is non-mandatory. Later, supplemental EIF data upload is supported.
  • Note: For EIF data collected via the Mega Toolbox mobile app, ensure correspondence between EIF data and mapping video data. For example, if mapping data is from Metro City 1st floor, the uploaded EIF data should also be from Metro City 1st floor.

Upload region

Select the nearest location based on the operator’s location.

Confirm upload

  • After clicking the Confirm upload button, the upload progress and status will display in the list.
  • During upload, keep the computer powered on and the network stable. Do not close the browser, refresh the page, or click other menus, otherwise the upload will be interrupted and require restarting.

Start mapping

After upload completes, the task automatically enters Under review, as shown below.

Mapping task under review

Once approved, the task automatically enters the mapping process, showing status as Queued or Generating, as shown below. Wait patiently for mapping to complete.

Mapping task generating

Auxiliary functions

The following functions help manage and operate mapping tasks more efficiently:

View uploaded files

Used to check if uploaded mapping files are complete, avoiding mapping failures due to missing files.

  1. Click the View uploaded files button to see all uploaded files in a pop-up. Confirm files are fully uploaded.

    View uploaded files

  2. Click any LRV file to preview video content online, ensuring data quality meets requirements.

    View uploaded files

Generate pretrack

Before mapping results are generated, click the Generate pretrack button to create a pretrack. Preview the pretrack diagram to verify if the actual collection path matches the planned route. Compare the route plan with the track shape to ensure full coverage without omissions. If inconsistencies are found, stop mapping immediately, then re-collect or supplement data before re-uploading.

Generate pretrack

Preview pretrack

After generating the pretrack, click the Preview pretrack button to view the track diagram. If mapping is complete, click Preview track directly to see the final trajectory.

Preview pretrack

Upload EIF

EIF data is specialized test data in Mega for remote debugging and simulated positioning. It verifies Mega effects remotely and supports simulated positioning during remote development, collected via specified tools. For detailed collection methods, refer to EIF data collection guide.

Steps to upload EIF:

  1. Click the Upload EIF button.

    Upload EIF

  2. Select the EIF data directory folder, then click Confirm upload.

    Upload EIF

View uploaded data:

After uploading, click View uploaded files to see EIF files in the pop-up. Supports Download and Delete operations.

View uploaded EIF data

Stop mapping

Before task completion, if incorrect data is uploaded or the track diagram mismatches reality, click Stop mapping. Confirm in the secondary pop-up to halt mapping.

Stop mapping

Delete task

If a mapping task fails or is no longer needed, click Delete task. Click Delete in the secondary pop-up to remove it.

Delete task

Confirm mapping results

After a task enters the mapping process, check Task status to determine completion. Statuses Task completed or Generation failed indicate the mapping task has ended.

Mapping task completed

Mapping success

When status shows Task completed, mapping succeeded and results are generated. Further inspect results to verify they meet expectations.
View mapping results:

Mapping failure

When status shows Generation failed, mapping failed. Troubleshoot as follows:

  • View mapping report: View mapping report and follow solutions in the report.
  • Refer to 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 resolution.