> 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/concrete-u-girder-bridge-workflow/loading-cug/loads-cug/static-loads-cug/vehicle-load-cug.md).

# Vehicle Load \[CUG]

**Bridge:** Select the bridge.

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

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

**Transverse Offset:** Specify the transverse offset, perpendicular to the PGL, to define the location of the vehicle load.

**Vehicle**: Vehicles can either be imported or manually defined by the user in the Influence Surface-Based Live Load/Breaking Load/Centrifugal Load section and later assigned to this parameter.

**Force (Gravity) (readonly):** The gross vehicle weight of the chosen vehicle is displayed to the user under this column.


---

# 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/concrete-u-girder-bridge-workflow/loading-cug/loads-cug/static-loads-cug/vehicle-load-cug.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.