> 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-6-management-practices/water-management/irrigation.md). # Irrigation Irrigation in an HRU may be scheduled by the user or automatically applied by SWAT+ in response to a water deficit in the soil. In addition to specifying the timing and application amount, the user must specify the source of irrigation water. Water applied to an HRU is obtained from one of five types of water sources: a reach, a reservoir, a shallow aquifer, a deep aquifer, or a source outside the watershed. In addition to the type of water source, the model must know the location of the water source (unless the source is outside the watershed). For the reach, shallow aquifer or deep aquifer, SWAT+ needs to know the reach number or subbasin number, respectively, in which the source is located. If a reservoir is used to supply water, SWAT+ must know the reservoir number. If the source of the irrigation water is a reach, SWAT+ allows additional input parameters to be set. These parameters are used to prevent flow in the reach from being reduced to zero as a result of irrigation water removal. Users may define a minimum in-stream flow, a maximum irrigation water removal amount that cannot be exceeded on any given day, and/or a fraction of total flow in the reach that is available for removal on a given day. For a given irrigation event, SWAT+ determines the amount of water available in the source. The amount of water available is compared to the amount of water specified in the irrigation operation. If the amount available is less than the amount specified, SWAT+ will only apply the available water. --- # 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-6-management-practices/water-management/irrigation.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.