Skip to content

laurencelin/GIS2RHESSys

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

GIS2RHESSys Readme

Introduction

There are two branches under this repository. Master branch (default) holds a set of shell / R scripts for processing GIS data and assemble RHESSys model inputs. Tools are designed to run locally on Mac / Linux. The usage of the scripts are organized by modules documented in workflow guide (links are below). The second branch is "JupyterNotebook" developed and maintained by Lukey (Choi). Lukey's goal is to create a user-friendly workflow interface on JupyterNotebook that utilizes the same scripts held on master branch. JupyterNotebooks have been developed for UVA Rivanna and HydroShare Jupyter App.

Requirements / Dependencies:

Recommended backgrounds for using GIS2RHESSys to setup RHESSysEastCoast model:

  • Any experiences in GIS, including finding data sources, pre- and post- processing data
  • Experiences in command lines, being comfortable to use commands to operate computer
  • Backgrounds in Hydrology and Ecology; After all, RHESSys is an eco-hydrological model used for hydrology and ecosystem studies.

Usage of the tools here

GIS2RHESSys has two parts: GIS setup part (I) and building RHESSys part (II).

The GIS setup part contains GIS (command line) modules to initiate GIS dataset with a desired projection and resolution, import and process raw GIS data, calculated variables and information used to for RHESSys modeling. User has options to perform these tasks on their own or GUI interface as long as user is responsible to understand what variables and information the model requried. A figure below (in data requirement section) summarizes the required GIS information for building RHESSys.

The building RHESSys part is to fill out a template used by the R script to read in maps from an established GRASS GIS database and write out into RHESSys input files, including def files, flow tables, worldfile, and worldfiles header. User is responsible for making the climate data available to the model. Note that vegetation carbon pools in the output worldfile have been initiated, i.e., no need of using LAIread. However, growth simulation is still required spin-up.

GIS setup modules (one of the links below):

Template guides (one of the links below):

Directory structures for RHESSys modeling:

When setup a RHESSys model for a catchment, we are expecting certain directory structure (Figure below).

  • Project directory holds all raw data, GIS dataset, RHESSys model inputs, and observations.
  • Raw data directory (named "raw_data" ) holds any data that are used for model setup, including GIS data, vegetation physiological dataset, and soil data.
  • GRASS database (named "grass_dataset") holds all the GRASS GIS databases that are developed by the commandline workflow; One GRASS database for one RHESSys model;
  • RHESSys model directory (could be named as anything) holds all input files for RHESSys; Sources / binary codes of RHESSys are downloaded and compiled seperatedly.
  • Observation directory (named "obs" ) usually holds streamflow time series or other data for later model calibrations.

Alt text

Minimum data requirements:

  • Elevation
  • Landuse & landcover
  • Soil texture
  • Climate time series (daily) Below diagram shows the relationship between GRASS dataset and RHESSys model. Alt text

Other links:

About

R-coded Workflows for GRASS GIS and RHESSys model

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published