Users create new tables using Database -> Create River Database Tables or tool. There are three tables always required for a model creation: river lines, cross-sections and flow paths. If a table needs a user specified attribute, it is given in the User defined attributes column. The table below lists river database tables created by RiverGIS. There is a table for river lines, cross-sections etc. Model geometry data are stored in a river database tables.
When a schema is created from outside the RiverGIS use the Database > Refresh Connections List or the tool. If a connection or schema was created in a previous session, it can be chosen from the DB Connection or Schema dropdown lists. RiverGIS will automatically switch to the newly created schema, as shown below. Users can create a schema in a number of ways: using pgAdmin, QGIS’ own DB Manager or from within RiverGIS dialog by choosing Database > Create New Schema or clicking tool icon from Database toolbar.
Therefore, the first step is to create a new schema for a model. Each model goes to its own schema, a kind of database directory for data grouping. A digital terrain model is subsequently synthesized by merging. Until a database and schema are set in RiverGIS window, most of the tools are inactive.Ī single PostgreSQL database can be used to store many models geometries. conversion from hydraulic model coordinates to geographic coordinates. A term river database refers to a database used by RiverGIS. At J_2, outflows from Subbasin_2 and Subbasin_3 are combined with R_1 flow before being carried and routed by Reach R_3.A fundamental difference from HEC-GeoRAS is that the RiverGIS uses a PostgreSQL database with PostGIS spatial extension for data storage (see Requirements for installation instructions). The original Subbasin_1 is split into new Subbasin_1 and Subbasin_3 and a new Reach R_1 is also created to accept the outflow from Subbasin_1 and then route the flow downstream to Junction J_2 ( Figure 5). You need to zoom in far enough to click within an identified stream grid cell. Muskingum-Cunge reach routing for channel reaches Transforms old TR-20 input data to new WinTR-20 format HEC-RAS Reformatter that transforms HEC-RAS output profile data to WinTR-20 stream cross section data Please report any problems you find to the WinTR-20 development team at or the hydraulic engineer in your state. From the Open Plan dialog box select the plan that you want to open. From the Flow Analysis Window click on File menu and select Open Plan. Click on your desired location to split Subbasin_1, which should be located exactly on top of an identified streams grid cell. From Run menu click on Steady Flow Analysis or Unsteady Flow Analysis. You will notice your mouse cursor becomes a cross hair. Select the Subbasin_1 and click top menu of GIS, then Split Element. First make sure the Identified Streams layer is visible (menu View -> Map Layers…). Now we will demonstrate HEC-HMS Split Element capability.Make sure the filter set as “None” to calculate and display all subbasins and reaches. Use HEC-RAS to Develop Storage-Discharge Paired Data for Modified Puls Routing in HEC-HMS By Jimmy J0 Modified Puls Routing, also known as storage routing or level-pool routing, is a commonly used reach (channel) routing method in HEC-HMS. Click top menu of Parameters, then Characteristics -> Subbasin and Reach to re-calculate/update subbasin and reach characteristics parameters such as subbasin longest flowpath length, longest flowpath slope, and reach sinuosity.It is very important that your river stationing for the two reaches are. A new subbasin Subbasin_6 is created to replace Subbasin_4 and Subbasin_5 ( Figure 2). There is no combine two rivers option in HEC-RAS, but it can be done using the. Click top menu of GIS, then Merge Elements to combine the two selected subbasins.
First to merge Subasin_4 and Subasin_5: Make sure the mouse cursor is a pointer (or arrow), select Subasin_4 by clicking it on Basin Model Map View window Holding down the SHIFT key (or CTRL key), select Subasin_5 and now both subbasins should be highlighted as shown on Figure 1.Only two elements can be merged at one time. Reaches should have an upstream-downstream relationship. Subbasins can be side-by-side adjacent (if the merge produces a logical single outlet) or upstream-downstream so that the outlet for the merged sub-basin is the same as the lower subbasin. Subbasins and reaches must be adjacent to each other for the merge operation to work. Five subbasins and two reaches were delineated ( HEC-HMS project file of Post Part 1 of 3) and now we want to merge Subbasin_3, Subbasin_4 and Subbasin_5, as well as R_1 and R_2 reaches. After Bear Creek Watershed has been initially delineated using HEC-HMS GIS tools ( Post Part 1 of 3), the delineated subbasins and reaches can be further refined by HEC-HMS merge and split functions.