> 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/bridge-geometry-cug.md).

# Bridge Geometry \[CUG]

OpenBrIM provides different workflows for each type of bridge. All objects are pre-defined and parametric, allowing users to create a model by defining several parameters. Due to the nature of parametric modeling, the requirements for defining parameters may vary. Definitions can be made using numbers, other parameters, or by choosing from the provided options.

To obtain the desired model, a specific sequence must be followed, known as the workflow.

The common starting point for all workflows is Bridge Geometry.

For further explanations of each OpenBrIM object, please refer to the relevant section of the documentation.


---

# 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/concrete-u-girder-bridge-workflow/bridge-geometry-cug.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.