Routing Product v2

The Routing Products

The routing product distributed under drainage_region_XXXX_YYYYY_v2_0 is providing several shape files:

1. finalcat_info.* It is the GIS layer containing catchments polygon which respect the lake inflow and outflow routing structures. It can be directly used to generate HRUs or generate model inputs (more details about the attribute table in this GIS layer can be found in here)
2. finalcat_info_riv.* It is the GIS layer containing river network polylines, the columns in it's attribute table is the same as finalcat_info.*.
3. sl_connected_lake.* It is the GIS layer containing the lake polygon of lakes that are connected by the finalcat_info_riv.*. It can be directly used to generate HRUS. The lake polygon is obtained from HydroLAKES database (Messager et al., 2016).
4. sl_non_connected_lake.* It is the GIS layer containing the lake polygon of lakes that are not connected by the finalcat_info_riv.*. It can be directly used to generate HRUS. The lake polygon is obtained from HydroLAKES database (Messager et al., 2016).
5. obs_gauges.* It is the GIS layer containing stream observation gauges included in the routing product. The stream flow observation gauges for watersheds in Canada are obtained from HYDAT database (); While the streamflow observation gauges for watershed in U.S is obtained from USGS (more details about the attribute table in this GIS layer can be found in here)
6. drainage_region_outline_XXXX_YYYYY.* containing drainage region outline of sub-region YYYYY within region XXXX (more details here)
7. catchment_without_merging_lakes.* It is the GIS layer containing catchments polygon of an incomplete routing product. the catchments covered by connected lakes are not merged in this GIS layer. It is used to custmoize/generate the new routing product based on user defined lake area thresholds and catchment minimmum drainage area threshold. The columns in it's attribute table is the same as finalcat_info.*.
8. river_without_merging_lakes.* It is the GIS layer containing river polylines of an incomplete routing product. the river polylines covered by connected lakes are not merged in this GIS layer. It is used to custmoize/generate the new routing product based on user defined lake area thresholds and catchment minimmum drainage area threshold. The columns in it's attribute table is the same as finalcat_info.*.

XXXXX catchment_without_merging_lakes

The attributes are the same as in final cat_info.*. Please see here.

Drainage region outline drainage_region_outline_XXXX_YYYYY

Name	Unit	Type	Description and Specific Values
Region		String	Drainage Region code XXXX
Sub_Reg		String	Sub-region code YYYYY

XXXXX finalcat_info_riv

The attributes are the same as in final cat_info.*. Please see here.

Catchment Information Shapefile finalcat_info

The following attributes can be found in finalcat_info:

Name	Unit	Type	Description and Specific Values
SubId	[-]	Integer	(Sub)Basins ID
DowSubId	[-]	Integer	ID of basin upstream of current basin
RivSlope	m/m	Float	Slope of river
RivLength	m	Float	Length of river
BasSlope	degree	Float	Slope of basin
BasAspect	degree	Float	Aspect of basin, it is counterclockwise from East: 90 degrees is North, 180 is West, 270 is South, 360 is East
BasArea	[m2]	Float	Area of basin
BkfWidth	m	Float	Bankfull width (width of river when full)
BkfDepth	m	Float	Bankfull depth (depth of river when full)
Lake_Cat	[-]	Integer	Lake category 0: basin without lake 1: basin with lake and lake connected by river network 2: basin with lake and lake not connected by the river network
HyLakeId	[-]	Integer	Basin ID in HydroLAKES database
LakeVol	[km3]	Float	Volume of lake; 0.0 for basins w/o lake
LakeDepth	[m]	Float	Depth of lake; 0.0 for basins w/o lake
LakeArea	[m2]	Float	Area of lake; 0.0 for basins w/o lake
Laketype	[-]	Integer	Type of lake (assigned by HydroLAKES) 0: basin without lake 1: basin with lake and lake is natural 2: basin with lake and lake is reservoir 3: basin with lake and lake is natural with regulations
Has_Gauge	[-]	Integer	Basin has streamflow gauge station at outlet 0: basin has no observation streamflow gauge station 1: basin has streamflow gauge station
MeanElev	m	Float	Basin mean elevation
FloodP_n	[m1/3/s]	Float	Channel flood plain manning's coefficient
Q_Mean	[m3/s]	Float	Basin mean streamflow; estimated based on XXXX
Ch_n	[m1/3/s]	Float	Main channel manning's coefficient
DrainArea	[m2]	Float	Basin drainage area based on routing product
Strahler	[-]	Integer	The Strahler order of each river reach
Seg_ID	[-]	Integer	The unique ID of each river reach
Seg_order	[-]	Integer	The unique ID of each river segment in each river reach
Max_DEM	m	Float	The maximum elevation along the river segment
Min_DEM	m	Float	The minimum elevation along the river segment
DA_Obs	[km2]	Float	Basin drainage area reported by institution providing streamflow gauge observations; 0.0 for basins w/o streamflow gauge station
DA_error	[%]	Float	Error defined by ratio between drainage area based on routing product (DrainArea) and basin drainage area reported by institution providing streamflow gauge observations (DA_Obs)
Obs_NM	[-]	String	Name of streamflow observation gauging station (Null for basins w/o streamflow gauging station)
SRC_obs	[-]	String	Country operating streamflow gauging station (CA=WSC and US=USGS; Null for basins w/o streamflow gauging station)
centroid_x	[deg_W]	Float	Basin centroid longitude
centroid_y	[deg_N]	Float	Basin centroid latitude

XXXXX obs_gauges.*

Name	Unit	Type	Description and Specific Values
DA_obs	[km2]	Float	Basin drainage area upstream of the gauge as reported by institution providing streamflow gauge observations
SRC_obs	[-]	String	Country operating streamflow gauging station (CA=WSC and US=USGS)
SubId	[-]	Integer	(Sub)Basins ID whose outlet is defined to best correspond to the streamflow gauge location
DrainArea	[m2]	Float	Basin drainage area upstream of the gauge based on routing product
DA_error	[%]	Float	The difference between DrainArea and DA_obs. Calculated as the ratio between drainage area based on routing product (DrainArea) and basin drainage area reported by institution providing streamflow gauge observations (DA_Obs)
Obs_NM	[-]	String	Name of streamflow observation gauging station
Use_region	[-]	Integer	Defines the spatial extent of the routing product required to cover the drainage area of the streamflow gauge (a guide for users). 1: drainage_region_XXXX required in order to cover entire gauge drainage basin (because the drainage area of this gauge covers more than one sub-region); 0: A single drainage subregion (Sub_Reg) covers the entire gauge drainage basin. It is named as drainage_region_XXXX_YYYYY. Downloading an entire Region is not required if only interested in this gauge.
Region	[-]	String	Drainage Region code XXXX which contains the gauge. Note each drainage region drains into an ocean directly, not to another region.
Sub_Reg	[-]	String	Sub-region code YYYYY which contains the gauge

XXXXX river_without_merging_lakes

The attributes are the same as in final cat_info.*. Please see here.

XXXXX sl_connected_lake

This information is coming directly from the HydroLAKES database. The attribute names in the shapefile are the ones used in HydroLAKES. In total, five attributes will be used for the Routing Product. The attribute names used therein are indicated in the following table. The other attributes and their values are only kept for completeness and user's convenience.

Name HydroLAKES	Name Routing Product	Unit	Type	Description and Specific Values
Hylak_id	HyLakeId		Integer
Lake_name	n/a		String
Country	n/a		String
Continent	n/a		String
Poly_src	n/a		String
Lake_type	Laketype		Integer
Grand_id	n/a		Integer
Lake_area	LakeArea		Float
Shore_len	n/a		Float
Shore_dev	n/a		Float
Vol_total	LakeVol		Float
Vol_res	n/a		Float
Vol_src	n/a		Integer
Depth_avg	LakeDepth		Float
Dis_avg	n/a		Float
Res_time	n/a		Float
Elevation	n/a		Integer
Slope_100	n/a		Float
Wshd_area	n/a		Float
Pour_long	n/a		Float
Pour_lat	n/a		Float

XXXXX sl_non_connected_lake

This information is coming directly from the HydroLAKES database. The attribute names in the shapefile are the ones used in HydroLAKES. In total, five attributes will be used for the Routing Product. The attributes are the same as in sl_connected_lake.*. Please see here for the list of attributes. The attribute names used therein are indicated in the table. The other attributes and their values are only kept for completeness and user's convenience.

Known issues with the Routing Product:

• XXXX
• XXXX

Users are encouraged to report inconsistencies with the product. Please either report either to Ming Han (ming.han@uwaterloo.ca) or create an Issue.