This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
start:hype_tutorials:hype_setup_tutorial [2017/07/04 09:01] cpers [Input data, GeoData.txt] |
start:hype_tutorials:hype_setup_tutorial [2018/06/08 15:20] cpers [Setting up optional input files for HYPE] |
||
---|---|---|---|
Line 119: | Line 119: | ||
It is necessary that the subbasins are ordered in a downstream sequence. [[https://github.com/rcapell/RHYPE/|RHYPE]] includes a function //SortGeoData()// for this purpose. | It is necessary that the subbasins are ordered in a downstream sequence. [[https://github.com/rcapell/RHYPE/|RHYPE]] includes a function //SortGeoData()// for this purpose. | ||
- | When GeoData.txt has been constructed it is always agood idea to check the tailoring of the data. Join the geodata.txt to the subbasin shapefile and produce some maps for spatial check, i.e. ELEV_MEAN, summerized LandUse and Soilclasses. A function //GroupSLCClasses()// from RHYPE can be helpful. To check the routing you can map each sub-basin's catchment area (from WHIST: AREA+UPAREA, from RHYPE: //SumUpstreamArea()//) and get a view of the network. | + | When GeoData.txt has been constructed it is always a good idea to check the tailoring of the data. Join the geodata.txt to the subbasin shapefile and produce some maps for spatial check, i.e. ELEV_MEAN, summerized LandUse and Soilclasses. A function //GroupSLCClasses()// from RHYPE can be helpful. To check the routing you can map each sub-basin's catchment area (from WHIST: AREA+UPAREA, from RHYPE: //SumUpstreamArea()//) and get a view of the network. |
==== Input data, P(obs), T(obs), ForcKey ==== | ==== Input data, P(obs), T(obs), ForcKey ==== | ||
Line 188: | Line 188: | ||
===== Setting up optional input files for HYPE ===== | ===== Setting up optional input files for HYPE ===== | ||
- | There are many optional components in HYPE. Below we describe some of the most commonly used optional model components, lakes and reservoirs and bifurcations, which often have large impact on the hydrology in large-scale river basins. | + | There are many optional components in HYPE. Below we describe some of the most commonly used optional model components, lakes and reservoirs and bifurcations, which often have large impact on the hydrology in large-scale river basins. Others can be found among the tutorials (e.g. [[start:hype_tutorials:floodplain_tutorial|floodplains]]). |
==== Information about outlet lakes (LakeData.txt)==== | ==== Information about outlet lakes (LakeData.txt)==== | ||