Copyright: I have got the permission from project partners to publish these information. The copyrights of the data and related software are hold by all project parters. All the information here is for demonstration purpose only. It can’t be used for any other purpose. For any concerns, please don’t hesitate to contact me.
Team: Watershed Evaluation Group, University of Guelph
Objective: Develop an interface to create and evaluate what-if agricultural BMP scenarios to help conservation districts/authorities gain understanding on water quantity and quality effects and allocate limited resources for BMP implementation
Agricultural best management practices (BMPs) has been applied in Canada to help reduce nitrogen and phosphorus coming from farm fields. With limited budget and clear water quality goal, conservation districts/authorities need to choose the most cost-effective BMPs and their locations. Managers needs a decision support system (DSS) to help them understand the impact of various available BMPs on hydrology and economy, i.e. what-if scenarios, and then make proper decisions.
The Watershed Evaluation of Beneficial Management Practices (WEBs) program was a successful nine-year Government of Canada initiative to determine the economic and water quality impacts of selected agricultural beneficial management practices (BMPs) at nine watershed sites across Canada. The interface was developed as part of the program for the South Tobacco Creek watershed located near Miami, Manitoba.
- Create scenarios to add, remove and configure various BMPs
- Run SWAT and economic model for each scenario
- Display SWAT, economic and integrated results on field, farm, subbasin and watershed level with map and chart
The interface is a Windows form application developed using C#. The main part of the interface is the map area implemented with DotSpatial map control. Microsoft chart controls are used for all charts.
In model side, to enable fast access to SWAT results, SQLite is added to SWAT source codes to write all results into a SQLite database with fixed structure including tables, views and indexes. A scenario definition file is also generated as the bridge between the interface and SWAT model to exchange data. Mix-language compilation (C and Fortran) is required to compile the modified SWAT codes.
The system architecture is show below.
ROLES AND RESPONSIBILITIES
- Design the main architecture and choose required technologies
- Design the GUI and code with C#
- Design the interface between GUI and SWAT with the scenario definition file
- Modify SWAT sourced codes to support SQLite results and scenario definition file
Project tree on the left to navigate different views, including project, scenario, BMPs and results
A project represents a watershed. It includes the geospatial and model information.
A scenario is a combination of various BMPs including small dams, holding ponds, grazing, tillage and forage conversion. SWAT and economic model could be run for each scenario. Results could be viewed after the simulation is done.
Small Dam View
Select/deselect small dam on map or from the list on the right to enable/disable them in model
Tillage View, Field Level
Select/deselect fields on map or from the list on the right to apply tillage. Farm level and subbasin level is also supported.
Result View, SWAT Results
- Display results with different colors for polygon and different sizes for point
- Select a feature to view time series in chart at the bottom
- Control result display using the right panel
Result View, Economic Results
Result View, Integrated Results
- Cost-effectiveness, i.e. the amount of reduction (on water, sediment, N or P) per $1000 between two scenarios.
- Most valuable for conservation districts and authorities
Result View, Off-site Integrated Results
Off-side is for the result at the watershed outlet and is good for whole watershed evaluation.