Table of Contents

Mega-space solution

For super-large scenarios such as tourist attractions, urban blocks, and large commercial complexes covering areas exceeding hundreds of thousands of square meters or even millions of square meters, the traditional "single acquisition, single large map" model cannot meet requirements. This document introduces how to handle acquisition and usage issues in mega-space scenarios, addressing problems caused by single super-large maps such as excessive cumulative error and memory overflow.

cluste_route

Core challenges

When dealing with mega-spaces spanning millions of square meters, attempting to create a single giant map faces multiple technical obstacles:

  1. Acquisition difficulties: Prolonged single acquisition causes device overheating and excessive data volume (hundreds of GB), making upload and processing extremely challenging.
  2. Cumulative error: Mapping errors accumulate with acquisition distance. On paths spanning several kilometers, even a 1% error can result in dozens of meters of deviation, which is difficult to correct.
  3. Performance bottlenecks: Loading and optimizing map data covering millions of square meters can instantly exhaust device memory.

Solution: Blocking and fusion

The standard solution for mega-space challenges is divide and conquer. Logically divide the entire large scene into multiple physically overlapping sub-regions, acquire each sub-region separately, and finally fuse and optimize all sub-regions. This enables seamless roaming through dynamic loading during runtime.

Data acquisition

You need to plan according to the mega-space data acquisition method.

  • Division principle: Divide the large scene by area, scenery, or functional zones, with each area ideally around 100,000 square meters.
  • Overlap requirement: Adjacent sub-regions require at least 200 meters of completely overlapping paths. Larger overlap areas yield better fused maps. Ensure sufficient overlap zones for fusion optimization between adjacent sub-maps.

Before acquiring data for each sub-region:

Creating mapping tasks

Viewing mapping results

After mapping completes, you can review results:

Tip

Testing localization performance

Operational strategy

Fused maps require no special processing and can be used directly as single maps.

  • GNSS-based queries: In outdoor scenarios, GNSS assists map queries, ensuring precise localization even in large maps.
  • On-demand loading: When placing content, load each sub-region's mesh individually.
  • Seamless switching:
    1. Localization algorithms run simultaneously in sub-map A and sub-map B.
    2. Content switches seamlessly in overlap areas.