> 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/custom-girder-bridge-workflow/loading-cg/loads-cg/wind-load-cg/wind-load-on-live-load-cg/wl-aashto-cg.md).

# WL AASHTO \[CG]

If the user wishes to apply static wind on live load, they can utilize this option.

The line load shall be applied onto the central line of the lane position designated by the user.

In the "Wind on Live Load AASHTO" section, users can choose defined lane positions. The line load will then be applied to these positions separately. For each designated lane location, a unique result scenario will be generated. The critical envelopes of these result scenarios will be used in subsequent design procedures.

## General

**Center Lines of Lanes:** Select the lane positions defined in the previous step. For every designated lane location, a distinct result scenario will be generated, and the envelopes (critical points) of these result scenarios will be employed in subsequent design processes.

**Stage:** Choose the stage at which to apply the wind load.

**Transverse Force:** Enter the transverse component values here as per AASHTO Table 3.8.1.3-1. Default value is 0.1 klf. If the user inputs a different value, the factors listed in the table will be employed to calculate the remaining angles. For instance, if the user inputs 0.2 klf, the transverse component for a 15-degree angle will be computed as 0.2 multiplied by 0.088.

![](https://openbrim.atlassian.net/wiki/download/attachments/2226978852/image-20230317-205549.png?api=v2)

![](https://openbrim.atlassian.net/wiki/download/attachments/2226978852/image-20230816-110116.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 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/templates/custom-girder-bridge-workflow/loading-cg/loads-cg/wind-load-cg/wind-load-on-live-load-cg/wl-aashto-cg.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.