SWAT+, Soil and Water Assessment Tool
The Soil and Water Assessment Tool (SWAT+) is a hydrological model used to simulate processes such as surface runoff, groundwater flow, and water quality across watersheds of varying scales. It evaluates the effects of land use, management practices, and climate scenarios on water resources. SWAT+ is widely used for studying soil erosion, non-point source pollution, and watershed management (https://swat.tamu.edu/) .The tool allows users to upload custom TextInOut folders to model any watershed of interest. Users can define model parameters, the simulation time range, calibration settings, output variables, and temporal resolution. By default, the tool is configured to simulate the hydrological behavior of the La Tordera Basin from 2000 to 2022 using SWAT+. The default tool settings generate daily outputs of flow, water temperature, and nutrient levels at the mouth of La Tordera River between July 2019 and December 2020, allowing for an assessment of river flow parameters during Storm Gloria (19 January 2020). The default La Tordera Basin model is calibrated through a two-step calibration process: an initial soft calibration based on a qualitative evaluation of annual average outputs, followed by an automatic calibration by landscape units using observed gauge data from the Catalan Water Agency (Agència Catalana de l'Aigua, https://aca.gencat.cat/). This tool executes SWAT+ using SWATrunR ( https://github.com/chrisschuerz/SWATplusR ) with the SWAT+ rev60.5.7_64rel_linux executable.
tordera use case AquaINFRA R SWAT+ watershed model
| Id | Title | Data Type | Description |
|---|---|---|---|
| TextInOut_URL | URL to project folder | object | To model a watershed other than the Tordera Basin, users can add a URL to their own zipped project folder. Important: Do not include the SWAT executable to that folder — AquaINFRA has integrated the executable version rev60.5.7_64rel_linux. Defaults to: https://raw.githubusercontent.com/AmandaBatlle/AquaINFRA_CaseUse_MedInlandModel/refs/heads/main/example_inputs/project.zip |
| par_cal | Parameter inputs | object | JSON file including the parameter value change as defined by SWATrunR documentation (https://chrisschuerz.github.io/SWATrunR/articles/SWATrunR.html#parameter-inputs). Defaults to: https://raw.githubusercontent.com/AmandaBatlle/AquaINFRA_CaseUse_MedInlandModel/refs/heads/main/example_inputs/par_cal.json |
| unit | Output Spatial unit | integer | Specify the spatial unit for which to generate output. This corresponds to the ID of a river reach, HRU (Hydrologic Response Unit), or LSU (Landscape Unit) as defined in the SWAT+ watershed delineation. The value can be entered as a single number (e.g., 1), a range (e.g., 1:10), or a list of values (e.g., (1, 3, 25, 40)). The default unit for the La Tordera SWAT+ model is 1. |
| file | SWAT Output File | string | A SWAT+ output file name consists of three elements separated by underscores (_): spatial unit, output category, and time step. For example, 'channel_sd_day'. The spatial unit defines the scale of the output and can be basin, hru, lsunit, channel, aquifer, or reservoir. The output category specifies the type of data such as wb (water balance), nb (nutrient balance), ls (losses), pw (plant and weather), or sd (streamflow and sediment in channels). The time step indicates the temporal resolution and can be day (daily), mon (monthly), yr (yearly), or aa (annual average). Combining these elements forms the output file name. For more details, refer to the SWAT+ OUTPUT FILES section in the SWAT+ documentation (https://swatplus.gitbook.io/io-docs). Defaults to: "channel_sd_day" |
| variable | SWAT Variable | string | Variable to simulate. Example: "flo_out". For more details and extended capabilities, refer to the SWAT+ OUTPUT FILES section in the SWAT+ documentation (https://swatplus.gitbook.io/io-docs). For one variable, enter the variable name. For multiple variables, enter them separated by comma. Defaults to: "flo_out,water_temp" |
| start_date | Start Date | integer | Start date of the simulation in the format yyyymmdd. Defaults to: 20160101. Earliest possible date for the default input project: 20000101. |
| start_date_print | Start Date for printing | integer | Start date for printing in the format yyyymmdd. Defaults to: 20190601. Earliest possible date for the default input project: 20020101. It is recommended to allow for at least two warm-up years between the model simulation start and the model output printing to ensure relevant results. |
| end_date | End Date | integer | End date of the simulation in the format yyyymmdd. Defaults to: 20201231. Latest possible date for the default input project: 20221231. |
| Id | Title | Description |
|---|---|---|
| swat_output_summary | SWAT+ run summary | SQLite database (inputs.sqlite) containing all the parameters used in the executed SWAT+ run |
| swat_output_file | SWAT+ Variable Outputs Database | SQLite database (thread_1.sqlite) storing the simulated output values based on the defined time range and time step (daily, monthly, yearly, or annual average). |
Educational resources and documentation
- How to use a OGC processing service with R (text/html)
- How to use a OGC processing service with python (text/html)
Jobs
Browse jobsLinks
- GitHub repo (text/html)
- How to use a OGC processing service with R (text/html)
- How to use a OGC processing service with python (text/html)
- Process description as JSON (application/json)
- Process description as HTML (text/html)
- Jobs list as HTML (text/html)
- Jobs list as JSON (application/json)
- Execution for this process as JSON (application/json)
Execution modes
- Synchronous
- Asynchronous