> 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/openbrimfea/model-fea/reference-geometry-fea.md).

# Reference Geometry \[FEA]

Reference Geometry holds the reference frames the model is built and reported against.

* [Alignments](https://docs.openbrim.org/templates/openbrimfea/model-fea/reference-geometry-fea/alignments-fea.md) define the roadway geometry - horizontal path, vertical profile and cross-slopes - so objects can be positioned by station and offset rather than by absolute coordinates, and so the model follows the roadway when it changes.
* [Coordinate Systems](https://docs.openbrim.org/templates/openbrimfea/model-fea/reference-geometry-fea/coordinate-systems-fea.md) define a local frame with its own origin and rotation. Their main structural purpose is skewed and inclined boundary conditions: a bearing on a skewed abutment is fixed along the bearing line and free across it, which cannot be expressed in global axes at all.

Assigning a coordinate system to a node reinterprets its coordinates **and** its restraint directions, and reports its displacements and reactions in that frame - so a result that appears to disagree with a global hand-check is often correct and simply expressed locally.


---

# 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/openbrimfea/model-fea/reference-geometry-fea.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.
