QGIS ARR2016 to TUFLOW

From Tuflow
Jump to: navigation, search

Introduction

The ARR2016 to TUFLOW utility has been developed to help users set up a TUFLOW model that uses ARR2016 input parameters and BOM 2016 rainfall by automating the collection and processing of the data. The inputs and outputs of the tool are explained in detail below.

It should be noted this tool helps with data processing, however is not a substitute to reading ARR2016 and understanding the outputs, how to use them correctly and their limitations. Please see the ARR2016 Website for more information.

If you experience any problems, please email through a description of the problem and the log.txt file to support@tuflow.com

How to Run

This tool is a part of the QGIS plugin tool set and can be initiated through the plugin.
ARR2016 initiate.PNG
QGIS ARR2016 Main Dialog.PNG

  1. Input GIS catchment layer:
    Catchment layer to extract data for. The tool will use the geographical location of the catchment layer for data extraction from the ARR2016 datahub and BOM 2016 rainfall. The catchment layer is able to have multiple features (i.e. a number of subcatchments) and will extract data for each feature.This layer can be either a point or polygon layer. For polygon layers, the polygon centroid is used for geographical data extraction, and the area is used for ARF calculations. For point layers, ARF calculations cannot be automated.

  2. Unique Catchment Identifier:
    The unique catchment identifier is used as the name for the inflow in the TUFLOW model. When extracting data for multiple subcatchments, it is important to have unique identifiers otherwise data will be overwritten if identical names have been used.

  3. Event Selection:
    Select at least one event magnitude and one event duration.

  4. Climate Change Selection:
    Optional climate change parameters. If choosing to include climate change, one year and one RCP must be selected.

  5. Output Options:
    Output options include:
    • Selecting the format of the inflow files (*.csv or *.ts1)
    • Selecting the output notation#:
      • % AEP - e.g. 10p60m
      • yr ARI - e.g. 10y60m
      • # Frequent events (EY) will be denoted with e regardless of above options e.g. 12e60m. The only exception is the 0.5EY and 0.2EY which will be converted to 2y and 5y respectively when using yr ARI

  6. Areal Reduction Factor:
    Choose the method of area calculation for the ARF:
    • Calculate area from input catchment - the area will be calculated automatically using QGIS (this option can only be used with polygon input layers)
    • Manually Specify Area by attribute field - the area can be specified using an attribute field in the input GIS layer. The field containing the area values can be selected using the dropdown box
    • To ignore ARF, use Manually Specify Area and select -None- in the dropdown box
    The option to change the minimum ARF is also available. The default value is 0.2.

  7. Optional additional temporal patterns
    The tool allows the option of adding additional temporal patterns from other regions. This could be useful if your site is on the border of multiple regions and sensitivity with neighbouring temporal patterns is required. The option allows selection of as many additional temporal patterns as desired.

  8. Initial Loss Options
    • Option to choose the preburst percentile (default is median). The initial loss is calculated by Storm Loss minus Preburst.
    • Option to choose methods for calculating initial loss for durations less than 60 mins.
      • Interpolate to Zero: Assumes an initial loss of 0 mm for a duration of 0 mins and interpolates for values between the 60 min duration and the 0 min duration.
      • Rahman et al 2002: From a study of 11 Victorian catchments (source link)
      • Hill et al 1996: 1998 (source 1996, source 1998)
      • Static Value: User defined value for initial loss for durations less than 60min
      • Use 60 min Loss: Adopt 60 min loss for durations less than 60 min

  9. BOM Terms and Conditions:
    By selecting these, you agree to BOM's Conditions and Caveat (required to run run the utility)

  10. Output Location:
    User defined folder where the outputs and log file of the utility will be written to



Log File

The log.txt file is written out into the same location as the other outputs and contains WARNING and ERROR messages from the tool.

The log.txt file is very important and should be checked after running the tool to check whether it has successfully run.

The QGIS utility calls an external Python script and once the script has completed (whether successfully or unsuccessfully) QGIS will report the process as complete. Therefore the user must check the log.txt file to check whether there has been any errors.

How to Read

  1. The first thing the log file will output is the version of the ARR_to_TUFLOW python script
    QGIS ARR2016 log header text.png
  2. The next item written will be a list of the inputs
    QGIS ARR2016 log inputs.png
  3. Following this will be a description of the function the utility is performing - e.g. extracting BOM data
  4. The last part is the most important and is where ERRORs and WARNINGs are written
    QGIS ARR2016 log errors warnings.png

If reading in more than one catchment, each catchment extraction is a separate process and will be appended to the log.txt file.

Data Output

The following outputs are located in the folder <output_folder>\data

  1. Raw BOM and ARR Datahub outputs
    • The raw data extracted from ARR2016 datahub and BOM2016 IFD
      • ARR_Web_data_<catchment_name>.txt
      • BOM_raw_web_<catchment_name>.html
  2. Rainfall depths
    • Processed rainfall depths after Areal Reduction Factors have been applied
      • BOM_Rainfall_Depths_<catchment_name>.csv
  3. ARF Factors
    • Calculated ARF factors applied to the rainfall depths
      • <catchment_name>_ARF_Factors.csv
  4. Storm Burst Rainfall Losses
    • Calculated Storm Burst Initial Rainfall Losses (Complete Storm Initial Loss - Preburst Rainfall Depth)
      • <catchment_name>_Burst_Initial_Loss.csv

TUFLOW Output

The following outputs are generated by the utility in TUFLOW format:

  1. Rainfall Inflows
    • The rainfall inflows are output in the following location <output_folder>\rf_inflows. This output folder is where all the direct rainfall inflows that would be used in the TUFLOW model are output. An inflow file is generated for each event magnitude - duration combination. All available temporal patterns are included in a single file (including climate change options).
      • <catchment_name>_RF_<magnitude><duration>.csv
  2. BC_Dbase
    • TUFLOW boundary condition database. Setup to point to the RF folder with wildcards applied.
      • bc_dbase.csv
  3. Tuflow Event File
    • TUFLOW Event File. Setup with wildcards applied. To keep the file names from becoming overly long and complicated, Climate Change scenarios are labelled as CC1, CC2.. etc. These correspond to the combinations of climate change scenarios requested by the user e.g. 2090_8.5 (climate change year: 2090, RCP: 8.5)
      • Event_File.tef

An example of a naming convention that could be used with the ARR2016 output is: <Model_Name>_~e1~~e2~_~e3~_~s1~_00X.tcf where

  • e1 = Event magnitude
  • e2 = Event duration
  • e3 = climate change scenario
  • s1 = user defined scenario switch

For example M01_10p60m_CC1_EXG_001.tcf

Future Enhancements

  1. Automatic output to user choice of TUFLOW rainfall loss - infiltration / rainfall excess

Can't access websites

For whatever reasons, sometimes the BOM or ARR Datahub websites are down or unable to be accessed by the tool. The below are a set of instructions that can be used as a workaround should this occur: