> For the complete documentation index, see [llms.txt](https://swatplus.gitbook.io/io-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swatplus.gitbook.io/io-docs/introduction-1/soils/soils.sol/usle_k.md).

# usle\_k

Some soils erode more easily than others even when all other factors are the same. This difference is termed soil erodibility and is caused by the properties of the soil itself. Wischmeier and Smith (1978) define the soil erodibility factor as the soil loss rate per erosion index unit for a specified soil as measured on a unit plot. A unit plot is 22.1-m (72.6-ft) long, with a uniform length-wise slope of 9%, in continuous fallow, tilled up and down the slope. Continuous fallow is defined as land that has been tilled and kept free of vegetation for more than 2 years. The units for the USLE soil erodibility factor in the MUSLE are numerically equivalent to the traditional English units of 0.01 (ton acre hr)/(acre ft-ton inch). Wischmeier and Smith (1978) noted that a soil type usually becomes less erodible with decrease in silt fraction, regardless of whether the corresponding increase is in the sand fraction or clay fraction.

Direct measurement of the erodibility factor is time consuming and costly. Wischmeier et al. (1971) developed a general equation to calculate the soil erodibility factor when the silt and very fine sand contents make up less than 70% of the soil particle size distribution. Williams (1995) proposed an alternative equation.

#### References

> Wischmeier and Smith (1978)
>
> Wischmeier et al. (1971)
>
> Williams (1995)


---

# 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://swatplus.gitbook.io/io-docs/introduction-1/soils/soils.sol/usle_k.md?ask=<question>&goal=<endgoal>
```

`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.