Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Number of columns to read for list of elements in the Routing Unit
If each element in the Routing Unit is listed individually, the number of columns to read will equal the number of elements in the Routing Unit. However, if there are several elements with consecutive numbers in a Routing Unit, they can be listed by specifying the first one in one column and the last one with a hyphen in front of it in the next column.
Object type of the element
The following object types can be elements in a Routing Unit:
another rtu
hru
res
aqu
sdc
rec
Pointer to the topography file
The pointer to the topography file is a foreign key referencing name in topography.hyd.
The topography variables for Routing Units are used to compute time of concentration for sub-daily routing.
Pointer to the routing unit definition file
The pointer to the routing unit definition file is a foreign key referencing id in rout_unit.def.
This file references other files specifying the elements that are part of a Routing Unit and its topographic and field properties.
id
ID of the Routing Unit
integer
name
Name of the Routing Unit
string
Pointer to the Routing Unit definition file
string
dlr
Delivery ratio
Pointer to the topography file
string
Pointer to the field file
string
This file specifies which elements a Routing Unit contains.
ID of the Routing Unit
integer
Name of the Routing Unit
string
Number of columns to read for list of elements in the Routing Unit
integer
First column listing elements in the Routing Unit
integer
Pointer to the field file
The pointer to the field file is a foreign key referencing in .
ID of the routing unit
The ID of the Routing Unit is a primary key referenced by in . All IDs in the rout_unit.rtu file must be unique.
Name of the routing unit
The name of the routing unit is not used by the model.
Routing Units are the spatial units in SWAT+ that allow us to lump outputs and route them to any other spatial object. Routing Units don't have a lot of properties as they mostly serve the purpose of collecting hydrographs and the simulation of the processes generating those is controlled by the properties of the individual elements within a routing unit.
references other files specifying the elements that are part of a Routing Unit and its topographic and field properties.
specifies which elements a Routing Unit contains.
lists all elements that are part of a Routing Unit.
First column listing elements in the Routing Unit
If = 1, there can be only one element in the Routing Unit, whose ID ( in ) is specified in this column. If > 1, this column is followed by additional columns listing the elements included in the Routing Unit, but those columns will not have a header. If there are several elements with consecutive numbers in a Routing Unit, they can be listed by specifying the first one in one column and the last one with a hyphen in front of it in the next column.
ID of the element
The ID of the element is a primary key referenced by elements in rout_unit.def. All IDs in the rout_unit.ele file must be unique.
Unique ID of the Routing Unit
The ID of the Routing Unit is a primary key referenced by define in rout_unit.rtu. All IDs in the rout_unit.def file must be unique.
Name of the Routing Unit
The name of the Routing Unit is not used by the model.
Name of the element
The name of the element is not used by the model.
This file lists all elements that are part of a Routing Unit.
ID of the element
integer
Name of the element
string
Object type of the element
string
Object ID of the element
integer
frac
Fraction of Routing Unit area assigned to the element
real
dlr
Currently not used
real
Object ID of the element
The object ID of the element is a foreign key referencing the ID of the object in its file: