> 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/support-lines-ex1-sig.md).

# Support Lines

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

For detailed parameter explanations, see the [Support Lines Reference](https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/bridge-geometry-sig/support-lines-sig).
{% endhint %}

**Step 1:** Click **three-dots icon** on **Bridge** cell and set a bridge alignment as **BRG1**.

![image-20240724-103914.png](https://openbrim.atlassian.net/wiki/download/attachments/2101379467/image-20240724-103914.png?api=v2)

**Step 2:** Keep the **Station, Skew Angle** and **Transverse Offset** as default.

![image-20240724-104003.png](https://openbrim.atlassian.net/wiki/download/attachments/2101379467/image-20240724-104003.png?api=v2)

<details>

<summary><strong>Quick Tip:</strong> Skew Angle</summary>

![](https://openbrim.atlassian.net/wiki/download/attachments/2278031376/image-20230302-111832.png?api=v2)

</details>

<details>

<summary><strong>Quick Tip:</strong> Skew Angle 2</summary>

![](https://openbrim.atlassian.net/wiki/download/attachments/2278031376/image-20230302-111935.png?api=v2)

</details>

<details>

<summary><strong>Quick Tip:</strong> Transverse Offset</summary>

Offset values use PGL as the reference point.

![](https://openbrim.atlassian.net/wiki/download/attachments/2278031376/Untitled%20Diagram.drawio%20\(15\)-20221025-123233.png?api=v2)

</details>

**Step 3:** Set name as **Abut1**.

![image-20240724-104039.png](https://openbrim.atlassian.net/wiki/download/attachments/2101379467/image-20240724-104039.png?api=v2)

**Step 4:** When the steps are completed, the shared screenshot displayed in the adjacent cell should be visible in the 3D view of OpenBrIM.

![](https://openbrim.atlassian.net/wiki/download/attachments/2101379467/image-20231002-150746.png?api=v2)

{% hint style="success" %}
The completed support lines are illustrated below. Please verify that you have the same model on your end by examining each view provided here. For more information on how to perform visual checks, refer to the quick tips.
{% endhint %}

<details>

<summary><strong>Quick Tip:</strong> Learn how to show Model</summary>

Click on the arrow button above the Analysis button located in the upper-left corner of the OpenBrIM screen.

![](https://openbrim.atlassian.net/wiki/download/attachments/2278031376/image-20230920-135407.png?api=v2)

Click on the Model button on the screen that opens up.

![](https://openbrim.atlassian.net/wiki/download/attachments/2278031376/image-20230920-135445.png?api=v2)

![](https://openbrim.atlassian.net/wiki/download/attachments/2101379467/image-20231002-153144.png?api=v2)

![image-20240724-104143.png](https://openbrim.atlassian.net/wiki/download/attachments/2101379467/image-20240724-104143.png?api=v2)

![image-20240724-104333.png](https://openbrim.atlassian.net/wiki/download/attachments/2101379467/image-20240724-104333.png?api=v2)

</details>

{% hint style="success" %}
To view the entire procedure explained on this page, please watch the recorded Video below.
{% endhint %}

{% embed url="<https://openbrim.atlassian.net/wiki/download/attachments/2101379467/Support%20Lines.mp4?api=v2>" %}
Support Lines
{% endembed %}


---

# 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/support-lines-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.
