> 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/sw-segmental-walls/sw-gravity.md).

# Design Assumptions for Gravity Segmental Retaining Walls

Understand the NCMA-based methodology and design assumptions for geogrid reinforced segmental retaining walls.

When working with the Geogrid Reinforced Segmental Retaining Wall module, the input screens and output report vary from the conventional cantilevered and restrained retaining walls.

In general, methodology used conforms to NCMA’s *Design of Segmental Retaining Walls, 3rd Edition.*

Since segmental retaining walls can be highly complex, some simplifying design assumptions have been implemented to make the program easier to use and still cover most conditions encountered. These assumptions are:

1. All masonry units are the same size (height, width, depth) and single wythe.
2. Offsets between blocks are uniform for the full height of the wall.
3. Coulomb method is used for determining lateral earth pressures.
4. Setting base is assumed to be gravel or crushed stone, 6” thick, and extending 6” beyond each edge of the bottom block.
5. Block dimensions are obtained from vendor websites or literature.
6. Weight of wall is assumed to be 120 pcf for depth of block.


---

# 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/sw-segmental-walls/sw-gravity.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.
