Table of Contents

Mega lossless full update

Lossless full update is an advanced feature provided by EasyAR Mega to address dynamic scene changes. It allows developers to comprehensively update the entire scene using newly collected data while preserving the original coordinate system. The cloud algorithm reconstructs the spatial map based on new video data, ensuring that developed AR content positions remain unchanged for seamless updates.

Features

  • Comprehensive update: Rebuilds the entire scene using newly collected data.
  • Coordinate system preservation: Maintains the original coordinate system to prevent positional shifts of developed AR content.
Important

If partial areas are missed during full update collection, those regions will also be absent in the generated spatial map.

Applicable scenarios

  • Comprehensive environment renovation: Scenarios like complete mall refurbishment, office floor reconstruction, or exhibition hall theme overhaul.
  • Data quality optimization: Re-collecting the entire scene with higher precision to improve localization accuracy.
  • Scene expansion: Significant area extensions requiring complete remapping of the original scene.
Note

Lossless full update suits comprehensive scene-wide updates. For partial area changes, use the supplementary update feature.

Supported mapping types

  • ✅ Single-map mapping task: Supports lossless full update
  • ✅ Multi-map fusion task: Supports lossless full update
  • ❌ Mobile mapping: Does not support lossless full update (including small-scale mobile mapping tasks and object mobile mapping tasks)

Supported mapping versions

  • Version 7.6 and above

Data collection

Since lossless full update targets the entire environment, refer to: Data Collection.

Lossless full update mapping

After data collection, upload the latest video data to the designated lossless full update task to generate the updated spatial map.
For specific steps, see: Lossless Full Update Mapping.

Using updated maps for localization

Upon completion, a new spatial map is generated (Block ID remains unchanged). Developers should load the updated Block into the cloud localization library to immediately use the updated map without modifying application code or repackaging.
Loading procedures differ based on mapping versions: