> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/common-for-several-products/smart-dimensions/dimensioning-tabs.md).

# Dimensioning Tabs

There are several tabs for dimensioning elements in which you can define how elements on different Faces or in different directions should be dimensioned.

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FlyAKeAQG4BRWcSepHZmH%2F0.jpeg?alt=media)

In each tab, you can choose from different options. Some of them may vary depending on the chosen category:

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FtqlfJ00BmsmkQZgIw1ez%2F1.jpeg?alt=media)

**Horizontal Dimensions/ Vertical Dimensions/Along Element Dimensions/ Across Element Dimensions** - choose options for vertical, horizontal and diagonal dimensions

**Measure Width/Position/Length/Height** - turns ON Horizontal/Vertical/Diagonal dimensioning

**Measure** - choose to where dimension point should snap:

* Location Point - will snap to insertion point of a Family
* Location Line - will snap to location line. Available for line-based elements (Structural Framing, Pipes, etc)
* Left/Right Edge - will snap to the edges of solid body in the Family
* Reference planes - will snap to reference planes which are inside Family. Reference planes should be set to Left/Top/Center etc.

  ![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FGwqNFIvgFonYI5u43zv0%2F2.jpeg?alt=media)
* Model lines - will snap to model lines, which are inside the Family. Model lines should be perpendicular to the dimension line in the view

**Join Dimension Lines** - if OFF, each element will have its own dimension line. That's why it's usually ON, to have fewer dimension strings.

**Measure Only First & Last Element** - will skip dimensioning of intermediate elements

**Disconnect from Total Dimension Point** - will give dimension only between measured elements

**Dimension Position** - select from available options where to place the dimension:

* Left/Right/Top/Bottom - dimensions will be placed at selected side, outside of all elements, to be included in Total Measure
* By Element - dimension will be placed at nearest side
* By Measure - dimension will be placed at the position of dimensioned element

**Text Note** - enter a value for text note. Works with Text Note Settings. *(See relevant help file.)*

**Text Note Parameter** - select parameter, which should be added as a note to the dimension line. Works with Text Note Settings. *(See relevant help file.)*

**Grouping** - group dimension lines by the selected parameter 


---

# 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://docs.besmart.software/common-for-several-products/smart-dimensions/dimensioning-tabs.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.