Skip to main content

An automated GIS toolbox for watershed delineation with lakes

Project description

BasinMaker - An automated GIS toolbox for watershed delineation with lakes

Overview

Before introducing the methodology and application procedure of the BasinMaker, the differences between routing structure without considering lake and routing structure with lakes defined by BasinMaker will be introduce in this section.

A routing structure without considering lakes is showed in Figure 1A. Catchments defined by river reaches in this routing structure are showed in Figure 1A. In hydrological models, the streamflow is only explicitly simulated at the outlet of each catchment. It is not explicitly simulated at the mid of the river segment or any point inside each catchment. Thus, when using this routing structure to build hydrological model, we could obtain the simulated streamflow at end of each reach or catchment outlet in Figure 1A, but the inflow and the outflow of each lake showed in Figure 1 cannot be simulated. Thus, the impact of lake on the routing process modeling such as flow attenuation can not be correctly modeled.

An example of routing structure with lakes generated by the BasinMaker is shown in Figure 1B. Lakes are divided into two categories by the BasinMaker: (1) connected lakes (CL), which indicates lakes directly connected with the river network; and (2) non-connected lakes (NCL), which denotes lakes not connected with the river network (Figure 1B). The resolution of the river network is defined by user provided flow accumulation threshold. Both CL and NCL defined here are within the drainage area of the watershed and water released from both CL and NCL will move to the outlet of the watershed. Thus, the definition of NCL here is not the same as the definition of none contributing area, in which runoff generated will not move to the watershed outlet.

For both CL and NCL, the BasinMaker will use lake polygon to identify each lake’s inlets and outlet and then represent each lake as a lake catchment (LC) shown Figure 1B. A lake catchment will fully cover the lake polygon and its outlet is the same as the outlet of the lake (Figure 1B). At the same time, each inlet of the CL will also be identified as a catchment outlet (Figure 1B). In this way, both inflow and outflow of each lake can be explicitly simulated by the semi-distributed hydrological models.

Figure 1: Lakes in the generated routing network by the lake river routing toolbox. A is the predefined river network and catchment boundary (Catchment boundary (River)) defined by the predefined river network without considering lakes. Figure B, the generated lake river routing structure by this toolbox using predefined river network and lake's polygons.

Documentation

The BasinMaker is developed within python3 environment and using several basic raster and vector functions in QGIS and GRASS GIS. The list of functions from GRASS and QGIS and have been used by BasinMaker can be found in here

  • The installation of the toolbox can be found in here

  • List of all tools provided by BasinMaker can be found in here

Example usage

Example to delineate lake-river routing structure from DEM

  • An example to delineate lake-river routing structure with OIH 30 m DEM can be found here

  • An example to delineate lake-river routing structure with HydroSHEDS 90 m DEM can be found here

  • An example to delineate lake-river routing structure with MERIT 90 m DEM can be found here

Example to post processing existing lake-river routing structure

  • The application procedure to part of the existing lake-river routing structure can be found in here

  • The application procedure to simplify an existing lake-river routing structure by increasing catchments minimum drainage area can be found in here

  • The application procedure to simplify an existing lake-river routing structure by removing lakes with lake area smaller than given lake area threshold can be found in here

  • The application procedure to generate hrus and raven model inputs can be found in here

Example to 'parallel' processing

  • The application procedure to working with large domain with high resolution DEM here

Citation

Han, M., Mai, J., Tolson, B. A., Craig, J. R., Gaborit, É., Liu, H., and Lee, K. (2020a): Subwatershed-based lake and river routing products for hydrologic and land surface models applied over Canada, Canadian Water Resources Journal, 0, 1-15. (publication)

Han, M. et al. (2020b): An automated GIS toolbox for watershed delineation with lakes In preparation.

Han, M., Mai, J., Tolson, B. A., Craig, J. R., Gaborit, É., Liu, H., and Lee, K. (2020c): A catchment-based lake and river routing product for hydrologic and land surface models in Canada (Dataset) Zenodo. (dataset)

Acknowledgments

Funded under Lake Futures project of Global Water Futures program.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

basinmaker-0.0.1.tar.gz (120.9 kB view details)

Uploaded Source

Built Distributions

basinmaker-0.0.1-py3.7.egg (3.3 kB view details)

Uploaded Egg

basinmaker-0.0.1-py3-none-any.whl (3.3 kB view details)

Uploaded Python 3

File details

Details for the file basinmaker-0.0.1.tar.gz.

File metadata

  • Download URL: basinmaker-0.0.1.tar.gz
  • Upload date:
  • Size: 120.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.23.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.7.0

File hashes

Hashes for basinmaker-0.0.1.tar.gz
Algorithm Hash digest
SHA256 1e24a1dbf823345f355ac7b397fa7332811e51354fc2fa0f26502854abd48d0d
MD5 3e44ea098bf565e13aaf645aa9d53936
BLAKE2b-256 b35157c2551c1be629792aefa141a07255dcc1235f905bbecac1e333b696b8f4

See more details on using hashes here.

File details

Details for the file basinmaker-0.0.1-py3.7.egg.

File metadata

  • Download URL: basinmaker-0.0.1-py3.7.egg
  • Upload date:
  • Size: 3.3 kB
  • Tags: Egg
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.23.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.7.0

File hashes

Hashes for basinmaker-0.0.1-py3.7.egg
Algorithm Hash digest
SHA256 434490455617fc13fad3829397d690985a73442dc33112bdb7a71ae062e22cd6
MD5 c9c179287951e77ee98b196be75ad4fa
BLAKE2b-256 b9fb550e1cca3ee96d4464391c83f492ec829ce9138d127faae047bdca95832f

See more details on using hashes here.

File details

Details for the file basinmaker-0.0.1-py3-none-any.whl.

File metadata

  • Download URL: basinmaker-0.0.1-py3-none-any.whl
  • Upload date:
  • Size: 3.3 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.23.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.7.0

File hashes

Hashes for basinmaker-0.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 5fad06343f7e0322a88137dcfbf1eda1a4340aaf1ee397e9cb777101e0f96a57
MD5 e031584404f750a2c269ef0d81c1bfbc
BLAKE2b-256 83362e5f36bf7f8158102274d607d6b5a209786d853dfb00bd69fb58c3a3bca2

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page