> 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/superstructure-cug/deck-cug/cross-section-cug.md).

# Cross-Section \[CUG]

## Cross-Section

### Deck Cross Section

**Use Custom Alignments for Deck Edges \[No/Yes]:** When set to Yes, the left and right edges of the deck follow alignments you select instead of offsets measured from the PGL. Use this when the deck edges do not run parallel to the PGL (e.g., widening flares, ramp connections). When set to Yes, PGL to Left Edge and PGL to Right Edge no longer apply and the two edge alignments below become active.

**PGL to Left Edge:** The distance between the PGL and the left edge of the deck. Applies only when Use Custom Alignments for Deck Edges is No.

**PGL to Right Edge:** The distance between the PGL and the right edge of the deck. Applies only when Use Custom Alignments for Deck Edges is No.

**Alignment (Left Edge of Deck):** The alignment the left edge of the deck follows. Applies only when Use Custom Alignments for Deck Edges is Yes, and must then be selected.

**Alignment (Right Edge of Deck):** The alignment the right edge of the deck follows. Applies only when Use Custom Alignments for Deck Edges is Yes, and must then be selected.

When Use Custom Alignments for Deck Edges is Yes, both edge alignments are required: one edge cannot keep its PGL offset while the other follows an alignment. To put only one edge on a second alignment, the other edge still needs an alignment of its own that runs along it. Each edge alignment is a separate alignment object, added and defined under **Bridge Geometry > Roadway Alignment** like the main one.

**Mid Thickness:** The mid thickness of the concrete deck, excluding the overhang part, is utilized as the thickness of the deck shell elements in finite element analysis.

**Left Overhang Thickness:** The thickness of the left overhang at the deck edge. When the Concrete Deck's **Mesh Algorithm** is GridMesh, it is also the thickness of the deck shell elements between the left deck edge and the exterior girder. Whether the overhang bottom tapers from this thickness down to the haunch of the exterior girder is set by the **Taper** input of the Concrete Deck. When Deck Construction includes the haunch load, the additional concrete over the exterior girder is computed from this thickness and that Taper setting.

**Right Overhang Thickness:** The thickness of the right overhang at the deck edge. When the Concrete Deck's **Mesh Algorithm** is GridMesh, it is also the thickness of the deck shell elements between the right deck edge and the exterior girder. Whether the overhang bottom tapers from this thickness down to the haunch of the exterior girder is set by the **Taper** input of the Concrete Deck. When Deck Construction includes the haunch load, the additional concrete over the exterior girder is computed from this thickness and that Taper setting.

![Deck cross-section dimensions](https://openbrim.atlassian.net/wiki/download/attachments/2124775451/image-20230313-112049.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/concrete-u-girder-bridge-workflow/superstructure-cug/deck-cug/cross-section-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.
