> 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-tub-girder-bridge-workflow/reports-stg/seat-elevation-table-stg.md).

# Seat Elevation Table \[STG]

For each insertion point location, the elevation with respect to the PGL (0 Ft) can be presented to the user as a report, provided the section is defined.

## General

**Bridge:** This parameter can be used to specify the bridge model for which the seat elevation table will be generated.

**Select Elev. Location \[Bottom of Girder/Bottom of Seat]:** The seat elevation table can be generated for either the bottom of the girder or the bottom of the seat. This parameter can be used to specify that property.

## Settings

**Number of Decimal Points:** This input allows users to define the number of decimal points to be displayed.

{% hint style="info" %}
The **Seat Elevation Table** includes:

* Support lines,
* Skew angles,
* Bearings,
* Station with respect to the PGL, and
* The elevation of either the bottom of the girder or the bottom of the seat. ![image-20250620-123946.png](https://openbrim.atlassian.net/wiki/download/attachments/2126151808/image-20250620-123946.png?api=v2)
  {% 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/templates/steel-tub-girder-bridge-workflow/reports-stg/seat-elevation-table-stg.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.