> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/cadd/sectioncallout-cadd.md).

# Section Callout

A **Section Callout** is the symbol that marks where a section is taken on one drawing and refers to where the section view is shown on another drawing — the conventional `A` / `A` pair, `B` / `B`, etc. Place it on a plan or elevation drawing at the location of the cut, with text identifying the section and the sheet where it's drawn.

## Content

**Text Top:** The text shown in the upper half of the callout circle. Conventionally the section letter (`A`, `B`, `C`, ...).

**Text Bottom:** The text shown in the lower half. Conventionally the sheet number where the section is drawn (`S-3`, `12`, etc.).

**Text Size:** Font size in real units.

## Geometry

**Diameter:** Diameter of the callout circle in real units. Default 0.625" (a typical bridge-sheet section bubble size at 1"=10' scale).

**Tail Type:** Whether the callout's tail points one direction (`Single`) or two (`Double` — typical when a section line crosses a complex feature with cuts taken on both sides).

**Opposite Direction:** When true, the callout's arrow points opposite to its tail — useful when the cut direction is opposite to the natural reading direction of the bubble's text.

## Style

**Color / Thickness / Level:** Standard styling.

## Notes

A complete section callout pair consists of two bubbles connected by a line (the cut line, with arrows at each end indicating the view direction), or two separate bubbles at each end of a section line. Most projects standardize on one convention.

For sections taken at fixed alignment stations, place the callout on the plan at the station, label as `<letter>` over `<sheet>`, and add a Station Offset annotation nearby if the station number itself needs to be on the plan.


---

# 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.openbrim.org/templates/cadd/sectioncallout-cadd.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.