Map Scale

You can now upload 360° videos without any physical scale markers. The capture is processed into a map, and once the map is active you set its real-world scale yourself: measure something in the map whose length you know and enter that length in metres. MultiSet applies the corresponding metric scale factor so the map's geometry and stored metrics match the real world.

This is useful whenever a marker-less 360 capture needs its true scale set (or corrected) after processing.

Map scaling is available only for standalone Insta360 maps that are currently active. A map that belongs to a MapSet or a version chain cannot be scaled directly.

Where to find it

In the Developer Portal, open the map's Map Details page and click View Splat in the toolbar:

Map Details toolbar. Open View Splat.

Then click the Scaling button (top right of the Splat View) to open the measure-to-scale tool:

1. Click the two ends of something you know the real size of: a door, a window, a tile.

2. Drag the dots to line them up exactly.

3. Enter its real length in metres and confirm.

MultiSet computes the factor as scaleFactor = known length (in metres) ÷ length measured in the map. For example, a door that is 2 m in reality but measures 2.35 in the map's current units gives 2 ÷ 2.35 ≈ 0.85, scaling the map to 85%. You can also apply scaling programmatically with the API below.

Inside the Splat View, click Scaling (highlighted, top right) to open the measure-to-scale tool. Measure something of a known real length, enter its length in metres, and confirm to scale the map.

Map Scale API

Make a POST request to /v1/vps/map/{mapId}/scale with your authentication token and a single scale factor. {mapId} accepts the map id or map code.

• scaleFactor: number, required, must be greater than 0. Values below 1 shrink the map, above 1 enlarge it (e.g. 0.85 scales the map to 85% of its current size).

The operation is asynchronous: the endpoint responds immediately with 202 Accepted and sets the map to pending. The map returns to active once scaling completes, or failed if it could not be applied.

Sample Request

curl -X POST "https://api.multiset.ai/v1/vps/map/{mapId}/scale" \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{ "scaleFactor": 0.85 }'

Sample Response

{
    "mapId": "67e12d4bff7ecf561f2f8a0c",
    "scaleFactor": 0.85,
    "status": "pending"
}

Behaviour

• The map is set to status: "pending" while scaling runs, then flips to active on success or failed if it could not be applied.

• Scaling is multiplicative. Each call scales relative to the map's current size, so applying 0.85 twice results in 0.85 × 0.85.

• Requests are rejected if the map is not found, not owned by your account, not an Insta360 map, not currently active, or part of a MapSet or version chain.

Scale a Map

post

Applies a metric scale factor to a standalone, active 360 (Insta360) map. Responds immediately with 202 Accepted and sets the map to pending; the map returns to active on success or failed if the scaling could not be applied. Scaling is multiplicative and applied relative to the map's current size.

Authorizations

AuthorizationstringRequired

JWT token obtained from the authentication endpoint.

Path parameters

mapIdstringRequired

Map id or map code.

Example: MAP_740EYUJTS85Z

Body

scaleFactornumberRequired

Metric scale factor (> 0). Below 1 shrinks, above 1 enlarges.

Example: 0.85

Responses

202

Scaling accepted and running.

application/json

mapIdstringOptionalExample: 67e12d4bff7ecf561f2f8a0c

scaleFactornumberOptionalExample: 0.85

statusstringOptionalExample: pending

400

Bad Request. Invalid scale factor, or the map is not an Insta360 map, not active, or part of a MapSet / version chain.

401

Unauthorized. Invalid or expired token.

403

Forbidden. The map does not belong to your account.

404

Map not found.

502

Scaling job could not be started; the map is reverted to active.

post/vps/map/{mapId}/scale

POST /v1/vps/map/{mapId}/scale HTTP/1.1
Host: api.multiset.ai
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 20

{
  "scaleFactor": 0.85
}

{
  "mapId": "67e12d4bff7ecf561f2f8a0c",
  "scaleFactor": 0.85,
  "status": "pending"
}