> 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-prestressed-i-girder-concrete-bridge-ex1-pig/bridge-geometry-ex1-pig/bridge-alignment-ex1-pig.md).
# Bridge Alignment
This section assigns a roadway alignment to each bridge in the project, allowing multiple bridges to share or have different alignments.
{% hint style="info" %}
**Navigation:** Bridge Geometry > Bridge Alignment
For detailed parameter explanations, see the [Bridge Alignment Reference](https://docs.openbrim.org/templates/precast-i-girder-bridge-workflow/bridge-geometry-pig/bridge-alignment-pig).
{% endhint %}
## Steps
### Step 1: Navigate to Bridge Alignment
Navigate to **Bridge Geometry > Bridge Alignment** in the tree view.
### Step 2: Assign Alignment
Click the **three-dots icon** on the alignment cell and select **"Alignment1"** from the dropdown.
### Step 3: Set Bridge Name
Enter **Bridge1** as the bridge name.
This approach allows different alignments to be assigned to multiple bridges within one project. Each row represents a bridge, and you can assign the appropriate alignment accordingly.
Quick Tip: Bridge Information
You can enter additional bridge information through the **Bridge Info** tab if needed. This includes project details, owner information, and other metadata.
## Verification
{% hint style="success" %}
After completing these steps, your Bridge Alignment should match the view shown below. You can now 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/concrete-bridge-examples/example-prestressed-i-girder-concrete-bridge-ex1-pig/bridge-geometry-ex1-pig/bridge-alignment-ex1-pig.md?ask=&goal=
```
`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.