User Tools

Site Tools


start:hype_tutorials:transfer_lakebasin

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:transfer_lakebasin [2020/05/18 08:25]
cpers
start:hype_tutorials:transfer_lakebasin [2020/05/28 10:46] (current)
cpers
Line 12: Line 12:
 If there are branches from other lakebasins than the last one that leave the multi-basin lake, they now need to have specified outflow information. Earlier they were calculated as a fraction of the flow leaving the lakebasin ((1-//​mainpart//​) in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​branchdata.txt|BranchData.txt]]). That is not possible anymore, additional outlet of a lakebasin lake now need to be specified in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​lakedata.txt|LakeData.txt]]. If there are branches from other lakebasins than the last one that leave the multi-basin lake, they now need to have specified outflow information. Earlier they were calculated as a fraction of the flow leaving the lakebasin ((1-//​mainpart//​) in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​branchdata.txt|BranchData.txt]]). That is not possible anymore, additional outlet of a lakebasin lake now need to be specified in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​lakedata.txt|LakeData.txt]].
  
-All lakebasins will have the same ''​ldtype''​ (7). The last lakebasin (GeoData order) will be identified by HYPE. All lakebasins of a multi-basin lake need to be connected by maindown or branchdown. No subbasins without lakebasin or with a lake belonging to other lake/​multi-basin lake are allowed in between the subbasins of lakebasins. Note that lakebasins belonging to different multi-basin lakes should not be mixed in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​geodata.txt|GeoData.txt]],​ i.e. all lakebasins of a multi-basin lake need to be following each other in GeoData without any other lakebasins in between (mixing with subbasins without lakes or with simple lakes are ok though). This might cause problems.+All lakebasins will have the same ''​ldtype''​ (7). The last lakebasin (GeoData order) will be identified by HYPE. All lakebasins of a multi-basin lake need to be connected by maindown or branchdown. No subbasins without lakebasin or with a lake belonging to other lake/​multi-basin lake are allowed in between the subbasins of lakebasins. ​
  
start/hype_tutorials/transfer_lakebasin.txt ยท Last modified: 2020/05/28 10:46 by cpers