> 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/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/bridge-geometry-ex1-stg/bridge-alignment-ex1-stg.md).

# Bridge Alignment

This section assigns the roadway alignment to the bridge structure.

{% hint style="info" %}
**Navigation:** Bridge Geometry > Bridge Alignment

For detailed parameter explanations, see the [Bridge Alignment Reference](https://docs.openbrim.org/templates/steel-tub-girder-bridge-workflow/bridge-geometry-stg/bridge-alignment-stg).
{% endhint %}

## Steps

### Step 1: Navigate to Bridge Alignment

Navigate to **Bridge Geometry > Bridge Alignment** in the tree view.

![Bridge Alignment navigation](https://openbrim.atlassian.net/wiki/download/attachments/2169110529/image-20230216-122332.png?api=v2)

### Step 2: Set Alignment Reference

Click the **three-dot icon** on the **Alignment** cell and select the roadway alignment.

![Set alignment](https://openbrim.atlassian.net/wiki/download/attachments/2169110529/image-20230216-122637.png?api=v2)

### Step 3: Enter Bridge Name

Set the bridge name as **BRG1**.

<details>

<summary><strong>Quick Tip:</strong> Bridge Information</summary>

Additional bridge information can be entered through the **Bridge Info** tab if needed.

![Bridge info tab](https://openbrim.atlassian.net/wiki/download/attachments/2169110529/image-20230216-122906.png?api=v2)

</details>

## Verification

{% hint style="success" %}
After completing these steps, the bridge alignment is configured. Proceed to the Support Lines section.
{% endhint %}


---

# 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/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/bridge-geometry-ex1-stg/bridge-alignment-ex1-stg.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.
