This shows you the differences between two versions of the page.
Both sides previous 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 [2017/07/04 09:02] cpers [Input data, GeoData.txt] |
||
---|---|---|---|
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 ==== |