Differences

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

--- start:hype_tutorials:hype_setup_tutorial [2017/07/04 09:00]
cpers [Input data, GeoClass.txt]
+++ start:hype_tutorials:hype_setup_tutorial [2017/07/04 09:02]
cpers [Input data, GeoData.txt]
@@ Line 112: / Line 112: @@
 Geodata.txt holds information about the subbasins, i.e. routing, area, mean elevation, fraction of SLCs, parameter regions, general lake depths etc. See [[start:hype_file_reference:geodata.txt|GeoData.txt]] for a comprehensive reference on GeoData.txt columns.
-The structure of a GeoData.txt files is shown in Fig. 9. The first column holds the ROWNR to keep the order of the rows since the subbasins have to be ordered in a downstream sequence starting at headwaters and ending at outlet basins. The columns SUBID and MAINDOWN (0=outlet to the sea) hold the routing information (see green cells). The columns may be in any order. The mandatory columns for simulating water are: SUBID, MAINDOWN, AREA, ICATCH, RIVLEN and SLC_nn, but it is also recommended to use LAKE_DEPTH and ELEV_MEAN. If you use a [[start:hype_file_reference:lakedata.txt|LakeData.txt]] file for tailored data on lake properties, you need to link to this file in the column named LAKEDATAID (see blue cell). The parameter regions (which can be used in par.txt  to correct some parameters according to regions) are described in PARREG column. The sum of the SLCs should always be =1. See the geodata.txt for more information about the geodata columns.
+The structure of a GeoData.txt files is shown in Fig. 9. The first column holds the ROWNR to keep the order of the rows since the subbasins have to be ordered in a downstream sequence starting at headwaters and ending at outlet basins. The columns SUBID and MAINDOWN (0=outlet to the sea) hold the routing information (see green cells). The columns may be in any order. The mandatory columns for simulating water are: SUBID, MAINDOWN, AREA, ICATCH, RIVLEN and SLC_nn, but it is also recommended to use LAKE_DEPTH and ELEV_MEAN. If you use a [[start:hype_file_reference:lakedata.txt|LakeData.txt]] file for tailored data on lake properties, you need to link to this file in the column named LAKEDATAID (see blue cell). The parameter regions (which can be used in par.txt  to correct some parameters according to regions) are described in PARREG column. The sum of the SLCs should always be =1. See the [[start:hype_file_reference:geodata.txt|GeoData.txt]] for more information about the geodata columns.
 |{{ :start:hype_tutorials:hype_setup_tutorial:figure9.png?direct&700 |}}|
@@ 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.
-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 ====

HYPE Model Documentation

User Tools

Site Tools

Differences

Page Tools