MultiSet
Developer PortalContact UsTutorials
  • MultiSet Developer Docs
  • Getting Started
    • Changelog
    • VPS SDK : Unity Guide
    • FAQ
  • Basics
    • Maps
      • Mapping Instruction
      • Mapping Planning
      • Mapping Equipment
    • MapSet : Multiple Maps
      • Merging Maps without Overlap
        • Extend a MapSet
      • Merging Maps with Overlap
      • Adjust Map Transformation
    • App Localization
    • Credentials
    • Analytics and Usage
    • Downloads
    • REST API Docs
    • WebXR Integration
    • Third Party Scans
      • Matterport
      • Leica Scans
    • MapFoundry
    • Georeferencing Maps
    • On-Premises Localization
  • Unity-SDK
    • Authentication
    • MultiSet package import
      • Universal 3D (Core) support
    • Sample Scenes
    • On-Cloud Localization
      • Individual Map
      • MapSet (Multiple maps)
        • Hint MapCodes
      • Pose Prior : HintPosition
    • Occlusion
    • NavMesh Navigation
  • Support
  • Native Support
    • iOS Native
    • Android Native
Powered by GitBook
On this page
  • Scanning Workflow
  • Uploading to MultiSet
  • Best Practices

Was this helpful?

  1. Basics
  2. Third Party Scans

Leica Scans

PreviousMatterportNextMapFoundry

Last updated 20 days ago

Was this helpful?

MultiSet AI’s Visual Positioning System (VPS) accepts structured .e57 point-cloud files exported from Leica’s Cyclone REGISTER 360 PLUS. By pairing Leica’s high-fidelity LiDAR capture with MultiSet’s VPS you can turn large venues into centimeter-accurate AR canvases in hours instead of days. The guide below walks you through recommended devices, capture workflow, export settings and the upload process to the MultiSet Developer Portal.

Supported Devices

  • Leica RTC360

  • Leica BLK360 G2

  • Leica BLK2GO / BLK2FLY

MultiSet parses the panoramic images and intrinsic calibration blocks embedded in a structured E57. Unstructured “raw” exports will be rejected during processing.

Scanning Workflow

1 Prerequisites

Item
Notes

Scanner & power

Fully charge two batteries; firmware ≥ 2023.1 on RTC360/BLK360.

Mobile app

Leica Cyclone FIELD 360 on iOS/Android for live QA and alignment.

Desktop software

Leica Cyclone REGISTER 360 PLUS 2023.1 or later (adds one-click structured E57 export).

2 Required Equipment

  • Sturdy tripod (3⁄8-16 UNC), quick-release clamp.

  • Target spheres / checkerboards if survey-grade alignment is needed.

  • Tablet/phone with FIELD 360 (Wi-Fi 6 preferred for RTC360’s onboard hotspot).

3 Prepare the Environment

  1. Declutter walkways and remove moving objects if possible.

  2. Set low-resolution LiDAR when AR is the only deliverable; high-res mode multiplies file size with no VPS benefit.

  3. Turn off HDR on BLK360; use LDR panoramas to avoid over-saturated textures.

4 Capture the Space

  • RTC360 / BLK360 – place the scanner roughly every 5–7 m; 30 % overlap between setups.

  • BLK2GO – maintain slow walking speed (< 1 m/s) and follow loop-closure paths.

  • Monitor FIELD 360: green spheres = complete scan, yellow = alignment pending.

5 Register & Clean

  1. Import data into Cyclone REGISTER 360 PLUS.

  2. Run Auto-Cloud > Cloud for coarse alignment; refine with target-based or visual alignment as needed

  3. Crop excess ceiling sky boxes or outdoor noise for faster VPS processing.

6 Export Structured E57

  • Choose “Export > E57 (Structured)” and tick Include Panoramas.

  • Leave “Compatibility Mode” unchecked unless another software requires it; it downsamples points.

Expect ~1 GB per 1 k sq ft at low-res settings. The MultiSet portal currently accepts files up to 20 GB for free plan.


Uploading to MultiSet

  • Create Map → Select Leica → Upload.

  • Drag-and-drop the zip of E57 file.

  • Please allow up to one hour to receive an email notification once your scan is complete

Best Practices

Do
Avoid

Keep the scanner out of mirrors & windows.

Walking within 2 m of shiny cars or glass facades (causes ghost points).

Use low-res LiDAR + LDR pano for VPS-only jobs.

High-res HDR if final AR textures aren’t required (adds 3–4× size).

Validate overlap in FIELD 360 before leaving the site.

Expecting Register 360 to fix large gaps automatically.

Export one file per level for multi-story buildings, then combine with MultiSet Merge tools.

A single 40 GB monolithic export.

Google Play