QGIS ReFH2 to TUFLOW: Difference between revisions
Content deleted Content added
Tuflowduncan (talk | contribs) |
Tuflowduncan (talk | contribs) |
||
Line 25:
<br>
[[File:Plugin ReFH2 Menu.png|
<br>
Line 31:
<br>
[[File:ReFH2 To TUFLOW Menu.png|
<br>
Line 50:
<br>
[[File:ReFH2 Location.png|
<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.
Line 60:
<br>
[[File:ReFH2 Event Selection.png|
<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.
Line 98:
<br>
[[File:ReFH2 Input GIS.png|
<br>
Line 107:
<br>
[[File:ReFH2 Output.png|
<br>
Line 116:
<br>
[[File:ReFH2 Raw Output.png|
<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|
<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.
Line 127:
<br>
[[File:ReFH2 bc dbase file.png|
<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|
<br>
The zero padding option in the ReFH2 to TUFLOW tool determines how many zeros are added to the event name. For instance:-
| |||