> 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/segmental-overview.md).

# Segmental Wall Overview

Overview of geogrid-reinforced segmental mechanically stabilized earth retaining walls in ENERCALC SEL.

Segmental walls are constructed of stacked masonry blocks, usually of proprietary configurations, without steel rebar, grouting, or mortar. They are dry-stacked, either vertically or with offsets at each block such that the wall is slightly battered and leans into the earth. When geogrids are used in segmental retaining walls, they are placed in horizontal layers separated by some vertical distance as the wall is constructed and backfilling progresses. Their purpose is to reinforce the earth behind the wall such that the reinforced earth zone acts en masse with the wall to resist sliding and overturning, hence no conventional foundation is required. (These walls are also called MSE – Mechanically Stabilized Earth walls.) The geogrids extend beyond the failure plane and resist pullout by friction resistance due to the weight of soil above. Connection to the wall blocks is achieved through friction between blocks and sometimes by proprietary connection devices.

![](https://3283832020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiBJmBoewuy4ZcBC7RF3m%2Fuploads%2Fgit-blob-47cc3cb135519fb64850094740bda9262b27ff85%2FClip33.jpg?alt=media)


---

# 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/segmental-overview.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.
