User Tools

Site Tools


start:hype_file_reference:lakedata.txt

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
start:hype_file_reference:lakedata.txt [2020/05/05 10:30]
cpers
start:hype_file_reference:lakedata.txt [2020/05/25 07:53]
cpers
Line 3: Line 3:
 This file contains lake properties for **outlet lakes** with specific data available. Properties defined here override the properties and generic parameters given in [[start:​hype_file_reference:​geodata.txt|GeoData.txt]] and [[start:​hype_file_reference:​par.txt|par.txt]]. If you want to use a generic parameter from [[start:​hype_file_reference:​par.txt|par.txt]] for a particular lake in //​LakeData.txt//,​ use -9999 as parameter value for that lake in //​LakeData.txt//​. Lake depth from [[start:​hype_file_reference:​geodata.txt|GeoData.txt]] may also be kept by using -9999 for the value in //​LakeData.txt//​. Lake properties include physical characteristics,​ e.g. depth, and outlet rating curve, regulation routine parameters, and parameters concerning nutrient cycling within the lake. In //​LakeData.txt//,​ two regulation regimes can be defined; constant flow and seasonally varying sinus-wave shaped flow. For more regulation options, use [[start:​hype_file_reference:​damdata.txt|DamData.txt]],​ which extends the regulation options provided here. This file contains lake properties for **outlet lakes** with specific data available. Properties defined here override the properties and generic parameters given in [[start:​hype_file_reference:​geodata.txt|GeoData.txt]] and [[start:​hype_file_reference:​par.txt|par.txt]]. If you want to use a generic parameter from [[start:​hype_file_reference:​par.txt|par.txt]] for a particular lake in //​LakeData.txt//,​ use -9999 as parameter value for that lake in //​LakeData.txt//​. Lake depth from [[start:​hype_file_reference:​geodata.txt|GeoData.txt]] may also be kept by using -9999 for the value in //​LakeData.txt//​. Lake properties include physical characteristics,​ e.g. depth, and outlet rating curve, regulation routine parameters, and parameters concerning nutrient cycling within the lake. In //​LakeData.txt//,​ two regulation regimes can be defined; constant flow and seasonally varying sinus-wave shaped flow. For more regulation options, use [[start:​hype_file_reference:​damdata.txt|DamData.txt]],​ which extends the regulation options provided here.
  
-Outlet lakes in HYPE can cover a fraction of a subbasin or the whole subbasin. Large lake systems can be split into several subbasins themselves (lake basins), which allows for different properties in different lake basins. Outlet flows for such multi-basin lakes are defined for each lake basin which has an outlet to the outside of the multi-basin lake. Flow between lakebasins are not defined in here. Maximum five outflows of a multi-basin lake is allowed. Smaller lakes that are not divided into lakebasins may have two outlets defined in LakeData.txt (see [[start:​hype_model_description:​hype_routing#​outlet_lake_with_two_outlets|model description]]). These outlets are defined by ''​ldtype''​ 5 and 6 for the main outlet and the branch outlet. For these lakes only the downstream subid of the branch need to be given in [[start:​hype_file_reference:​branchdata.txt|BranchData.txt]].+Outlet lakes in HYPE can cover a fraction of a subbasin or the whole subbasin. Large lake systems can be split into several subbasins themselves (lake basins), which allows for different properties in different lake basins ​(e.g. depth). Outlet flows for such multi-basin lakes are defined for each lake basin which has an outlet to the outside of the multi-basin lake. Flow between lakebasins are not defined in here. Maximum five outflows of a multi-basin lake is allowed. Smaller lakes that are not divided into lakebasins may have two outlets defined in LakeData.txt (see [[start:​hype_model_description:​hype_routing#​outlet_lake_with_two_outlets|model description]]). These outlets are defined by ''​ldtype''​ 5 and 6 for the main outlet and the branch outlet. For these lakes only the downstream subid of the branch need to be given in [[start:​hype_file_reference:​branchdata.txt|BranchData.txt]].
  
  
start/hype_file_reference/lakedata.txt.txt ยท Last modified: 2020/05/25 08:06 by cpers