User Tools

Site Tools


start:hype_tutorials:hype_setup_tutorial

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
start:hype_tutorials:hype_setup_tutorial [2020/04/08 09:31]
rcapell [Input data, GeoData.txt]
start:hype_tutorials:hype_setup_tutorial [2020/04/08 09:32] (current)
rcapell [Input data, GeoData.txt]
Line 119: Line 119:
 It is necessary that the subbasins are ordered in a downstream sequence. [[https://​github.com/​rcapell/​HYPEtools/​|HYPEtools]] includes a function //​SortGeoData()//​ for this purpose. It is necessary that the subbasins are ordered in a downstream sequence. [[https://​github.com/​rcapell/​HYPEtools/​|HYPEtools]] includes a function //​SortGeoData()//​ for this purpose.
  
-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 HYPEtools 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 HYPEtools can be helpful. To check the routing you can map each sub-basin'​s catchment area (from WHIST: AREA+UPAREA,​ from HYPEtools: //​SumUpstreamArea()//​) and get a view of the network. ​
  
 ==== Input data, P(obs), T(obs), ForcKey ==== ==== Input data, P(obs), T(obs), ForcKey ====
start/hype_tutorials/hype_setup_tutorial.txt ยท Last modified: 2020/04/08 09:32 by rcapell