> 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/dimensionslope-cadd.md).

# Slope Dimension

A **Slope Dimension** labels the grade between two points. Use it for profile-grade callouts (the longitudinal grade of a bridge), cross-slope callouts on deck plans, slope of approach roadway, and ramp grades.

Pick two points, and the dimension shows the slope between them in your chosen format.

## Format

**Slope Format:** How the slope is shown:

* **Percentage** — `2.5%` (typical for highway profile grades).
* **Ratio** — `1:50` (typical for embankment slopes, drainage slopes).
* **Rise per Run** — `1/4" per 12"` or `2 mm per m` (typical for cross slope on bridge decks).

**Show Direction:** Whether to draw a small arrow indicating the direction of fall. Default on. Useful for cross-slope callouts where the direction (toward gutter, toward median) needs to be visually clear.

## Text and units

**Label:** Override text.

**Prefix:** Text before the value.

**Suffix:** Text after the value.

**Precision:** Number of decimal places. 2 is typical for percentage; 0–1 for ratios.

## Typography

**Text Height:** Text size in real units.

**Font Family / Font Weight / Font Style:** Font controls.

## Notes

For profile grade callouts on bridge elevation drawings, percentage format is conventional (`+2.5%`, `-1.8%`). For cross slope on deck plans, rise-per-run format is more readable (`1/4" per 12"`, `0.02 m/m`). For embankment and drainage slopes, ratio format is conventional (`1:50`, `1:3`).

The slope is computed from the two snapped points' coordinates — vertical rise over horizontal run. If you change the profile grade by moving a pier or adjusting vertical curve parameters, the slope dimension updates.


---

# 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/dimensionslope-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.