> 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-tags/tagging-dimensioning-tabs-in-smart-tags-and-smart-dimensions.md). # Tagging/Dimensioning Tabs in Smart Tags & Smart Dimensions In the Configuration windows of **Smart Tags** and **Smart Dimensions**, you will find **tabs for dimensioning/tagging**. These tabs are used for typical dimensioning and tagging applications. They are in addition to the standard tabs available for each category (such as **Common Options** in Smart Tags or **Common** and **To Nearest Element** in Smart Dimensions). These include: * **Elements in View** * **Horizontal Elements, Diagonal Elements, Vertical Elements, Element Sections, and Diagonal Elements** * A few other **unique tabs** for **specific categories.** {% hint style="info" %} **The logic** covered on this page **is identical for both Smart Tags and Smart Dimensions**, so we will be using both tagging and dimensioning examples. Keep in mind that if an example refers to tagging, the same logic applies to dimensioning, and vice versa. {% endhint %} {% hint style="info" %} This page only covers which tab to use for your This page only explains which tab to use for your specific application. The settings within each tab are mostly identical and are covered in the main [**Smart Tags Configurations**](/common-for-several-products/smart-tags/smart-tags-configurations.md) page {% endhint %} In many cases, **these tabs function as additional filters** **based on the orientation of the elements**. For example, instead of dimensioning/tagging every instance of the category you are working with, you can dimension/tag only the horizontal ones. This page will provide an in-depth explanation of these tabs and how to use them. ## Elements In View Categories that are typically **point-based** elements (such as **Columns, Duct Fittings, Pipe Fittings**) have only one additional tab—**Elements In View.** The **Point Based Elements** multi-category also has only the **Elements In View** tab. Similarly, **Doors** and **Windows**—despite being limited to specific host categories—also have just this one tab.

For all these point-based categories, this tab is used to define main tagging/dimensioning preferences. **Using this tab**, **all instances** of the corresponding category **will be tagged or dimensioned in an active view**—unless filters are applied or there are some incorrect settings. {% hint style="info" %} This page covers only the logic of specific tabs in **Smart Dimensions** and **Smart Tags**. To learn more about the settings inside these tabs, refer to the [**Smart Tags Configurations**](/common-for-several-products/smart-tags/smart-tags-configurations.md) or [**Smart Dimensions Configurations**](broken://pages/WQbzSgoqW3CCClvjkgAx) pages. {% endhint %} ## Horizontal Elements, Vertical Elements, Diagonal Elements, Element Sections Categories that are always (such as **Walls, Pipes, Ducts, Conduits, and Cable Trays**) or typically (e.g., **Structural Framing**) line-based have these tabs: * **Horizontal Elements** * **Diagonal Elements** * **Vertical Elements** * **Element Sections** * **Diagonal Elements**. In short, each tab **filters elements based on how they are positioned** within the current view. The filtering is always **relative to the view you are in**. ### MEP System Example Let’s look at a few tagging examples. The first one is an MEP system: In the plan view, there are ducts in various positions. The **Vertical Elements** tab in the **Ducts** category will tag only the ducts that appear in a **vertical** orientation. {% hint style="info" %} This is not related to how the elements appear in 3D. Using the **Vertical Elements** tab in **Smart Tags' Ducts** category does not mean tagging riser ducts—it means tagging ducts that are **vertical in the active view**. It's always relative to the view you are in. {% endhint %}

Similarly, ducts that appear horizontal in a view will be tagged through the **Horizontal Elements** tab:

Likewise, if an element is neither horizontal nor vertical because it's rotated, it is tagged through the **Diagonal Elements** tab (highlighted in red in the image below). Elements that are perpendicular to the view plane are tagged using the **Element Sections** tab. In the image below, these are the riser ducts (highlighted in blue). We can only see their cross-section because these elements are perpendicular to the active view.

To tag this view, I'm using a configuration with two **Rules** for the **Ducts** category—one tag type for non-insulated ducts and a different type for insulated ones. All orientations are tagged except for **Element Sections**. Additionally, a filter ignores all ducts shorter than 500mm to prevent cluttering the view with excessive tags. **Mechanical Equipment** and **Duct Accessories** are also tagged, as well as **Air Terminals**, using multiple **Rules** to apply different tags for different terminal types.

This is the result:

Now, let's look at **Section S1** (already tagged). Here, we're seeing the same elements but from a different perspective. The riser ducts now appear vertical. Elements that were previously vertical are now seen as cross-sections, so they are tagged through **Element Sections**.

{% hint style="info" %} **Configuration analysis**: A slightly different configuration is used here: * The same two **Rules** for ducts—one for insulated ducts and one for non-insulated ducts—are applied, along with the same length-based filter. But this time, also using * Tags for **horizontal ducts** are placed at the **center** of the element, for **vertical ducts** at the **top**, and for **cross-section ducts** at the **bottom** with a **leader**. * **Air Terminal** tags for **diffusers** use the **Bottom** position, while tags for **grilles** utilize **Element Face Offset** to appear on the intake side. {% endhint %} ### Framing Example Let's use a different example—this time, dimensioning a wall frame. However, the same logic still applies.

For vertical studs in the **Frame Front** view, the dimension at the bottom comes from the **Vertical Elements** tab. Similarly, bottom and top plates, nogging, and the door header are horizontal elements in this view and can be dimensioned using the **Horizontal Elements** tab. This is where the dimension on the right comes from.

{% hint style="info" %} You can also see different tagging for horizontal and vertical structural members. By utilizing the **Horizontal Elements** and **Vertical Elements** tabs, different tagging preferences were applied. Vertical studs have tags on the left side of the element with a leader, while horizontal members have tags centered on each element. {% endhint %} When looking at the same frame from a different perspective, an elements' orientation can change. In the **Framing Plan Detail** view, the horizontal members from the **Frame Front** view remain horizontal. However, for what were previously vertical elements, only their cross-sections are visible. In this view, they are dimensioned using the **Element Sections** tab:

The same applies to the **Frame Side** view. Here, you can only see the cross-sections of elements that were horizontal in the **Frame Front** view, so these members are also dimensioned using the **Element Sections** tab. ## On Front Sides, On Vertical Sides, On Horizontal Sides, On Diagonal Sides The **Face Based Details** multi-category has its own unique tabs: * **On Front Sides** * **On Vertical Sides** * **On Horizontal Sides** * **On Diagonal Sides** This multi-category is used for dimensioning/tagging families that can attach (be hosted) to the faces of other elements. {% hint style="info" %} To learn more about **Face Based Elements** in Smart Tags, refer to the [**Smart Tags Configurations**](/common-for-several-products/smart-tags/smart-tags-configurations.md#list-of-categories) page. {% endhint %} These tabs in **Face Based Details** follow a similar logic to line-based element tabs. The main difference is that they filter families based on the face (surface) they are hosted on., ### Precast Example In this example, there are different elements hosted on different sides of the wall. *Grout tubes* are placed on the bottom of the panel, *top fixtures* at the top, and there are *side loops* on both sides of the panel.

When looking at the panel from the front, *grout tubes* appear to be placed on a surface that is horizontal in the current view. This is exactly what the **On Horizontal Sides** tab is used for. *Side loops* in **Elevation Front** are placed on the sides of the panel. These sides appear vertical in this view, so the **On Vertical Sides** tab is used to dimension these elements. If there were any elements on the front of the panel, the **On Front Sides** tab would be used.

{% hint style="info" %} *Top fixtures* in this example are also dimensioned through **On Horizontal Sides**, but a different **Rule** with a different dimension position and dimension type was used. {% endhint %} When switching to a view from a different perspective, elements’ orientation relative to the view also changes. For example, in **Elevation Left**, *side loops* now appear to be placed on a face (surface) that is parallel to the current view plane. In such cases, the **On Front Faces** tab is used. The surface *grout tubes* and *top fixtures* are placed on is still horizontal in this view, so these elements are still dimensioned through **On Horizontal Sides**.

--- # 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://docs.besmart.software/common-for-several-products/smart-tags/tagging-dimensioning-tabs-in-smart-tags-and-smart-dimensions.md?ask=&goal= ``` `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.