> 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/loading-stg/loads-stg/inf-surf-based-llbrce-stg/influence-surface-railroad-stg.md).

# Influence Surface (Railroad) \[STG]

**Rail:** Rail object referencing the rail profile used for this influence surface.

**Live Load Category \[Gravity/Gravity and Centrifugal/Centrifugal/Hunting/Braking]:** Influence-surface category used for this railroad live-load definition.

**Unit Load Spacing Long.:** Longitudinal spacing of the unit loads used to generate the influence surface.

**Centrifugal factor comp. method \[AREMA 1.3.6.c/User defined]:** Method used to compute the centrifugal factor — AREMA 1.3.6.c formula or a user-defined value.

**Max. Design Speed:** Maximum design train speed used in centrifugal-force computation.

**Centrifugal factor:** User-defined centrifugal factor when method is 'User defined'.

**Height of application point (from rail):** Height above the rail at which the transverse force (hunting/centrifugal) is applied.

**Hunting Force Factor (0-1):** Fraction of the wheel load (0-1) applied as the hunting (lateral) force per AREMA 1.3.9.


---

# 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/loading-stg/loads-stg/inf-surf-based-llbrce-stg/influence-surface-railroad-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.