Introduction to the new modular SWAT code: The input file structure explained using the example of the Little River Experimental Watershed, USA

Transcription

1 Introduction to the new modular SWAT code: The input file structure explained using the example of the Little River Experimental Watershed, USA Katrin Bieger and Jeffrey G. Arnold 2014 International SWAT Conference Pernambuco, Brazil 7/30/2014

2 Introduction - Ongoing development of SWAT integration of new variables and subroutines complex code and input/output files, that are difficult to manipulate and maintain - Large number of input files causes long model runtimes - New modular SWAT code: - Data is stored in objects instead of a large number of individual arrays - HRUs, subbasins, aquifers and channels are separate spatial objects flexibility in defining spatial interactions within the watershed

3 Structure of HRU input files weather_generator.dat hru.dat weather_stations.da snow.dat topography.dat hydrology.dat surface_storage.dat landuse.dat mgt_ops.dat plant_initial.dat soils.dat soil_nut_initial.dat weather data files wind_direction.dat atmodep.dat urban_parms.dat cntable.dat plant_parms.dat plant_initial.dat fertops.dat autofertops.dat contfertops.dat grazeops.dat sweepops.dat pestops.dat contpestops.dat harvkillops.dat harvops.dat irrops.dat plant_parms.dat fert_parms.dat pest_parms.dat pest_initial.dat pest_parms.dat autoirrops.dat bact_initial.dat bact_parms.dat tillops.dat tillage_parms.dat str_ops.dat tiledrain.dat burnops.dat str_initial.dat septic.dat septic_parms.dat

4 HRU properties This file points to a number of separate files defining the HRU properties, e.g. climate, topography, hydrology, soil, land use and management

5 Weather: climate stations and data Specifies whether observed or simulated climate data are used Specifies which climate station is used by pointing to the number of the dataset in climate data files (pcp1.pcp, tmp1.tmp, hmd.hmd, slr.slr, wnd.wnd)

6 Topography

7 Hydrology

8 Soils Equivalent to former usersoil database!

9 Landuse General land use properties that used to be defined in the.mgt files.

10 Plant initialization and parameters Initialization of plants/crops and plant communities

11 Management operations Operation code # of operation Date/heat unit scheduling

12 Subbasin definition and elements sub_define.dat: sub_element.dat:

13 Subbasin spatial connections and properties - OBTYP_OUT = Type of spatial object the output is sent to Output is sent - OBTYPNO_OUT = # of spatial object 100% to two locations - HTYP_OUT of total = flow Type is of sent hydrograph to the 100% that is of sent recharge is sent to the channel - FRAC_OUT in the = respective Fraction of hydrograph aquifer in the respective subbasin subbasin

14 Aquifer spatial connections and properties Output is sent 100% of total flow is sent to the to one locationchannel in the respective subbasin

15 Channel spatial connections and properties Output is sent 100% of total flow is sent to the to one location channel located downstream

16 Basin 1. basin_cc.dat: Basin control codes, e.g. PET method, water routing method, channel degradation code, stream water quality code 2. basin.dat: General watershed properties, e.g. EVLAI, FFCB, SURLAG, ADJ_PKR

17 Run the model and print output time.dat print.dat 1 = annual, 2 = monthly, 3 = daily

18 Output files - waterbal and waterbal_aa - nutbal and nutbal_aa - losses and losses_aa - plantwx and plantwx_aa *.hru, *.sub, and *.bsn - channel.out and channel_aa.out - aquifer.out and aquifer_aa.out - mgt.out - crop_yld_aa.out - soils.out

19 Conclusion - Flexible spatial interactions within the watershed - Sharing of data structures and files with other models (EPIC, APEX) - Development of additional databases (e.g., management schedules and operations) - Development of interface will start this fall - Release of first version planned for next summer

20 Thank you for your attention!