> 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/concrete-u-girder-bridge-workflow/reports-cug/geometrical-criteria-vertical-clearance-cug.md).

# Geometric Criteria (Vertical Clearance) \[CUG]

## Vertical Clearance

**Component 1:** Specify the first structural component for which the vertical clearance will be calculated.

**Component 2:** Specify the second structural component to check the clearance between Component 1 and Component 2.

**Clearance Limit:** Specify the minimum required vertical clearance distance between the two components.

**Description:** Provide a text description for the clearance check.

**Minimum Distance:** This parameter displays the calculated minimum distance between the two components (read-only).

## Boundary

**Alignment:** Specify the alignment to define the reference coordinate system for the clearance calculation.

**Station:** Specify the station along the alignment where the clearance check will be performed.

**Width:** Specify the width of the boundary region within which the clearance is evaluated.

**Depth:** Specify the depth of the boundary region perpendicular to the width.


---

# 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/concrete-u-girder-bridge-workflow/reports-cug/geometrical-criteria-vertical-clearance-cug.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.