Land Use Management

A primary goal of environmental modeling is to assess the impact of human activities on a given system. Central to this assessment is the itemization of the land and water management practices taking place within the system. This section contains input data for planting, harvest, irrigation applications, nutrient applications, pesticide applications, and tillage operations. Information regarding tile drains and urban areas is also stored in this file.

SWAT+ Input File	Database Table
landuse.lum	landuse_lum
management.sch	management_sch
	management_sch_auto
	management_sch_op
cntable.lum	cntable_lum
ovn_table.lum	ovn_table_lum
cons_practice.lum	cons_practice_lum

In addition to the above, SWAT+ Editor groups the operations databases in this section of the editor. However, within the SWAT+ master watershed file (file.cio), these are listed under the ops section.

SWAT+ Input File	Database Table
graze.ops	graze_ops
harv.ops	harv_ops
irr.ops	irr_ops
sweep.ops	sweep_ops
fire.ops	fire_ops
chem_app.ops	chem_app_ops

Land Use Management

This section is the entry point for management data in SWAT+. It comprises cross-walks to several other sections of data.

This data is accessed from the HRU properties section (hru-data.hru).

landuse_lum

Field	Type	Description	Related Table
id	int	Auto-assigned identifier
name	text	Name of the land use properties
cal_group	text	Calibration group
plnt_com_id	int	Plant community	plant_ini
mgt_id	int	Management schedule	management_sch
cn2_id	int	Curve number	cntable_lum
cons_prac_id	int	Conservation practices	cons_prac_lum
urban_id	int	Urban land use	urban_urb
urb_ro	text	Urban runoff
ov_mann_id	int	Overland flow Manning's n	ovn_table_lum
tile_id	int	Tile drain	tiledrain_str
sep_id	int	Septic tank	septic_str
vfs_id	int	Filter strip	filterstrip_str
grww_id	int	Grassed waterway	grassedww_str
bmp_id	int	Best management practices	bmpuser_str
description	text	Optional description of the row

Management Schedules

Management schedules comprise auto-schedules (decision tables) and/or operations schedules.

When you import your project from GIS, SWAT+ assigns auto-schedules for management based on your crop land use.

Plant Type (in plants_plt)	Decision Table Template
warm_annual	pl_hv_corn
cold_annual	pl_hv_wwht
perennial	no management schedule

For example, oats is a cold annual crop. If this crop is in your HRUs, a decision table named pl_hv_oats will be created based on the template of pl_hv_wwht when you import your data from GIS.

Adding/Editing a Schedule

From the management schedules section, click create a new record or click edit on a row in the table. Give your schedule a unique name.

There are two modes within the editor: schedule builder and advanced. The schedule builder tab lets you easily customize existing decision table parameters in an easy-to-read format. Click the edit icon next to any existing tables in your schedule, or add a new one using the drop down at the bottom.

For most users we recommend using the schedule builder tab to select from decision tables built and tested by the model team. Advanced users can click the advanced tab and select automatic schedules or enter manual operations.

Input Data Definitions

Refer to the SWAT+ Documentation section on Landuse and Management for input column definitions and units.