> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-user-manual/calculation-modules/earth-retention/cantilevered-and-restrained-re/ct-criteria-tab/ct-general-data-2-2.md).

# Use of Vertical Component (Not in Restrained Retaining Wall module)

How to choose where the vertical component of active soil pressure is applied in retaining wall design.

**Use of vertical component of active lateral soil pressure**

This category offers options for considering the vertical component of active lateral soil pressure:

* Use for Soil Pressure & Footing Design
* Use for Sliding Resistance
* Use for Overturning Resistance
* Use for Global Stability Check

When used, the vertical component of the active earth pressure is applied as follows.

When EFP is used, the program will backsolve the Coulomb equation to find the equivalent internal friction angle, phi. The soil-wall friction angle is assumed to be phi/2, and the vertical component will be applied at the the back of the ***wall***.

When the Coulomb method is used, the phi angle is specified by the user. The soil-wall friction angle is assumed to be phi/2, and the vertical component will be applied at the back of the ***wall***.

When the Rankine method is used, the active earth pressure acts parallel to the slope of the retained soil, and the vertical component will be applied at the end of the ***heel***.


---

# 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://enercalc.com/docs/sel-user-manual/calculation-modules/earth-retention/cantilevered-and-restrained-re/ct-criteria-tab/ct-general-data-2-2.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.
