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

# Cross-Section \[SIG]

## Deck Cross Section

**Use Custom Alignments for Deck Edges \[NO/YES]:** Enable this option to use separate alignments for defining the left and right edges of the deck instead of offset values from the main alignment (PGL). When set to 'YES', the PGL to Left Edge and PGL to Right Edge parameters become not applicable, and the Alignment parameters below become active.

**PGL to Left Edge:** The distance between PGL and the left edge. This parameter is only applicable when 'Use Custom Alignments for Deck Edges' is set to 'NO'.

**PGL to Right Edge:** The distance between PGL and the right edge. This parameter is only applicable when 'Use Custom Alignments for Deck Edges' is set to 'NO'.

**Alignment (Left Edge of Deck):** When using custom alignments, select the alignment that defines the left edge of the deck cross-section. This parameter is only applicable when 'Use Custom Alignments for Deck Edges' is set to 'YES'.

**Alignment (Right Edge of Deck):** When using custom alignments, select the alignment that defines the right edge of the deck cross-section. This parameter is only applicable when 'Use Custom Alignments for Deck Edges' is set to 'YES'.

**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 maximum thickness of the left overhang, and it influences the thickness of the deck shell element in the overhang region. The taper parameter will be included in the deck component data. Furthermore, if the deck is constructed using automatic haunch load computation, any additional load will be added or removed based on the thickness and taper parameter of the deck overhang.

**Right Overhang Thickness:** The maximum thickness of the right overhang, and it influences the thickness of the deck shell element in the overhang region. The taper parameter will be included in the deck component data. Furthermore, if the deck is constructed using automatic haunch load computation, any additional load will be added or removed based on the thickness and taper parameter of the deck overhang.

![](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/steel-i-girder-bridge-workflow/superstructure-sig/deck-sig/cross-section-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.