Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Latitude of the object
Longitude of the object
Loading...
Loading...
Loading...
Pointer to the constituent file
Loading...
Pointer to the decision table for hydrograph fractions
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Elevation of the object
used for lapse rates
Name of the object
The SWAT+ Editor assigns a name to every object, which is typically the abbreviation of the object type followed by the object number in QSWAT+. However, the name of the object is not used by SWAT+, so the user may change it.
Gravity-controlled flow is routed from one spatial object to the next using so-called connect files, which are available for the following objects:
Object | Connect file |
---|---|
All connect files have the exact same structure, so to avoid repetition it is only described once instead of for every spatial object (see 'object'.con). The connectivity between objects can be changed during the simulation using Decision Tables.
If the user wishes to connect an aquifer to more than one channel, the aqu_cha.lin file can be used instead of the aquifer connect file.
Unique ID of the object
The unique ID of the object is a primary key that is referenced by .
Please be aware that the unique ID of the object is not necessarily the same as the ID in QSWAT+. The GIS interface numbers the objects when they are first created. Later in the process, some objects might be replaced by others, e.g. channels that are located within reservoirs. When the SWAT+ Editor writes the SWAT+ input files, it assigns consecutive ID numbers to those objects that are still included in the final setup of the model. It is extremely important to pay attention to this when identifying the channels that streamflow gauges are located on for comparing simulated and observed data.
HRU
hru.con
HRU-lte
hru-lte.con
Routing Unit
rout_unit.con
Aquifer
aquifer.con
SWAT-DEG channel
chandeg.con
Reservoir
reservoir.con
Point source/inlet
recall.con
Export coefficient
exco.con
Delivery ratio
delratio.con
Outlet
outlet.con
This file defines the connectivity of spatial objects.
Field | Description | Type | Unit | Default | Range |
---|---|---|---|---|---|
Unique ID of the object
integer
n/a
n/a
n/a
Name of the object
string
n/a
n/a
n/a
Object number in QSWAT+
integer
n/a
n/a
n/a
Area of the object
real
ha
n/a
n/a
Latitude of the object
real
dec degrees
n/a
-90.0-90.0
Longitude of the object
real
dec degrees
n/a
-180.0-180.0
Elevation of the object
real
m
100.0
0-7000
Pointer to the object data file
integer
n/a
n/a
n/a
Pointer to the weather station file
string
n/a
n/a
n/a
Currently not used
integer
n/a
n/a
n/a
Currently not used
integer
n/a
n/a
n/a
Currently not used
integer
n/a
0
0-1
Total number of outgoing hydrographs
integer
n/a
1
12
Type of the receiving object
string
n/a
n/a
n/a
ID of the receiving object
integer
n/a
n/a
n/a
Type of hydrograph that is sent to the receiving object
string
n/a
n/a
n/a
Fraction of hydrograph sent to the receiving object
integer
fraction
n/a
0-1
Pointer to the weather station file
The pointer to the weather station file is a foreign key referencing name in weather-sta.cli.
Object ID in QSWAT+
Please be aware that the ID in QSWAT+ is not necessarily the same as the unique ID of the object. The GIS interface numbers the objects when they are first created. Later in the process, some objects might be replaced by others, e.g. channels that are located within reservoirs. When the SWAT+ Editor writes the SWAT+ input files, it assigns consecutive ID numbers to those objects that are still included in the final setup of the model. It is extremely important to pay attention to this when identifying the channels that streamflow gauges are located on for comparing simulated and observed data.
Area of the object
HRU: Area of HRU, conversion from mm to m3
Routing Unit: Area of Routing Unit, conversion from mm to m3
Aquifer: Area of aquifer, conversion from mm to m3
Reservoir/Channel: Drainage area of the channel/reservoir
Outlet: not used
Recall: not used
Export coefficient: not used
Delivery ratio: not used
ID of the receiving object
The ID of the receiving object is a foreign key referencing the object ID (id) in the connect file of the receiving object.
Pointer to the overbank flooding file
This file is used to connect an aquifer to multiple channels.
A detailed description of this file will be added as soon as possible.
Type of the receiving object
Code | Definition |
---|---|
Recall, Export Coefficient, and Delivery Ratio objects cannot be receiving objects.
hru
HRU
hlt
HRU-lte
ru
Routing Unit
aqu
Aquifer
cha
Channel
res
Reservoir
out
Outlet
Type of hydrograph that is sent to the receiving object
The types of hydrographs that can be sent depend on the object. The code tot is used for several spatial objects, but its meaning differs between objects.
Code | Object | Definition |
---|---|---|
tot
Channel
Streamflow
tot
Aquifer
Groundwater flow
tot
Reservoir
Reservoir outflow
tot
Outlet
Flow at the outlet
tot
Recall
Flow from point source or inlet
tot
HRU & Routing Unit
Surface runoff + lateral flow + tile flow
sur
HRU & Routing Unit
Surface runoff
lat
HRU & Routing Unit
Lateral flow
til
HRU & Routing Unit
Tile flow
rhg
HRU, Routing Unit, aquifer, reservoir
Seepage that recharges the receiving object
Fraction of hydrograph sent to the receiving object
When editing the fractions, the user has to make sure that they add up to 1. Otherwise, water will be added or removed from the system and the water balance will not close.
Pointer to the object data file
The pointer to the object data file is a foreign key referencing the unique ID in the respective object data file. The header of this column is different in each connect file.
Connect file | Column header | Object data file |
---|---|---|
hru.con
hru
hru-lte.con
hlt
rout_unit.con
rtu
aquifer.con
aqu
chandeg.con
lcha
reservoir.con
res
recall.con
rec
exco.con
exc
delratio.con
dlr
outlet.con
out
No data file