> 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-i-girder-bridge-ex1-sig/bridge-geometry-ex1-sig.md).

# 2. Bridge Geometry

This section defines the geometric layout of the bridge, including alignments, support locations, and girder positions.

{% hint style="info" %}
Complete these definitions in order. Each subsequent step depends on the previous definitions.
{% endhint %}

## Geometry Definitions

| Definition                                                                                                                                      | Description                                         |
| ----------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| [Roadway Alignment](/examples/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/bridge-geometry-ex1-sig/roadway-alignment-ex1-sig.md) | Horizontal and vertical alignment of the roadway    |
| [Bridge Alignment](/examples/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/bridge-geometry-ex1-sig/bridge-alignment-ex1-sig.md)   | Bridge centerline referencing the roadway alignment |
| [Support Lines](/examples/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/bridge-geometry-ex1-sig/support-lines-ex1-sig.md)         | Pier and abutment locations along the alignment     |
| [Insertion Point](/examples/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/bridge-geometry-ex1-sig/insertion-point-ex1-sig.md)     | Reference points for girder positioning             |
| [Girder Layout](/examples/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/bridge-geometry-ex1-sig/girder-layout-ex1-sig.md)         | Lateral spacing and arrangement of girders          |

## Geometry Parameters for This Example

| Parameter               | Value                       |
| ----------------------- | --------------------------- |
| Span Configuration      | 160 ft - 210 ft - 160 ft    |
| Horizontal Curve Radius | 700 ft                      |
| Number of Girders       | 4                           |
| Girder Spacing          | Variable (curved alignment) |
| Deck Width              | 40.5 ft                     |
| Superelevation          | 5%                          |

## Workflow

1. **Roadway Alignment**: Define horizontal curve and vertical profile
2. **Bridge Alignment**: Reference the roadway alignment for the bridge centerline
3. **Support Lines**: Place 4 support lines at pier and abutment locations
4. **Insertion Points**: Define 4 insertion points with transverse offsets
5. **Girder Layout**: Create 4 girder layouts connecting the insertion points


---

# 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/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/bridge-geometry-ex1-sig.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.