# Mapping Instruction

Follow these techniques to capture high-quality maps with the MultiSet Mapping App. Accurate scans produce faster localization, better accuracy, and lower drift, the foundation of every reliable AR experience.

{% hint style="success" %}
The MultiSet Mapping App currently supports iPhones and iPads equipped with a LiDAR sensor.
{% endhint %}

### 1. Ideal distance between you and the surface to map

Maintain a capture distance of **1–5 meters** between the device and the surface being mapped. If the maximum distance is not sufficient, move closer or reposition to a different vantage point. Too close loses context; too far loses feature detail.

<div><figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-fa346ef1f776a5a0bafb3d9cdfcc8df26a9b4431%2Fmapping-1-good-distance.svg?alt=media" alt="Correct capture range of 1-5 meters"><figcaption><p>Correct range</p></figcaption></figure> <figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-d230ab903357519f882a8541532b6d630825a683%2Fmapping-1-too-far.svg?alt=media" alt="Too far from surface, weak features"><figcaption><p>Too far — weak features</p></figcaption></figure></div>

### 2. Avoid capturing the same area from the same viewpoint

Repeating the same area from identical viewpoints in a single session does **not** improve accuracy. Instead, capture the same surface from multiple different angles and distances — this gives the system the multi-perspective data it needs to reconstruct 3D geometry reliably.

<div><figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-06985ebbc6add36ebf498600c37cb892ea065388%2Fmapping-2-multiple-viewpoints.svg?alt=media" alt="Capture from multiple viewpoints"><figcaption><p>Multiple viewpoints</p></figcaption></figure> <figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-7baf7ed97b7df5b818ff9eb10ade3898229ba227%2Fmapping-2-same-viewpoint.svg?alt=media" alt="Same viewpoint repeated adds no value"><figcaption><p>Same viewpoint repeated</p></figcaption></figure></div>

### 3. Avoid rapid movements — maintain a steady mapping speed

Rapid or jerky movements break frame-to-frame feature tracking, causing gaps and position tracking loss in the map. Move at a slow, **continuous and consistent pace**. If the on-device mesh becomes patchy or unstable, slow down and reorient toward previously scanned features.

<div><figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-59416a27feafb41f4e0c5d160aa09681055d3002%2Fmapping-3-steady-pace.svg?alt=media" alt="Steady pace maintains frame overlap"><figcaption><p>Steady pace</p></figcaption></figure> <figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-542689a6c7c814ab42698c2f3395ad9d4387fa05%2Fmapping-3-jerky-movement.svg?alt=media" alt="Rapid jerky movement causes tracking loss"><figcaption><p>Rapid / jerky movement</p></figcaption></figure></div>

### 4. Map in landscape mode — capture floor and ceiling if required

Landscape mode captures a wider field of view and more environmental features per frame. However, it may miss the floor and ceiling in a standard sweep — if those surfaces need to be localized, **tilt the device up and down while moving** to include them in separate passes.

<div><figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-8eb114d6fd4aebc387e5d94dcda489c8eb685eaa%2Fmapping-4-landscape.svg?alt=media" alt="Landscape mode gives wider field of view"><figcaption><p>Landscape recommended</p></figcaption></figure> <figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-c90835e9861d430f5455b3ee1a975e30ac572213%2Fmapping-4-tilt-ceiling.svg?alt=media" alt="Tilt up to capture ceiling"><figcaption><p>Tilt up for ceiling</p></figcaption></figure> <figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-51070220cc7139c8226a3b8124c4e218a37c7f40%2Fmapping-4-tilt-floor.svg?alt=media" alt="Tilt down to capture floor"><figcaption><p>Tilt down for floor</p></figcaption></figure></div>

### 5. Map corridors from both directions

Long corridors are one of the most challenging localization environments. Scanning from only one end results in repetitive, symmetric visual features that are hard to distinguish. **Capture the same corridor walking in both directions** — this doubles viewpoint diversity and dramatically improves localization accuracy and stability along the full length.

<div><figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-35a09b1f565bb6902f51d217f111e12ae9f3ab9d%2Fmapping-5-both-directions.svg?alt=media" alt="Scan corridor in both directions"><figcaption><p>Both directions</p></figcaption></figure> <figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-cdcb01c62cccc60cece8ac1feb4bc187d50ac1f5%2Fmapping-5-single-direction.svg?alt=media" alt="Single direction results in poor accuracy"><figcaption><p>Single direction only</p></figcaption></figure></div>

### 6. Ensure sufficient overlap between scan sessions

When a site requires multiple scan sessions, each new scan must **share visible features** with the previous session. Overlap at boundaries, doorways, and transitions connects multiple scans into a single coherent 3D map. Isolated scans that share no visible features cannot be merged.

<div><figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-70a398783ba9172ac48620a11398e7c0412d0dee%2Fmapping-6-overlap-good.svg?alt=media" alt="Overlapping scans merge cleanly"><figcaption><p>Overlapping scans merge cleanly</p></figcaption></figure> <figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-9d3b296bbedd19cd8cae844fe32e7b90058c845a%2Fmapping-6-no-overlap.svg?alt=media" alt="No overlap means scans cannot merge"><figcaption><p>No overlap — cannot merge</p></figcaption></figure></div>

### 7. Minimize problematic surfaces

Certain surface types reduce localization quality. When possible, **keep these out of the center of frame** or avoid capturing them as the primary subject. Focus on areas with distinct, stable visual features.

<figure><img src="https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-5af93ca3881898b3d75b24f1e7806a09fa3fb4fb%2Fmapping-7-surfaces-avoid.svg?alt=media" alt="Surfaces to avoid: mirrors, blank walls, glass, moving objects"><figcaption><p>Surfaces to avoid</p></figcaption></figure>

**Instead, focus on:**

* Textured walls with paint, artwork, or signage
* Furniture, shelving, and equipment
* Columns, pillars, and architectural features
* Floors with distinct patterns or markings
* Fixed machinery and structures

{% hint style="info" %}
MultiSet's AI pipeline automatically filters many dynamic elements. However, minimizing them during capture always produces a more stable and accurate map.
{% endhint %}

***

## Quick reference

A checklist to review before and during every mapping session.

| # | Technique             | Key rule                                         |
| - | --------------------- | ------------------------------------------------ |
| 1 | Capture distance      | Stay 1–5 m from the surface                      |
| 2 | Viewpoint diversity   | Vary angles; never repeat the same viewpoint     |
| 3 | Movement speed        | Slow, continuous, no sudden stops or turns       |
| 4 | Orientation           | Landscape; tilt up/down for ceiling and floor    |
| 5 | Corridors             | Scan in both directions — always                 |
| 6 | Multi-session overlap | Share visible features at every session boundary |
| 7 | Surfaces to avoid     | Mirrors, glass, blank walls, moving objects      |

{% embed url="<https://youtu.be/by7hcMoHO0c>" %}
