> For the complete documentation index, see [llms.txt](https://docs.archlogbook.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archlogbook.co/02-urban-site-planning-building-design-concepts/slope-gradients.md). # Slope Gradients **Slope gradient represents how steep a ramp is.**\ **It is represented by a ratio of rise to run.** Or its height and length respectively. The smaller the unit of run vs 1 unit of rise, the steeper the slope is. Thus a 1:8.3 slope is steeper than a 1:15 one. ## **Common gradients:** **(slope gradient listed are the maximum allowed and are non-exhaustive)** 1 : 2 - Steepest slope for earth without need for ERSS\* 1 : 8.3 - Steepest vehicular access slope 1 : 10 - Equipment ramp 1 : 12 - Wheelchair ramp 1 : 15 - Fire Engine deployment, heavy vehicles straight ramp 1 : 20 - Curved ramps for heavy/articulated vehicles (20/40ft trailers) 1 : 25 - Handicap Ramp without need for handrails 1 : 30 - Drainage gradient for public roads 1 : 100 - Screed to fall for roof drainage 1: 200 - Screed to fall for workshops drainage --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.archlogbook.co/02-urban-site-planning-building-design-concepts/slope-gradients.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.