> 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.
### 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.
Quick Tip: Transverse Offset Direction
Offset values use PGL as the reference point.
***
{% 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 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/superstructure-ex1-cug/deck-ex1-cug/cross-section-ex1-cug.md?ask=&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.