TauRkSWAT. An Operating System Independent SWAT Model Watershed Initialization Interface. Virginia Tech, Nature Conservancy, EPA, USDA-ARS

Transcription

1 TauRkSWAT An Operating System Independent SWAT Model Watershed Initialization Interface Daniel Fuka, Daniel Auerbach, Brian Buchanan, Amy Collick, Peter Kleinman, Moges Berbero, Andrew Sommerlot, Zachary Easton Virginia Tech, Nature Conservancy, EPA, USDA-ARS

2 Why? Motivating problem: comparison of conservation management across Latin America Needed rapid, consistent & replicable initialization for n-many basins Increase initial parameterization from data rather than defaults Avoid/minimize subjective decisions and user error Wanted to take advantage of existing SWATmodel R package for calibration/optimization via Unix high performance resources Intended to complement NOT replace existing tools Not yet fully developed for deep dive into single location by experienced SWATer But, facilitates platform independent manipulation of TxtInOut from any source

3

4 Why R? Simple install and FREE! Any OS Mac and *nix Bindings to GDAL, OGR, etc. Functions for geospatial processing Automated data access NSF Bcube data brokering Many visualization options (including Google Earth) Powerful analysis tools (e.g., hydrogof & EcoHydRology) Numerous optimization & parallelization options Straightforward, high-level scripting & established support protocols

5 Workflow overview DEM download, pre-processing BCube, RGDAL Watershed delineation Port TauDEM (C++, Fortran to R CRAN) Landuse download, pre-processing HRU definition Parameter initialization Weather Calibration

6 TauRkSWAT Requirements TauDEM4 port to CRAN R Package TauDEM5 is MPI R is not MPI friendly as of yet MPI is not multi-platform consistent.. mainly due to dynamic XCode SWAT txt input file skeleton, creation, and parameter altering scripts EcoHydRology/SWATmodel CRAN packages change_params Theft of ArcSWAT and MWSWAT MDBs for parameterizations

7 Datasets Available Elevation Global SRTM 30m, 90m Global GDEM 30m US 30m NED US 10m NED US 3m NED Landuse Global MODIS Global USGS NLCD Soils Global FAO Vector US SSURGO Vector Historical Daily Weather Global CFSR Gridded Global GHCN Point Forecasts Daily Global 16day Climate Global Last Century Gridded Global Next Century Gridded

8 Watershed delineation: porting TauDEM New TauDEM4 R Workflow: C++ and Fortran flood setdird8 setdir aread8 area gridnet source netsetup Original TauDEM5 Based Workflow: C++ and MPI Pitremove D8Flowdir AreaD8 threshold Streamnet

9 Watershed Delineation Filled elevation and automatically generated subbasins (GRDC ) Columbia

10 HRU definition: Brokering data DEM: SRTM GL1 1sec (30m); various others possible Soils: FAO DSMW; again, others possible pending lookup LU Outside US: MODIS (500m, Broxton et al decadal avg.) Inside US: NLCD2001 (30m) TI (and elevation) classes calculated to support parameter value distribution from DSMW

11 HRU Creation LU & TI classes (n=5)

12 Parameter initialization: Extending existing defaults Lookup tables from hmisc of ArcSWAT and MWSWAT mdbs ArcSWAT Template Stolen Easily modified with R regex alter_files() function in EcoHydRology (e.g., channel width scaling)

13 Weather & Calibration CFSR, GHCN, FAA 4D DataCube accessor functions to pull pre-formatted time series at lat-long (i.e., subbasin centroids) DEOptim & SWATmodel architecture for parallelized operations on project text folders

14 Test case: USGS gages in Puerto Rico

15 Automated success (50/55) USGS Gage # some artifacts of automated subbasin delineation algorithm i.e., decrease contributing area/cells threshold for channel until desired number of subs reached

16 Direct Data/Code Publication Allow full project to data/code publication in FigShare with Template generation

17 VirginiaTech ArcSWAT Interface to TauRkSWAT

18 NEW DATA POLICIES, NSF/AGU/Journals Earth and space science data should be widely accessible in multiple formats and long term preservation of data is an integral responsibility of scientists and sponsoring institutions. all data necessary to understand, evaluate, replicate, and build upon the research must be made available and accessible whenever possible. data include, but are not limited to: data used to generate, or be displayed in, figures, graphs, plots, videos, animations, or tables in a paper. AGU reserves the right to refuse publication when authors are unwilling to make the underlying data available or otherwise refuse to comply with this Data Policy.

19

20

21

22 Finishing Thanksgiving projects Call for community interaction Development Site, Beta Testers