> 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/superstructure-ex1-cug/deck-ex1-cug/cross-section-ex1-cug.md).

# Cross-Section

{% hint style="info" %}
**Navigation:** Superstructure > Deck > Cross Section

For detailed parameter explanations, see the [Cross-Section Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/superstructure-cug/deck-cug/cross-section-cug).
{% endhint %}

## Steps

### Step 1: Understand Cross-Section Requirements

If the section of your deck varies from the beginning to the end of your project, you should define at **least two** cross-sections.

However, in this particular project, the deck sections remain consistent throughout. Thus, it is adequate to define **a single** cross-section to generate this deck.

### Step 2: Navigate to Cross Section

Navigate to **Deck > Cross Section** in the tree view.

![Navigation](https://openbrim.atlassian.net/wiki/download/attachments/2258763829/image-20230829-113151.png?api=v2)

### Step 3: Enter Cross-Section Name

Navigate to the first cell in the Name column and enter **CS1** as the name.

### Step 4: Enter Cross-Section Values

Enter all Cross Section values as in the figure.

![Cross Section Values](https://openbrim.atlassian.net/wiki/download/attachments/2258763829/image-20230829-113509.png?api=v2)

<details>

<summary><strong>Quick Tip:</strong> Transverse Offset Direction</summary>

Offset values use PGL as the reference point.

</details>

![Cross Section Diagram](https://openbrim.atlassian.net/wiki/download/attachments/2104689432/image-20230216-130246.png?api=v2)

***

{% hint style="success" %}
The Cross Section has been created.
{% endhint %}


---

# 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/superstructure-ex1-cug/deck-ex1-cug/cross-section-ex1-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.
