> 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/theoretical-documentation/section-7-main-channel-processes/in-stream-nutrient-processes.md). # In-Stream Nutrient Processes Parameters which affect water quality and can be considered pollution indicators include nutrients, total solids, biological oxygen demand, nitrates, and microorganisms (Loehr, 1970; Paine, 1973). Parameters of secondary importance include odor, taste, and turbidity (Azevedo and Stout, 1974). The SWAT+ in-stream water quality algorithms incorporate constituent interactions and relationships used in the QUAL2E model (Brown and Barnwell, 1987). The documentation provided in this chapter has been taken from Brown and Barnwell (1987). The modeling of in-stream nutrient transformations has been made an optional feature of SWAT+. To route nutrient loadings downstream without simulating transformations, the variable IWQ in the basin input (.bsn) file should be set to 0. To activate the simulation of in-stream nutrient transformations, this variable should be set to 1. --- # 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/theoretical-documentation/section-7-main-channel-processes/in-stream-nutrient-processes.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.