> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/build/measurement.md).

# Measurement

Drop a ruler into the scene and read the distance between two points, with angles if you need them.

Someone asks whether the doorway is wide enough for the crate, or how far the camera is from the wall it is about to clip. Eyeballing it in a viewport is guesswork. Drop a ruler between the two points and read the number.

Measurements shipped in release 2.0.72.

## Place one

Open the asset library and find **Measurements**. **Add Measurement** places a ruler in the scene, by click or by drag, the same way a populator or a road goes in.

## What it tells you

The ruler carries ticks in metres and centimetres, and labels the distance between its two endpoints along with their separation on each axis, all to two decimal places.

**Measurement Options** adds direction angles. Three switches, **X Angle**, **Y Angle** and **Z Angle**, each drawing an arc for that axis. Turn on the one you need rather than all three; three arcs on one ruler is harder to read than the number you were after.

## Moving the ends

Selecting the ruler itself moves both endpoints together, so the measurement keeps its length and orientation while you reposition it.

To change what is being measured, move one end at a time. The contextual toolbar carries **Select Start** and **Select End**, and with one endpoint selected it behaves like any other object: drag it, snap it to a surface, or parent it to something.

That last part is the useful bit. **Parent an endpoint to an object and the measurement follows it.** Pin one end to a wall and the other to a crate, and the distance updates as you move the crate, so you can push it until the number says what you need rather than nudging and re-measuring.

The endpoint gizmos are global only; the local and smart modes on [Transform](/build/transform.md) do not apply to them. Their hit zones are twice the size of the visible dot, which matters when a ruler is small on screen.

![Adding a measurement and placing both ends, the distance and the coordinates updating as the second point moves](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-75b75ad127f062aedcb2263ee82cc92688444286%2Fmeasurement-in-scene-02.gif?alt=media)

![A measurement in a scene: a dashed ruler between two points, labelled 2.08 m, with the XYZ coordinates of each end shown beside it](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-0571d805ea0b916b337b84a014d076f4321b39f1%2Fmeasurement-in-scene-01.png?alt=media)

## Where they live

A new measurement arrives one metre long, laid along X, with its two endpoints named **Start** and **End** and the ruler itself named Measurement 1, Measurement 2 and so on.

They are saved with the scene, so they are still there when you come back, and they appear in the [Scene Outliner](/build/scene-outliner.md) like anything else. The code calls them editor-only.

## Related

* [Transform](/build/transform.md) for the gizmo and snapping
* [Working with objects](/build/working-with-objects.md) for parenting, which is how an endpoint follows an object
* [Populators](/build/populators.md), placed from the same library


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/build/measurement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.