QGIS ReFH2 to TUFLOW: Difference between revisions

<br>

[[File:Plugin ReFH2 Menu.png|800px]]<br>

Once the ‘Extract ReFH2 for TUFLOW (beta)’ tool has been selected, the ReFH2 to TUFLOW Dialog will appear.

 

<br>

[[File:ReFH2 To TUFLOW Menu.png|800px]]<br>

The tool has a number of data input sections with the following headings associated with them:-

<ol>

<br>

[[File:ReFH2 Location.png|800px]]<br>

When using Catchment Descriptors, the area value from the XML file will be used. For Point Descriptors, there is no area value within the XML file, so the user is prompted to provide an area in km2. This can be user specified or can be taken from a GIS polygon specified in a later section.

<br>

<br>

[[File:ReFH2 Event Selection.png|800px]]<br>

The user can also specify a duration and a timestep. If no duration is specified, then the ReFH2 to TUFLOW tool will use the recommended duration determined by the ReFH2 software. The recommended duration is a function of the time to peak parameter (Tp) and the catchment average annual rainfall (SAAR). Once the duration is specified, an appropriate timestep is required that meets the requirement that the duration must be an odd multiple of the timestep. Table 1 below shows some common timesteps for some common durations. Where possible it is recommended a timestep between 10% and 20% of the duration should be used.

 

<br>

[[File:ReFH2 Input GIS.png|800px]]<br>

 

==Output==

<br>

[[File:ReFH2 Output.png|800px]]<br>

 

The other option is to output an inflow hydrograph which can be output to TUFLOW 1D_bc, 2D_bc and 2d_sa boundaries. The user can again select the rural and urban boundary types. There is also the option to select the inflow, ReFH2 calculates the total runoff as the sum of direct runoff and base flow. The direct runoff is obtained via a soil moisture accounting approach to convert rainfall to direct runoff. The base flow model is based on the linear reservoir concept.

Splitting up the runoff hydrographs allows the user to apply the direct runoff as a 2d_sa boundary to apply the flow over a region and then add the base flow as a point or line source elsewhere within the model domain.

When the tool is run, three csv files are output. The first is the raw output from ReFH2. This contains the timeseries of all the result parameters for the selected return periods of interest. This will have the same name as the XML file which is loaded into the ReFH2 to TUFLOW tool unless the ReFH2 Output File option is used to specify a different name and location for the file (for example, a TUFLOW bc_dbase folder).

<br>

[[File:ReFH2 Raw Output.png|800px]]<br>

A second csv file is the processed data for the output of interest (ie, net rainfall or direct runoff) for the return periods of interest. This file is named as the above raw file but has the suffix ‘_TUFLOW’. As well as only included the selected output time-series, the time format is converted from HH:MM:SS to hours which is the format used by TUFLOW. The first value in the time series is also set to Zero to be valid within a TUFLOW simulation.

<br>

[[File:ReFH2 Prcoessed Output.png|800px]]<br>

The third csv output is a bc_dbase.csv file which links the boundary name to the source csv. An optional Boundary name can be specified to specify the boundary ID which the hyetograph or hydrograph is applied to. When a GIS layer has been used as an input, the input feature will override this setting. This value, or the GIS layer feature, will provide the name for the boundary within the bc_dbase.csv file.

Column 1 references the ‘Time (hr)’ data in the processed time series csv file whereas column 2 will reflect the chosen output. Column 2 will contain the ~ARI~ wildcard, such that the column used will depend on the event simulated and specified in the batch file.

<br>

[[File:ReFH2 bc dbase file.png|800px]]<br>

A fourth file is also generated which is the TUFLOW Event File (TEF). This defines the event names together with the ~ARI~ wild card value which would be used in the bc_dbase.csv file to link the correct event with the boundary conditions. The use of TUFLOW event is described in a later section.

<br>

[[File:ReFH2 TEF.png|800px]]<br>

The zero padding option in the ReFH2 to TUFLOW tool determines how many zeros are added to the event name. For instance:-

• Choosing ‘no zero padding’ will set the event name to ‘1yr’.