|
|
Here you will find some step by step tutorials for some basic WHIST procedures.
|
|
|
|
|
|
____
|
|
|
|
|
|
[[_TOC_]]
|
|
|
____
|
|
|
## C 1 Delineate new subbasins using the given topography data
|
|
|
|
|
|
There are two ways to delineate new subbasins in WHIST from topography data.
|
|
|
- with so called "forced points"
|
|
|
- without "forced points"
|
|
|
|
|
|
Forced points are locations we want to **coincide with subbasin outlets**, e.g. hydrological features as gauging stations, lake or reservoir outlets.
|
|
|
|
|
|
Forced points must be **adjusted to the river network of the topography data** before they are useful otherwise the delineation of a proper upstream area from the forced point can not be developed. See [**HYPE set up tutorial**](http://www.smhi.net/hype/wiki/doku.php?id=start:hype_tutorials:hype_setup_tutorial#creating_sub-basins_for_hype) for more information.
|
|
|
|
|
|
Instructions for the creation of forced points can be found here: **[C 3 Adjust forced points to river network](Adjust forced points to river network)**.
|
|
|
|
|
|
When the forced points are generated or if no forced points are going to be used, follow these instructions:
|
|
|
|
|
|
|
|
|
- Go to HYDRO/Create and click on the "Edit" button in the new window
|
|
|
|
|
|
![01_Basin_creation](uploads/c4b13e9512525188c9ac8e6833d5b443/01_Basin_creation.png)
|
|
|
|
|
|
|
|
|
|
|
|
The new dialog window is shown in the figure further down.
|
|
|
|
|
|
Under **Grids** you can see which grids are used for the delineation and routing created. The GWD-LR river width (WTH) grid is here used as a mask to get the full width of broad rivers and avoid subbasins to be cut along the centerline.
|
|
|
|
|
|
Under **Parameters and options** you can set a subbasin area limit for both usptream subbasins and the coastal subbasins (a smaller coastal area limit decrease the number of very broad and large coastal subbasins). For World-wide HYPE and the course model the limits were set as in the figure, 1000 and 500 km2 respectively.
|
|
|
|
|
|
**Basin area limit shapefile** is an option where you can override the parameter "basin area limit" under "Parameters and options" by using a polygon shapefile with set limits. E.g. for urban area and steep mountains where it might be of interest to have higher resolution.
|
|
|
|
|
|
|
|
|
Under **Forced points file** you can browse for the file you use for forced points. Here are the gauging stations adjusted to the river network according to instruction under **[C 3 Adjust forced points to river network](Adjust forced points to river network)** has been used.
|
|
|
|
|
|
With the button "force reload of forced points file" the forced points shapefile will reloaded if it has been edited outside of WHIST during the same session (WHIST loads the forced points shapefile the first time it is used and keeps it in memory until shut down or the use of this button).
|
|
|
|
|
|
**Optional settings to add extra forced points for the subbasin generation**
|
|
|
(:warning: These are tools that you should test thoroughly before use. Especially if you use MASK. We have not used them very much ourselves yet.)
|
|
|
|
|
|
|
|
|
*Split on field*: Reads INTEGER from a column in the forced points shapefile for each point. Each point is then SPLIT into this number (max 3) of actual points that are pushed to immidiate upstream cells (in order of flow acc magnitude) and used as forced points instead of the singular original point. Value lower than or equal to zero means no split and the point will remain at original location (and still used!), note that a number of 1 still means that the point will be pushed one upstream cell. This function enables fine tuning the control of splitting on significant tributaries regardless of actual upstream area. Consider the case when X number of inflows to each lake needs catchments, then this function together with MASK should simplify the process.
|
|
|
|
|
|
*MASK*: Set a grid MASK to be used when placing the forced points. Grid cells with “Forbidden” values will push any forced points upstream until the mask grid read a non-forbidden value, the reverse “Accepted” values simplifies the use of certain grids and provides the same functionality. This function enables fine tuning the placement of forced points without the need of adjusting the forced point shapefile, e.g to prevent catchment from starting in lakes, wide rivers etc. The MASK is applied after any split using the “Split on field” (so points are first split and pushed one cell upstream in order of flow acc magnitude and then each resulting sub point may be further pushed upstream until a valid value is found in the mask).
|
|
|
|
|
|
*Final points*: Give name of output shapefile (overwrites!) where the final forced points will be saved, after any “Split on field” and MASK.
|
|
|
|
|
|
|
|
|
![02_Basin_creation](uploads/597c9b996d37ab77e3caf573b1d49a97/02_Basin_creation.png)
|
|
|
|
|
|
Save the settings and activate the button "Add tiles". If you are adding subbasins to already existing subbasins the "force add tiles" must be checked.
|
|
|
|
|
|
![03_Basin_Creation](uploads/015171dacee8f1b25bba3801bf542979/03_Basin_Creation.png)
|
|
|
|
|
|
Click on Tile size and choose the size of the calculation window. Approximately 5-15 subbasin per tile is fine (so this is dependent on the previous settings).
|
|
|
|
|
|
![04_Basin_Creation](uploads/926eece40518d113839f825aaa74391a/04_Basin_Creation.png)
|
|
|
|
|
|
Click OK and then click somewhere to add the first tile. Preferably where you have the outlets of the rivers. (You can also add tiles over the entire area from start).
|
|
|
|
|
|
![05_Basin_Creation](uploads/ca3326d223ae442d4c2adb2ab0cddf1b/05_Basin_Creation.png)
|
|
|
|
|
|
Then click on start iteration button and after a while some subbasins will appear within the tile.
|
|
|
|
|
|
![06_Basin_Creation](uploads/6f1d7ab34ab22000b8937e75196425d3/06_Basin_Creation.png)
|
|
|
|
|
|
These subbasins are not all finished and to let WHIST search for the upstream areas for some certain subbasins you should:
|
|
|
- deactivate the place tiles button
|
|
|
- select the river outlets you are interested in
|
|
|
- click on the Edit 1 /Haro Id "set"
|
|
|
|
|
|
![07_Basin_Creation](uploads/b514f03eee4d2c13b69a71c9c60dafaa/07_Basin_Creation.png)
|
|
|
|
|
|
New tiles will then automatically be added.
|
|
|
|
|
|
![08_Basin_Creation](uploads/046a6bd3c0a907ccf58ef7e89f03856c/08_Basin_Creation.png)
|
|
|
|
|
|
Check the "auto add tiles" and start iteration again. Now the iteration will continue until the total upstream areas of the selected coastal subbasins are finished.
|
|
|
|
|
|
![09_Basin_Creation](uploads/3947dfae1439fc96d5987a984e25e63b/09_Basin_Creation.png)
|
|
|
|
|
|
If you select the catchment you want to use for your model and then use the button **[Flip](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/-9.-Select-subbasins#92-select-subbasins-with-buttons-external-shapefile-or-dialog)** you will select all the other subbasins.
|
|
|
|
|
|
![10_Basin_Creation](uploads/c4e826f50adca9d00d3bcdeaf9d30435/10_Basin_Creation.png)
|
|
|
|
|
|
Use the **[kill](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/10.-Editing-tools#1027-kill-delete-subbasins)** button to delete the unnecessary subbasins.
|
|
|
|
|
|
![11_Basin_Creation](uploads/c04361582cadfbccb2a3f13e7bc52087/11_Basin_Creation.png)
|
|
|
|
|
|
If you **[view the Flow or Flownet](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/10.-Editing-tools#1027-kill-delete-subbasins)** you can see how the subbasins are routed.
|
|
|
|
|
|
Save your work, see **[Save](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/-8.-Load-and-save-WHIST-work#82-save-all-subbasins-as-folder-save)**
|
|
|
|
|
|
Now you can link other spatial data to these subbasins (elevations, SLC´s, etc), see **[11. Extract and connect attributes to the subbasins](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/11.-Extract-and-connect-attributes-to-the-subbasins)** and export a first output for a GeoData.txt file for HYPE.
|
|
|
|
|
|
You can also export different kinds of shapefiles (subbasins, flowlines, main river basins etc), see **[12. Export shapefiles and tables](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/12.-Export-shapefiles-and-tables)**
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## C 2 Delineate new subbasins using my own topography data
|
|
|
Read all instructions thoroughly and remember:
|
|
|
|
|
|
- There are just a few coordinate systems that can be used
|
|
|
- There are just a few DIR code systems to use so you have to adjust your data for this.
|
|
|
- The grids must be of BIL format.
|
|
|
|
|
|
See instructions: [**2. WHIST requirements**](https://git.smhi.se/whist/whist/wikis/WHIST-Wiki/-2.-WHIST-requirements#24-topographic-data).
|
|
|
|
|
|
When you have created the gridded data you must set a link to the data within WHIST and inform WHIST about its properties. See the instructions **[2.4.4 Load new topography data into the WHIST database](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/-2.-WHIST-requirements#244-load-new-topography-data-into-the-whist-database)**
|
|
|
|
|
|
After the loading of the grids you can make a first check and try to view them within WHIST, see **[6.3 Viewing grids/topography](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/-6.-View-tools#63-viewing-gridstopography)**
|
|
|
|
|
|
A second test is to create some first subbasins to see that the settings are fine and that the grids are harmonized. If no subbasins appear or strange subbasins appear, e.g very small, there might be something wrong with the units or projections.
|
|
|
|
|
|
When you are able to create subbasins you can decide whether you would like to prepare subbasins tailored to specific hydrological features or not (these split points can be added manually afterwards also, if a smaller model). Go to **[C 3 Adjust forced points to river network](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/Create-subbasins-from-hydrologically-corrected-topography-data-(DEM,-DIR,-ACC)#c-3-adjust-forced-points-to-river-network-under-development)** if you want to prepare forced points. If no forced points are needed, follow the instructions in [C 1.1 Create subbasins](https://git.smhi.se/whist/whist/-/wikis/WHIST-Wiki/Create-subbasins-from-hydrologically-corrected-topography-data-(DEM,-DIR,-ACC)#c11create-subbasins).
|
|
|
|
|
|
|
|
|
|
|
|
## C 3 Adjust forced points to river network
|
|
|
|
|
|
The forced points, e.g. gauging stations, might have unsure coordinates in their metadata which might not correspond to the topography river network used. Before these forced points can be used for tailoring the outlets of the subbasins they have to be adjusted to the river network. See figure beneath.
|
|
|
|
|
|
![FORCEDPOINTS](uploads/26db116c5d0977d86952d401b3db505b/FORCEDPOINTS.png)
|
|
|
*Figure to the left shows how the position of the feature is adjusted to the river network (ACC/UPA grid in behind). Figure to the right shows how the subbasin delineation is tailored to get the subbasin outlets at the forced points.*
|
|
|
|
|
|
**PROCEDURE:**
|
|
|
|
|
|
1. Prepare a metadata table as in the figure. The bold headers are mandatory. Save this file as a tab separated textfile (ASCII file).
|
|
|
|
|
|
- ID: a unique number
|
|
|
- NAME: a name for the location (no space allowed)
|
|
|
- LAT: original latitude of the feature
|
|
|
- LON: original longitude for the feature
|
|
|
- DRAINAGE: Drainage area in km2 of the feature (if not known, write -9999)
|
|
|
- RADIUS: The limit of the search area in the same unit as the topography data used.
|
|
|
|
|
|
![ForcedPointAdjustment](uploads/38456b0440b664bc5c88123538b8b71b/ForcedPointAdjustment.png)
|
|
|
*Example of a table, tailored for WHIST, with gauging station metadata according to the original source.*
|
|
|
|
|
|
2. Start WHIST and go to HYDRO/create/edit, see figure. Check that you are using the correct grids (DEM, DIR, ACC/UPA) and add a mask if there are locations to no adjustments should be allowed, e.g. within lakes, in the sea etc. Save and close window.
|
|
|
|
|
|
![CheckCorrectDATABASE_red2](uploads/9ee799ea93c0557dda85bda8eb64f52b/CheckCorrectDATABASE_red2.png)
|
|
|
*Figure: How to check that correct topography database and method is used.
|
|
|
|
|
|
3. Go to HYDRO/create or edit forced points.
|
|
|
|
|
|
![CreateForcPoint1](uploads/b7b3c1f7b667371c9ac33c44ca64ac74/CreateForcPoint1.png)
|
|
|
|
|
|
4. Click on the button "Add points from file" and browse for your tab separated textfile.
|
|
|
|
|
|
![CreateForcPoint2b](uploads/fb4a85a8248d8b845e38ddfbb67e0fff/CreateForcPoint2b.png)
|
|
|
|
|
|
5. Your table will appear at the top of the window. Check that you have the correct ACC/UPA grid, see figure beneath, and then click on the button "Auto Adjust".
|
|
|
|
|
|
![CreateForcPoint3b](uploads/f516c1fb179d05a75d4e9f622c736c9b/CreateForcPoint3b.png)
|
|
|
|
|
|
6. A new window opens where you select which column that shows the ID, drainage area, radius, if you want to use a mask where no forced points will be allowed. There is also a parameter called Accuracy, here you can give a floating value between 0-1. if you for example set it to 0,05 you let WHIST to search for the best point within the search window which match the drainage area with an accuracy of +/- 5%.This parameter can be used to decrease the spatial adjustment (the drainage area may be more inaccurate than the location). Click OK.
|
|
|
|
|
|
![CreateForcPoint5b](uploads/c37439b7e53468e579c98704b05e5487/CreateForcPoint5b.png)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|