> 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/templates/steel-i-girder-bridge-workflow/loading-sig/loads-sig/wind-load-sig/wind-load-on-live-load-sig/lane-position-sig.md).

# Lane Position \[SIG]

To define wind loads for live loads, several parameters must be established, including lane positions. These lane positions will be utilized in the sections for **WL AASHTO** and **WL Custom**. This section allows users to specify the relevant lane positions.

## Geometry

Here, the user can specify the center line of the lane, which can then be utilized in the Wind on Live Load AASHTO or Wind on Live Load Custom sections.

**Bridge:** Select the bridge.

**Start Station:** Specify the start station along the PGL.

**End Station:** Specify the end station along the PGL.

**Transverse Offset:** Use this parameter to define the centerline of the lane, consider 0 as the PGL location.

![image-20240923-101905.png](https://openbrim.atlassian.net/wiki/download/attachments/2125299759/image-20240923-101905.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/templates/steel-i-girder-bridge-workflow/loading-sig/loads-sig/wind-load-sig/wind-load-on-live-load-sig/lane-position-sig.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.