> 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/inf-surf-based-ll-br-ce-cg/vehicle-cg.md).

# Vehicle \[CG]

## Data

**Factor:** Multiplier to increase the vehicle wheel loads

**Gross Vehicle Weight (readonly) :** Obtained by summing up the loads on all wheels.

## Cell Actions:

![](https://openbrim.atlassian.net/wiki/download/attachments/2125561874/image-20230307-225135.png?api=v2)

**Import Vehicle:** "Import Vehicle" allows you to bring in vehicles from the workspace library into your current project.

![](https://openbrim.atlassian.net/wiki/download/attachments/2125561874/image-20230307-225708.png?api=v2)

**Edit Wheel Loads:** Selecting "Edit Wheel Loads" enables users to create a custom vehicle if it is not available in the library.

![](https://openbrim.atlassian.net/wiki/download/attachments/2125561874/image-20230307-230740.png?api=v2)

X1 refers to the longitudinal positioning of the wheel locations, and it's essential to define the front wheel of the vehicle at X1=0. Y denotes the transverse placement of the wheels, which typically have a spacing of 6 feet between them.

X2 is used to define the range of variation in the location of the axle between two points. X1 indicates the starting point, while X2 indicates the endpoint. If X2 is set to 0, there is no variation in the position of the axle. For instance, the last axle's location varies between 28 and 44, as shown in the above screenshot.


---

# 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/inf-surf-based-ll-br-ce-cg/vehicle-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.