QGIS ReFH2 to TUFLOW - Revision history

Anne.Kolega: /* Output */ i.e.

2026-04-02T02:05:46Z

Output: i.e.

← Older revision		Revision as of 12:05, 2 April 2026
Line 119:		Line 119:
	[[File:ReFH2 Raw Output.png\|800px]]<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.		A second csv file is the processed data for the output of interest (i.e. 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>		<br>

Pavlina Monhartova: /* Output */

2024-08-08T01:27:56Z

Output

← Older revision		Revision as of 11:27, 8 August 2024
Line 141:		Line 141:
	The event name will be that which will need be specified in the batch file when using TUFLOW event files.		The event name will be that which will need be specified in the batch file when using TUFLOW event files.
	Finally, if the option to ‘Output to TUFLOW’ GIS is selected, then a GIS file in the correct TUFLOW boundary format containing the point, line or region will be created.		Finally, if the option to ‘Output to TUFLOW’ GIS is selected, then a GIS file in the correct TUFLOW boundary format containing the point, line or region will be created.
	These files can then be merged together by the user where multiple boundary conditions are required in the model domain ~~(future developments will allow this to be done automatically, as well as allow global rainfall to be applied)~~ and moved to the relevant TUFLOW model folders to be used within simulations.		These files can then be merged together by the user where multiple boundary conditions are required in the model domain and moved to the relevant TUFLOW model folders to be used within simulations.
	<br>		<br>

Pavlina Monhartova: /* ReFH2 Licensing */

2024-08-08T01:26:52Z

ReFH2 Licensing

← Older revision		Revision as of 11:26, 8 August 2024
Line 17:		Line 17:

	==ReFH2 Licensing==		==ReFH2 Licensing==
	In order to use the tool, ReFH2 Version 2.27059.19021 or later, must be installed on the local machine which can be downloaded from the following link (https://www.hydrosolutions.co.uk/software/refh-2/refh2_download/). The ReFH2 software requires the relevant local licence~~. Network licencing may be available in the future~~.		In order to use the tool, ReFH2 Version 2.27059.19021 or later, must be installed on the local machine which can be downloaded from the following link (https://www.hydrosolutions.co.uk/software/refh-2/refh2_download/). The ReFH2 software requires the relevant local licence.
	<br>		<br>

Tuflowduncan: /* Event Selection */

2023-09-25T18:57:32Z

Event Selection

← Older revision		Revision as of 04:57, 26 September 2023
Line 56:		Line 56:
	===Event Selection===		===Event Selection===

	Once the relevant location specific data has been input, then the user should first pick the ReFH2 model that they would like to use. The 'legacy' 2.2 and newer 2.3 ReFH2 models are available. In order to use the ReFH2.3 model ReFH2.3+ descriptor files, containing a new BFIHOST19 parameter, are required. If ReFH2.2 parameters are used with the ReFH2.3 engine, an error message will be flagged. The latest Catchment Descriptors contain information for the 2022 DDF model as well as the 2013 DDF model. The 2022 DDF model is recommended by CEH. However, the 2022 DDF parameters cannot be used with the legacy 2.2 ReFH2 model. Both 2013 and 2022 DDF parameters can be used with the 2.3 ReFH2 model. The default options are to use the 2022 DDF model witht he 2.3 ReFH2 model.		Once the relevant location specific data has been input, then the user should first pick the ReFH2 model that they would like to use. The 'legacy' 2.2 and newer 2.3 ReFH2 models are available. In order to use the ReFH2.3 model ReFH2.3+ descriptor files, containing a new BFIHOST19 parameter, are required. If ReFH2.2 parameters are used with the ReFH2.3 engine, an error message will be flagged. The latest Catchment Descriptors contain information for the 2022 DDF model as well as the 2013 DDF model. The 2022 DDF model is recommended by CEH. However, the 2022 DDF parameters cannot be used with the legacy 2.2 ReFH2 model. Both 2013 and 2022 DDF parameters can be used with the 2.3 ReFH2 model by specifying the desired option in the FEH Rainfall model section. The default options are to use the 2022 DDF model witht he 2.3 ReFH2 model.

	Once the ReFH2 engine version is selected, the user is then required to pick the events that they are interested in. The user can select from a number of pre-determined return periods or specify their own. All return period boundary conditions will be output in a single csv file for use as a TUFLOW boundary condition.		Once the ReFH2 engine version is selected, the user is then required to pick the events that they are interested in. The user can select from a number of pre-determined return periods or specify their own. All return period boundary conditions will be output in a single csv file for use as a TUFLOW boundary condition.

Tuflowduncan: /* FEH 2022 Rainfall */

2023-09-25T18:56:49Z

FEH 2022 Rainfall

← Older revision		Revision as of 04:56, 26 September 2023
Line 5:		Line 5:

	=FEH 2022 Rainfall=		=FEH 2022 Rainfall=
	FEH2022 is the most up-to-date Depth Duration Frequency (DDF) model for generating design rainfall hyetographs. CEH recommend the use of FEH2022, which supersedes the FEH2013 DDF model and therefore the 1999 method . In order to generate the design rainfall, the user obtains FEH2022 design rainfall depths from the FEH Web Service at https://fehweb.ceh.ac.uk for pre-defined return period/duration combinations. This requires a log on and user credits to purchase the data for the desired location. Data is available at a river catchment scale and as a point value. Both of these provide XML containing the rainfall depths. This is then imported into the ReFH2 software to generate hyetographs based on Flood Studies Report (FSR)/FEH approaches. The ~~current version of~~ ReFH2 (2.3) supports use of both the 2013 and 2022 DDF models. Version 2.2 only supports the 2013 DDF model		FEH2022 is the most up-to-date Depth Duration Frequency (DDF) model for generating design rainfall hyetographs. CEH recommend the use of FEH2022, which supersedes the FEH2013 DDF model and therefore the 1999 method . In order to generate the design rainfall, the user obtains FEH2022 design rainfall depths from the FEH Web Service at https://fehweb.ceh.ac.uk for pre-defined return period/duration combinations. This requires a log on and user credits to purchase the data for the desired location. Data is available at a river catchment scale and as a point value. Both of these provide XML containing the rainfall depths. This is then imported into the ReFH2 software to generate hyetographs based on Flood Studies Report (FSR)/FEH approaches. The ReFH2 2.3 model supports use of both the 2013 and 2022 DDF models. Version 2.2 only supports the 2013 DDF model, an error message will be generated should the user try to use the 2022 DDF rainfall with the 2.2 ReFH2 model.
	<br>		<br>

Tuflowduncan: /* Introduction */

2023-09-25T18:50:31Z

Introduction

← Older revision		Revision as of 04:50, 26 September 2023
Line 1:		Line 1:
	=Introduction=		=Introduction=

	Originally published in 1999, and subject to continuous development, the Flood Estimation Handbook (FEH) comprises the standard methods for estimating flood frequency in the UK. The rainfall-runoff model is one of two core handbook methods. In 2015, the Centre of Ecology and Hydrology (CEH) and Wallingford Hydro Solutions (http://www.hydrosolutions.co.uk) released a new version of the Revitalised Flood Hydrograph rainfall-runoff model (ReFH2) which allows users to generate design flows and hydrographs from given rainfall events for both catchment and development sites. ReFH2 is a rainfall-runoff model that takes inputs from the ~~FEH2013~~ web service (https://fehweb.ceh.ac.uk) and generates design rainfall events and provides a method for calculating design runoff from sites or contributing subcatchments. For a full description of the approaches, the reader is referred to their guidance which can be freely accessed at:- https://www.hydrosolutions.co.uk/support/refh2_faq/refh2_literature/. The ReFH2 method is available within the ReFH2 software. Version 3 of the ReFH2 software was released in 2020 which introduced a new model referred to as '2.3' with some changes to the ReFH2 models as well as support for climate-change adjusted rainfall, new default seasonality based on urban extent and use of the BFIHOST19 descriptor.		Originally published in 1999, and subject to continuous development, the Flood Estimation Handbook (FEH) comprises the standard methods for estimating flood frequency in the UK. The rainfall-runoff model is one of two core handbook methods. In 2015, the Centre of Ecology and Hydrology (CEH) and Wallingford Hydro Solutions (http://www.hydrosolutions.co.uk) released a new version of the Revitalised Flood Hydrograph rainfall-runoff model (ReFH2) which allows users to generate design flows and hydrographs from given rainfall events for both catchment and development sites. ReFH2 is a rainfall-runoff model that takes inputs from the FEH web service (https://fehweb.ceh.ac.uk) and generates design rainfall events and provides a method for calculating design runoff from sites or contributing subcatchments. For a full description of the approaches, the reader is referred to their guidance which can be freely accessed at:- https://www.hydrosolutions.co.uk/support/refh2_faq/refh2_literature/. The ReFH2 method is available within the ReFH2 software. Version 3 of the ReFH2 software was released in 2020 which introduced a new model referred to as '2.3' with some changes to the ReFH2 models as well as support for climate-change adjusted rainfall, new default seasonality based on urban extent and use of the BFIHOST19 descriptor.
	<br>		<br>

	=FEH ~~2013~~ Rainfall=		=FEH 2022 Rainfall=
	~~FEH2013~~ is the most up-to-date Depth Duration Frequency (DDF) model for generating design rainfall hyetographs. CEH recommend the use of ~~FEH2013~~, which supersedes the ~~FEH1999~~ method. In order to generate the design rainfall, the user obtains ~~FEH2013~~ design rainfall depths from the FEH Web Service at https://fehweb.ceh.ac.uk for pre-defined return period/duration combinations. This requires a log on and user credits to purchase the data for the desired location. Data is available at a river catchment scale and as a point value. Both of these provide XML containing the rainfall depths. This is then imported into the ReFH2 software to generate hyetographs based on Flood Studies Report (FSR)/FEH approaches.		FEH2022 is the most up-to-date Depth Duration Frequency (DDF) model for generating design rainfall hyetographs. CEH recommend the use of FEH2022, which supersedes the FEH2013 DDF model and therefore the 1999 method . In order to generate the design rainfall, the user obtains FEH2022 design rainfall depths from the FEH Web Service at https://fehweb.ceh.ac.uk for pre-defined return period/duration combinations. This requires a log on and user credits to purchase the data for the desired location. Data is available at a river catchment scale and as a point value. Both of these provide XML containing the rainfall depths. This is then imported into the ReFH2 software to generate hyetographs based on Flood Studies Report (FSR)/FEH approaches. The current version of ReFH2 (2.3) supports use of both the 2013 and 2022 DDF models. Version 2.2 only supports the 2013 DDF model
	<br>		<br>

Line 44:		Line 44:
	===Location===		===Location===

	The first section is where the XML files from the FEH2013 website are loaded into the tool. Both point descriptors and catchment descriptors are supported. The user can then specify whether the location is in England/Wales/Northern Ireland or in Scotland. The ReFH2 software includes Scotland specific algorithms to estimate model parameters from catchment descriptors. More information can be found in the ReFH2 Technical Report. If using the ReFH2.3 engine, the ReFH2.3+ descriptors which contain the BFIHOST19 value should be used. The ReFH2.3+ descriptors were added to the FEH Web Service in November 2019. If the BFIHOST19 parameter is omitted, the ReFH2 model used will ~~default~~ ~~to the 'legacy' 2.2 model~~.		The first section is where the XML files from the FEH2013 website are loaded into the tool. Both point descriptors and catchment descriptors are supported. The user can then specify whether the location is in England/Wales/Northern Ireland or in Scotland. The ReFH2 software includes Scotland specific algorithms to estimate model parameters from catchment descriptors. More information can be found in the ReFH2 Technical Report. If using the ReFH2.3 engine, the ReFH2.3+ descriptors which contain the BFIHOST19 value should be used. The ReFH2.3+ descriptors were added to the FEH Web Service in November 2019. If the BFIHOST19 parameter is omitted, the 'legacy' 2.2 ReFH2 model used will be needed.

	<br>		<br>
	[[File:ReFH2 Location.png\|400px]]<br>		[[File:ReFH2 Location.png\|400px]]<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 km<sup>2</sup>. This can be user specified or can be taken from a GIS polygon specified in a later section. If specifying an urban area, also in km<sup>2</sup>, this is used with Catchment Descriptors for Urban Outputs only. For point descriptors, the urban area is used for both Rural and Urban outputs. The urban area represents the mapped urbanised area within the catchment		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 km<sup>2</sup>. This can be user specified or can be taken from a GIS polygon specified in a later section. If specifying an urban area, also in km<sup>2</sup>, this is used with Catchment Descriptors for Urban Outputs only. For point descriptors, the urban area is used for both Rural and Urban outputs. The urban area represents the mapped urbanised area within the catchment.

	The user can also specify a user-defined Areal Reduction Factor which will override the calculated value by the ReFH2 software. If no value is supplied, the ARF calculated by the ReFH2 software will be used.		The user can also specify a user-defined Areal Reduction Factor which will override the calculated value by the ReFH2 software. If no value is supplied, the ARF calculated by the ReFH2 software will be used.
Line 56:		Line 56:
	===Event Selection===		===Event Selection===

	Once the relevant location specific data has been input, then the user should first pick the ReFH2 model that they would like to use. The 'legacy' 2.2 and newer 2.3 ReFH2 models are available. In order to use the ReFH2.3 model ReFH2.3+ descriptor files, containing a new BFIHOST19 parameter, are required. If ReFH2.2 parameters are used with the ReFH2.3 engine, an error message will be flagged.		Once the relevant location specific data has been input, then the user should first pick the ReFH2 model that they would like to use. The 'legacy' 2.2 and newer 2.3 ReFH2 models are available. In order to use the ReFH2.3 model ReFH2.3+ descriptor files, containing a new BFIHOST19 parameter, are required. If ReFH2.2 parameters are used with the ReFH2.3 engine, an error message will be flagged. The latest Catchment Descriptors contain information for the 2022 DDF model as well as the 2013 DDF model. The 2022 DDF model is recommended by CEH. However, the 2022 DDF parameters cannot be used with the legacy 2.2 ReFH2 model. Both 2013 and 2022 DDF parameters can be used with the 2.3 ReFH2 model. The default options are to use the 2022 DDF model witht he 2.3 ReFH2 model.

	Once the ReFH2 engine version is selected, the user is then required to pick the events that they are interested in. The user can select from a number of pre-determined return periods or specify their own. All return period boundary conditions will be output in a single csv file for use as a TUFLOW boundary condition.		Once the ReFH2 engine version is selected, the user is then required to pick the events that they are interested in. The user can select from a number of pre-determined return periods or specify their own. All return period boundary conditions will be output in a single csv file for use as a TUFLOW boundary condition.

	<br>		<br>
	[[File:ReFH2 Event Selection.png\|~~400px~~]]<br>		[[File:ReFH2 Event Selection 25 09 2023.png\|alt=\|400x400px]]<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.		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.

Chris Huxley at 22:51, 2 June 2021

2021-06-02T22:51:15Z

← Older revision		Revision as of 08:51, 3 June 2021
Line 171:		Line 171:
	<sup>1</sup> T.R. Kjeldsen, E.J. Stewart, J.C. Packman, S.S. Folwell & A.C. Bayliss, 2005. Revitalisation of the FSR/FEH rainfall-runoff method. Defra R&D Technical Report FD1913/TR <br>		<sup>1</sup> T.R. Kjeldsen, E.J. Stewart, J.C. Packman, S.S. Folwell & A.C. Bayliss, 2005. Revitalisation of the FSR/FEH rainfall-runoff method. Defra R&D Technical Report FD1913/TR <br>
	<sup>2</sup> Houghton-Carr, H., 1999. Restatement and application of the Flood Studies Report rainfall-runoff method, Flood Estimation Handbook Volume 4.		<sup>2</sup> Houghton-Carr, H., 1999. Restatement and application of the Flood Studies Report rainfall-runoff method, Flood Estimation Handbook Volume 4.
			<br>
			{{Tips Navigation
			\|uplink=[[TUFLOW_QGIS_Plugin#Usage\| Back to TUFLOW QGIS Plugin Main Page]]
			}}

Tuflowduncan: /* Output */

2021-03-25T11:02:17Z

Output

← Older revision		Revision as of 21:02, 25 March 2021
Line 136:		Line 136:

	The zero padding option in the ReFH2 to TUFLOW tool determines how many zeros are added to the event name. For instance:-		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’.		* Choosing ‘no zero padding’ will set the event name to ‘1yr’.
	• Choosing ‘Auto Pad with zeros’ will pad the event names so that all events have the same number of figures. For example if the 100 year event is the highest event, the 1 year event will be named ‘001yr’, if the 1000year event is the largest, the 1 year event will be named ‘0001yr’.		* Choosing ‘Auto Pad with zeros’ will pad the event names so that all events have the same number of figures. For example if the 100 year event is the highest event, the 1 year event will be named ‘001yr’, if the 1000year event is the largest, the 1 year event will be named ‘0001yr’.
	• Choosing a value will set the padding to that many zeros, for instance 3, will set the name to ‘0001yr’.		* Choosing a value will set the padding to that many zeros, for instance 3, will set the name to ‘0001yr’.
	The event name will be that which will need be specified in the batch file when using TUFLOW event files.		The event name will be that which will need be specified in the batch file when using TUFLOW event files.
	Finally, if the option to ‘Output to TUFLOW’ GIS is selected, then a GIS file in the correct TUFLOW boundary format containing the point, line or region will be created.		Finally, if the option to ‘Output to TUFLOW’ GIS is selected, then a GIS file in the correct TUFLOW boundary format containing the point, line or region will be created.

Tuflowduncan: /* Output */

2021-03-25T09:48:18Z

Output

← Older revision		Revision as of 19:48, 25 March 2021
Line 133:		Line 133:

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

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

Tuflowduncan: /* Output */

2021-03-25T09:47:50Z

Output

← Older revision		Revision as of 19:47, 25 March 2021
Line 108:		Line 108:
	Rainfall outputs can be applied as 2d_rf or 2d_sa_rf TUFLOW boundaries. The user selects whether they want to use the Gross Design Rainfall, or the Net Design Rainfall where the ReFH2 losses have been applied. The former would usually be applied to TUFLOW with some allowance for losses within TUFLOW, most commonly via 2D Infiltration. The latter will have ReFH2 losses already accounted for so additional losses would not usually be required.		Rainfall outputs can be applied as 2d_rf or 2d_sa_rf TUFLOW boundaries. The user selects whether they want to use the Gross Design Rainfall, or the Net Design Rainfall where the ReFH2 losses have been applied. The former would usually be applied to TUFLOW with some allowance for losses within TUFLOW, most commonly via 2D Infiltration. The latter will have ReFH2 losses already accounted for so additional losses would not usually be required.
	As well as the option to specify Gross or Net rainfall, the user can also select the rainfall type. The options are rural and urban. The rural rainfall is the default option which would represent the situation were the subcatchment 100% rural whereas the urban rainfall allows the representation of the URBEXT2000 parameter or Urban Area if specified in the 'Location' section. Further control over the impact of urbanisation can be carried out within the ReFH2 software. Note, that this option will only affect the Net Design Rainfall, it will have no impact on the Gross Design Rainfall. The output in both cases is the Total net rain mm (ARI) which for the rural model is 100% rural and with the urban model is the sum of the Urban net rain mm (ARI) and the Rural net rain mm (ARI). When using point descriptors, it is important to specify an appropriate Urban Extent in the 'Location' section to derive the correct losses for the study area.		As well as the option to specify Gross or Net rainfall, the user can also select the rainfall type. The options are rural and urban. The rural rainfall is the default option which would represent the situation were the subcatchment 100% rural whereas the urban rainfall allows the representation of the URBEXT2000 parameter or Urban Area if specified in the 'Location' section. Further control over the impact of urbanisation can be carried out within the ReFH2 software. Note, that this option will only affect the Net Design Rainfall, it will have no impact on the Gross Design Rainfall. The output in both cases is the Total net rain mm (ARI) which for the rural model is 100% rural and with the urban model is the sum of the Urban net rain mm (ARI) and the Rural net rain mm (ARI). When using point descriptors, it is important to specify an appropriate Urban Extent in the 'Location' section to derive the correct losses for the study area.

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