Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Please refer to the SWAT+ Input/Output Documentation linked below:
Please refer to the SWAT+ Input/Output Documentation linked below:
Documentation for this section is not available yet. For now, please refer to the SWAT+ input/output documentation PDF for parameter definitions.
In SWAT+, constant values for point sources and inlets are stored in the export coefficients properties file, exco.exc, while time series data are stored entirely in the recall section.
However, in the editor, we keep both constant and time series point sources and inlets in the recall section. When you write input files, the editor will write to the exco.exc and exco_om.exc files appropriately.
Documentation for this section is not available yet. For now, please refer to the SWAT+ input/output documentation PDF for parameter definitions.
Please note: there was a long outstanding issues with time series recall in version 2.0.x of SWAT+ Editor due to a missed change in format of the model. This should be corrected in SWAT+ Editor 2.1.2 and greater. Please update your software and project and reach out if you encounter any issues.
Recall objects are used for connecting point source or inlet data to your watershed. If you added point source in QSWAT+, when you import your project into SWAT+ Editor it will be connected via the recall section.
By default, constant data with all zero values during the default simulation period is added. To add your own recall data, click the recall item in the edit menu under connections.
Download sample data. Please read the README.txt file in the zip carefully.
By default, your recall data is imported as constant. To insert your values, you can edit each item individually by clicking the edit button and manually entering each value. Alternatively, you may upload a CSV of your data.
From the recall section, click the import/export button from the action bar at the bottom. Import is selected by default, so click the export button toggle. Choose a folder name, and click the export data button to get a template for your data.
Constant data will be located in the recall.csv
file in the directory you selected. Edit the CSV as needed, save, and then go back to the editor and click the import/output button again. This time toggle the import button. Choose your directory containing your modified files and click the import CSV data button. Your updated values will appear in the table.
By default recall data is imported as constant, however this can be changed by clicking the edit button next to a row in the recall data table. Select the new time step for your data: daily, monthly, or yearly. Click the save changes button. Next, press the back button to go back to the table view. Click the import/export button. Import is selected by default, so click the export button toggle. Choose a folder name, and click the export data button to get a template for your data.
Your directory may now contain two files: a recall.csv containing constant data, and another csv file named for the recall object (e.g., pt002
) you changed to time series.
Open the time series file after it is exported to see the template for your data. Modify your data as needed matching the time step you selected previously. Be sure the years match your simulation run time.
You change other recall objects from constant to time series, and you can mix and match all different types (constant, yearly, monthly, and daily). For any recall objects moving from constant to time series, first delete its row in recall.csv
. Then create a new csv with the file name matching the recall object's name and insert your time series data. Similarly, if you want to move from time series back to constant, just delete the time series file and add a row back into recall.csv
for the object.
To import your data, click the import/export data button again and this time click to toggle import. Choose your directory and click import data. Your new data will appear in the table.
Each record in recall_rec will have a data file named {name}.rec. All of this data is stored in a single recall_dat table in the database.
Please refer to the SWAT+ Input/Output Documentation linked below:
Please refer to the SWAT+ Input/Output Documentation linked below:
The connections section contains all spatial object connectivity for the simulation run. In SWAT+ Editor, all connection object properties can be set through this section. For example, when you click on channels, you will see additional menu links appear for initialization, hydrology and sediment, and nutrients.
All connection objects have a similar format as seen in the above figure. Each connection object will have properties associated with it (such as initial, hydrology and sediment, and nutrients in this example) as well as a weather station. Click on these names in the table, or from the edit view page, click the button next to their names to view information about the properties object or weather station.
Each connection object may have outflow. The total number of outflow connections is shown in the right-most column of the table (note: you may need to use the horizontal scroll button at the bottom of the table if it is wide). To view the outflow objects, click the edit icon on the left of the row you want to view.
If you imported your project from GIS, your connection objects are populated automatically during project setup.
The subbasin is defined by the DEM in the GIS interface as it always has been. All flow within the subbasin drains to the subbasin outlet.
A landscape unit (LSU) is defined as a collection of HRUs and can be defined as a subbasin, or it could be a flood plain or upland unit, or it could be a grid cell with multiple HRUs. The landscape unit is not routed, it only used for output. The landscape unit output files (waterbal, nutbal, losses, and plant weather) are output for HRUs, landscape units, and for the basin. Two input files are required: 1) landscape elements and, 2) landscape define. The elements file includes HRUs and their corresponding LSU fraction and basin fractions. The define file specifies which HRUs are contained in each LSU.
A routing unit is a collection of hydrographs that can be routed to any spatial object. The routing unit can be configured as a subbasin, then total flow (surface, lateral and tile flow) from the routing unit can be sent to a channel and all recharge from the routing unit sent to an aquifer. This is analogous to the current approach in SWAT. However, SWAT+ gives us much more flexibility in configuring a routing unit. For example, in CEAP, we are routing each HRU (field) through a small channel (gully or grass waterway) before it reaches the main channel. In this case, the routing unit is a collection of flow from the small channels. We also envision simulating multiple representative hillslopes to define a routing unit. Also, we are setting up scenarios that define a routing unit using tile flow from multiple fields and sending that flow to a wetland.
The routing unit is the spatial unit SWAT+ that allows us to lump outputs and route the outputs to any other spatial object. It gives us considerably more flexibility than the old subbasin lumping approach in SWAT, and will continue to be a convenient way of spatial lumping until we can simulate individual fields or cells in each basin.
Please refer to the SWAT+ Input/Output Documentation linked below:
SWAT+ Input File
Database Table
recall.rec
recall_rec
Field
Type
Description
id
int
Auto-assigned identifier
name
text
Name of recall object
rec_typ
int
Time step for recall object (1-daily, 2-monthly, 3-yearly)
SWAT+ Input File
Database Table
{name}.rec
recall_dat
Field
Type
Description
Units
jday
int
Julian day
mo
int
Month
day_mo
int
Day of the month
yr
int
Year
ob_typ
text
Type of recall
ob_name
text
Name of recall object
flo
real
Volume of water
m^3
sed
real
Sediment
metric ton
orgn
real
Organic nitrogen
kg N
sedp
real
Organic phosphorus
kg P
no3
real
Nitrate
kg N
solp
real
Mineral (soluble P)
kg P
chla
real
Chlorophyll-a
kg
nh3
real
Ammonia
kg N
no2
real
Nitrogen dioxide
kg N
cbod
real
Carbonaceous biological oxygen demand
kg
doc
real
Dissolved oxygen
kg
sand
real
Detached sand
silt
real
Detached silt
clay
real
Detached clay
sag
real
Detached small ag
lag
real
Detached large ag
gravel
real
Gravel
tmp
real
Temperature
deg c