> 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/concrete-bridge-examples/example-concrete-u-girder-bridge/bridge-geometry-ex1-cug/bridge-alignment-ex1-cug.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/concrete-u-girder-bridge-workflow/bridge-geometry-cug/bridge-alignment-cug).
{% endhint %}

## Steps

### Step 1: Navigate to Bridge Alignment

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

![Navigation](https://openbrim.atlassian.net/wiki/download/attachments/2258829314/image-20230823-154218.png?api=v2)

### Step 2: Create Bridge Entry

Enter the name **Bridge1** in the Name column.

### Step 3: Assign Alignment

Click the **three-dots icon** on the Alignment cell and select **ALIGNMENT1**.

![Alignment Assignment](https://openbrim.atlassian.net/wiki/download/attachments/2258829314/image-20230823-153930.png?api=v2)

<details>

<summary><strong>Quick Tip:</strong> Multiple Bridges</summary>

This approach allows for the assignment of different alignments to more than one bridge within a single project. Each row represents a bridge, and you can assign the alignment accordingly.

</details>

<details>

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

You can enter additional bridge information through the Bridge Info tab if needed.

![Bridge Info](https://openbrim.atlassian.net/wiki/download/attachments/2258829314/image-20230823-154412.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openbrim.org/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/bridge-geometry-ex1-cug/bridge-alignment-ex1-cug.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
