Metadata-Version: 2.1
Name: basinmaker
Version: 0.0.3
Summary: An automated GIS toolbox for watershed delineation with lakes
Home-page: https://github.com/dustming/basinmaker
Author: basinmaker development team
Author-email: m43han@uwaterloo.ca
License: UNKNOWN
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>
            <p align="center">
            <img src="https://github.com/dustming/RoutingTool/wiki/Figures/Figure1.png" width="100%" height="100%" />
            </p>
            <font size="1">
            <figcaption width="50%"> <b>Figure 1</b>: 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.<br>
            </figcaption>
            </font>
        </figure>
        
        # 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](https://github.com/dustming/basinmaker/wiki/Installation-of-the-BasinMaker#functions-from-qgis-and-grass-gis) 
        
        * The installation of the toolbox can be found in [here](https://github.com/dustming/RoutingTool/wiki/Installation-of-the-BasinMaker)
        
        * List of all tools provided by BasinMaker can be found in [here](https://github.com/dustming/RoutingTool/wiki/List-of-tools-provided-by-BasinMaker)
        
        # 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](https://github.com/dustming/basinmaker/tree/master/examples/wathershed_delineation_oih_30m_dem)
        
        
        * An example to delineate lake-river routing structure with HydroSHEDS 90 m DEM can be found [here](https://github.com/dustming/basinmaker/tree/master/examples/wathershed_delineation_hyshed_90m_dem)
          
        
        * An example to delineate lake-river routing structure with MERIT 90 m DEM can be found [here](https://github.com/dustming/basinmaker/tree/master/examples/wathershed_delineation_merit_90m_dem)  
        
        
        ## 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](https://github.com/dustming/basinmaker/tree/master/examples/extract_part_of_existing_lake_river_routing_structure)
        
        * The application procedure to simplify an existing lake-river routing structure by increasing catchments minimum drainage area can be found in [here](https://github.com/dustming/basinmaker/tree/master/examples/simplify_existing_routing_product_by_drainage_area)
        
        * 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](https://github.com/dustming/basinmaker/tree/master/examples/simplify_existing_routing_structure_by_filter_lakes)
        
        * The application procedure to generate hrus and raven model inputs can be found in [here](https://github.com/dustming/basinmaker/tree/master/examples/generate_hru_and_model_inputs)
        
        ## Example to 'parallel' processing  
        
        * The application procedure to working with large domain with high resolution DEM [here](https://github.com/dustming/basinmaker/tree/master/examples/parallel_for_large_watersheds)
        
        
        # 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](https://www.tandfonline.com/doi/ref/10.1080/07011784.2020.1772116?scroll=top))
        
        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](https://zenodo.org/record/3667677#.X7xD0c1KiUk))
        
        # Acknowledgments
         
        Funded under Lake Futures project of Global Water Futures program.
        <p align="left">
           <img src="https://github.com/dustming/Crop_Growth_Library/wiki/figures/logos/GWF_logo.png" width="10%"  />
           <img src="https://github.com/dustming/Crop_Growth_Library/wiki/figures/logos/LAKEFUTURES_logo.png" width="10%"  />
        </p>
        
        
Platform: UNKNOWN
Classifier: Programming Language :: Python :: 3
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Requires-Python: >=3.5
Description-Content-Type: text/markdown
