> 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.md).

# Wind Load \[SIG]

Wind loads on both bridge elements and vehicular live loads can be calculated and analyzed using OpenBrIM.

**Wind Loads on OpenBrIM** can be calculated for both:

* On structure
* On live loads

For **Wind on Structure**, two separate spreadsheets exist:

1. Users can either define the parameters to generate wind loads according to AASHTO requirements (with 18 cases of attack angles).
2. Alternatively, users can generate wind loads based on specific definitions from the parameter inputs (for instance, using a certain attack angle and constant pressure).

For the \*\*Wind on Live Load,\*\*two separate spreadsheets exist:

1. Users can either make the related definitions to generate loads according to AASHTO.
2. Or users can manually define the magnitudes for both transverse and longitudinal forces and moments, which may differ from AASHTO.


---

# 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/steel-i-girder-bridge-workflow/loading-sig/loads-sig/wind-load-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.
