> 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/superstructure-attachments-ex1-stg/roadway-ex1-stg.md).

# Roadway

This section defines roadway parameters for influence surface-based live load analysis.

{% hint style="info" %}
**Navigation:** Superstructure Attachments > Roadway

For detailed parameter explanations, see the [Roadway Reference](https://docs.openbrim.org/templates/steel-tub-girder-bridge-workflow/superstructure-attachments-stg/roadway-stg).
{% endhint %}

## Steps

### Step 1: Navigate to Roadway

Navigate to **Superstructure Attachments > Roadway** in the tree view.

![Roadway navigation](https://openbrim.atlassian.net/wiki/download/attachments/2169274421/image-20230221-130833.png?api=v2)

### Step 2: Assign Bridge

Click the **three-dots icon** on the **Bridge** cell and select **BRG1**.

### Step 3: Define Roadway Dimensions

Click the **three-dots icon** on **Roadway Dimensions** and select **Edit**.

![Roadway Dimensions](https://openbrim.atlassian.net/wiki/download/attachments/2169274421/image-20230221-131220.png?api=v2)

### Step 4: Enter Station and Width Data

Enter the start and end stations with left and right widths:

| Station (ft) | Left Width (in) | Right Width (in) |
| ------------ | --------------- | ---------------- |
| 0            | 216             | 216              |
| 520          | 216             | 216              |

![Station and Width Data](https://openbrim.atlassian.net/wiki/download/attachments/2169274421/image-20230221-131544.png?api=v2)

### Step 5: Configure Lane Parameters (Optional)

Navigate to the **Roadway** tab to adjust lane dimensions and asphalt thickness if needed.

| Parameter         | Value   |
| ----------------- | ------- |
| Lane Width        | 12 ft   |
| Shoulder Width    | 20 ft   |
| Asphalt Thickness | 0.75 in |
| Number of Lanes   | 2       |

![Roadway Tab](https://openbrim.atlassian.net/wiki/download/attachments/2169274421/image-20230221-132121.png?api=v2)

<details>

<summary><strong>Quick Tip:</strong> Station-Dependent Dimensions</summary>

Roadway dimensions can vary along the bridge length. Use the spreadsheet to define different widths at each station.

![Station Dimensions](https://openbrim.atlassian.net/wiki/download/attachments/2169274421/image-20230221-133420.png?api=v2)

![Dimension Variation](https://openbrim.atlassian.net/wiki/download/attachments/2169274421/image-20230221-133509.png?api=v2)

</details>

## Verification

{% hint style="success" %}
The completed roadway configuration is shown below.
{% endhint %}

![Completed Roadway](https://openbrim.atlassian.net/wiki/download/attachments/2169274421/image-20230221-133836.png?api=v2)


---

# 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/superstructure-attachments-ex1-stg/roadway-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.