> For the complete documentation index, see [llms.txt](https://multiset.gitbook.io/multiset/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://multiset.gitbook.io/multiset/basics/maps/output-asset.md).

# Output Asset

## Overview

Localization runs on a map's **feature data**, which stays inside the platform and is never downloaded. Alongside it, processing produces **output assets**: visual representations of the same space that you can preview in the Developer Portal, download, and load into your app, engine, or BIM tool.

There are three asset types:

| Asset                                                                      | Formats                                                                                                 | Typical use                                                                                        |
| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [**Mesh**](/multiset/basics/maps/output-asset/mesh.md)                     | `.glb` in two variants: **raw** (untextured geometry) and **textured**                                  | Occlusion, collision and NavMesh, content placement in the Unity Editor, BIM and analytics exports |
| [**Gaussian Splat**](/multiset/basics/maps/output-asset/gaussian-splat.md) | `.ply` (raw) and `.spz` (compressed)                                                                    | Photoreal preview and measurement, web and mobile splat viewers                                    |
| [**Panoramas**](/multiset/basics/maps/output-asset/360-virtual-tour.md)    | Equirectangular panorama images, one per capture point, with position, orientation, and neighbour links | 360° Virtual Tour, remote walkthroughs, comparing a space across map versions                      |

All assets of a map share one coordinate frame: the map's local frame, with the origin at `(0, 0, 0)`, `+Y` up, and metric scale. A VPS query returns poses in that same frame, so content aligned to any of these assets lands in the right place at runtime. See [Coordinate Systems](/multiset/basics/localization/coordinate-systems.md).

## What each input produces

| Input                                                                                              |                Mesh                |                Gaussian Splat                | Panoramas |
| -------------------------------------------------------------------------------------------------- | :--------------------------------: | :------------------------------------------: | :-------: |
| [**360 video**](/multiset/basics/third-party-scans.md) (raw `.insv` or stitched `.mp4`)            |       Yes (raw and textured)       |             Yes (`.ply`, `.spz`)             |    Yes    |
| [**Point cloud**](/multiset/basics/third-party-scans.md) (`.e57`, MatterPak)                       |       Yes (raw and textured)       |                      No                      |    Yes    |
| **MultiSet App / Unity SDK capture** (LiDAR)                                                       |       Yes (raw and textured)       |                      No                      |     No    |
| [**Gaussian Splat**](/multiset/basics/third-party-scans/gaussian-splat.md) (`.ply` + `poses.json`) | Yes (reconstructed from the splat) | Yes, re-aligned to the mesh (`.ply`, `.spz`) |     No    |

A **mesh is always produced**, whatever the input, so occlusion, physics, and editor-time content placement work the same way for every map.

**360 video** is the only input that produces the full set. One hand-held walk yields a navigable tour, a mesh, and a splat of the same space.

**Point cloud inputs** carry their own panoramic imagery, so `.e57` and MatterPak scans get a navigable tour as well as a mesh. LiDAR captures from the MultiSet App and Unity SDK have no panoramic imagery, so they produce a mesh only.

**Gaussian Splat uploads** get a reconstructed mesh plus their own splat back, with **modified coordinates**: the returned `.ply` and `.spz` are transformed into the map's coordinate frame so the splat sits exactly on the generated mesh. Render the returned file rather than the one you uploaded, otherwise your splat and your VPS poses will not line up.

{% hint style="info" %}
Panoramas are published for any input that carries 360° imagery: 360 video captures, and `.e57` or MatterPak scans with embedded panoramas. Check `hasPano` on [Map details](/multiset/basics/rest-api-docs/map-details.md) to see whether a given map has a tour.
{% endhint %}

## Where to find them

In the Developer Portal, open a map from the **Maps** list. The **Map Details** toolbar gives you each asset:

<figure><img src="/files/LBwZyUnecUGdYqjeDW8E" alt="Map Details toolbar with View Mesh, View Splat and View Pano buttons"><figcaption><p>Map Details toolbar: <strong>View Mesh</strong> for the mesh, <strong>View Splat</strong> for the Gaussian Splat, <strong>View Pano</strong> for the 360° tour.</p></figcaption></figure>

* **View Mesh** opens the mesh viewer, where the raw and textured GLB files can be downloaded.
* **View Splat** opens the splat viewer, which also hosts the [measure-to-scale tool](/multiset/basics/rest-api-docs/map-scale.md).
* **View Pano** opens the [360° Virtual Tour](/multiset/basics/maps/output-asset/360-virtual-tour.md).

Outside the portal, meshes can be pulled into the Unity Editor with the [Map Mesh Downloader](/multiset/multiset-quest-sdk/map-mesh-downloader.md), and every asset file can be fetched over REST with the [`/file`](/multiset/basics/rest-api-docs/map-operations.md) endpoint, which exchanges a storage key for a short-lived download URL.

{% hint style="success" %}
Output assets are for visualization and authoring. Replacing or editing them does not change localization accuracy, which is computed from the map's feature data. See [Map Operations](/multiset/basics/rest-api-docs/map-operations.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://multiset.gitbook.io/multiset/basics/maps/output-asset.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.