> 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/substructure-ex1-cug/foundation-ex1-cug/rectangular-ex1-cug.md).

# Rectangular

This section defines rectangular spread footing foundations.

{% hint style="info" %}
**Navigation:** Substructure > Foundation > Rectangular

For detailed parameter explanations, see the [Rectangular Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/substructure-cug/foundation-cug/rectangular-cug).
{% endhint %}

## Steps

### Step 1: Navigate to Rectangular Foundation

Navigate to **Foundation > Rectangular** in the tree view.

### Step 2: Define Footing Dimensions

Enter the footing dimensions including width, length, and thickness.

### Step 3: Assign to Columns

Associate each footing with the appropriate pier column.

### Step 4: Set Material

Assign the concrete material to the footings.

## Verification

{% hint style="success" %}
After completing these steps, the rectangular footings are defined and ready for the structural model.
{% 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/substructure-ex1-cug/foundation-ex1-cug/rectangular-ex1-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.