MultiSet
Developer PortalContact UsTutorials
  • MultiSet Developer Docs
  • Getting Started
    • Changelog
    • MultiSet Unity SDK
      • Universal 3D (Core) support
    • 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
    • ModelSet: Object Anchoring
      • How to Create a ModelSet
    • App Localization
    • Credentials
    • Analytics and Usage
    • Downloads
    • REST API Docs
    • WebXR Integration
    • Third Party Scans
      • Matterport
      • Leica Scans
    • MapFoundry
    • Georeferencing Maps
      • How to Align Scans
      • Outdoor-Indoor Transitions with Multiset
    • On-Premises Localization
    • Support
  • Unity-SDK
    • Authentication
    • Sample Scenes
      • Localization
      • Single Frame Localization
      • ModelSet Tracking
      • Navigation
      • Training
    • On-Cloud Localization
      • Individual Map
      • MapSet (Multiple maps)
        • Hint MapCodes
      • Pose Prior : HintPosition
      • GeoHint in Localization
    • Occlusion
    • NavMesh Navigation
    • Multiplayer AR
    • Building Steps
    • API Reference
      • MultisetSdkManager
      • MapLocalizationManager
      • SingleFrameLocalizationManager
      • ModelSetTrackingManager
      • MapMeshHandler
      • ToastManager
  • MultiSet-Quest-SDK
    • Installation Guide
    • Map Mesh Downloader
    • Authentication
    • Sample Scenes
      • Single Frame Localization
  • Native Support
    • iOS Native
    • Android Native
  • MultiSet App
    • Content Space
Powered by GitBook
On this page
  1. Basics

Georeferencing Maps

PreviousMapFoundryNextHow to Align Scans

Last updated 1 month ago

Was this helpful?

CtrlK
  • Benefits of Using HintPosition
  • Setting Up Geo-Referenced Maps

Was this helpful?

The MultiSet Visual Positioning System (VPS) now supports the use of geolocation data as an external prior to enhance localization performance. This feature, called GeoHint, allows you to provide approximate GPS readings to the localization query, which helps narrow down the search space and improves the speed and accuracy of pose estimation.

By geo-referencing your 3D scans with WGS84 coordinates, you can leverage device GPS and other sensors to provide initial position estimates that significantly reduce the computational load during localization.

Benefits of Using HintPosition

  • Improved Performance: Reduces search space and computational requirements

  • Faster Localization: Achieves quicker initial positioning by focusing on relevant areas

  • Higher Accuracy: Resolves potential ambiguities in visually similar environments

  • Seamless Transitions: Enables smooth transitions between different mapped areas

  • Reduced Resource Usage: Lower memory and processing requirements on devices

Setting Up Geo-Referenced Maps

To use the GeoHint field in Localization API's effectively, you need to establish a proper geo-reference for your MultiSet maps. This involves:

  1. Recording the exact WGS84 coordinates (latitude, longitude, altitude) of your map's origin point

  2. Documenting the compass heading to establish the orientation relative to true north

  3. Configuring these values in your MultiSet Developer Portal

To achieve accurate conversions at the centimetre level, ensure that you enter at least 6 decimal places for latitude and longitude.