FLO2D to TUFLOW

Introduction

This page outlines some utilities that may be used to convert FLO2D model files into a format which compatible with TUFLOW. The utilities are available for download from the the TUFLOW website.
If you have any suggestions to be included in these pages, please email support@tuflow.com.

Model Conversion (flo2d_to_gis.exe)

The flo2d_to_gis.exe utility creates a complete TUFLOW model from FLO-2D model data. The utility converts the following data into a TUFLOW compatible format:

• Model origin, grid orientation, extent and resolution information
• Topography datasets
• Landuse delineation
• Storage adjustment features
• Width reduction factors (flow constriction features)
• Inflow/outflow locations
• Boundary condition timeseries data

These datasets are written to the standard TUFLOW model folder structure. TUFLOW control files are also output (tcf, tcg, tbc, boundary condition database).

Note: This utility is currently still in its beta testing phase. Output should be carefully quality checked.

Input Data Requirements

FLO-2D files are used as input by the utility. The minimum required file inputs include:
FPLAIN.DAT
CADPTS.DAT
INFLOW.DAT
OUTFLOW.DAT

FLO-2D floodplain area and width reduction data (ARF.DAT) can optionally be used.

The utility also requires GIS projection information. This is used to correctly translate the FLO-2D data to its real-world GIS location. This is discussed further in the following section.

TUFLOW Model Conversion (TMC) File

The TUFLOW Model Conversion (TMC) file is the control file for the model conversion. It is used to define the input files and projection information.

Required Inputs

• FLO-2D floodplain grid element data file: FLO2D FPLAIN == <Filename>
  
• FLO-2D co-ordinate point data file: FLO2D CADPTS == <Filename>
  
• FLO-2D inflow hydrograph data file: FLO2D INFLOW == <Filename>
  
• FLO-2D outflow hydrograph data file: FLO2D OUTFLOW == <Filename>
  
• Projection Data (four available options)
  

1. MI Projection == <coordinate line from .mif file>
2. MI Projection File == <link to .mif file used for setting projection>
3. SHP Projection == <coordinate line from .prj file>
4. SHP Projection File == <link to .prj file used for setting projection>
   
   

Optional Inputs

• FLO-2D floodplain area and width reduction data file: FLO2D ARF == <Filename>
  

The utility is currently limited to being run using a batch file. To create a batch file:

1. Create a new text file in the same location as the sdf file. The name is arbitrary but the file must have the extension ".bat". For example the file name could be "run_sdf_to_GIS.bat".
2. Enter the relevant command syntax to the batch file (refer to the 'Input Flags' table and examples provided below).
3. Double click the batch file in windows explore to execute the model conversion.
   

Input Flags

A list of the input switches is provided below:

Switch	Description
"-mif"	The output format will be the MapInfo Interchange format (.mif/.mid) recognised by most GIS software
"-shp"	The output format will be the ArcGIS Shapefile format. This can be opened directly in ArcMap, QGIS or SAGA (and most GIS software)
"-notrim	This command will prevent the utility from trimming cross-section data at levee markers. This is a non-default option due to most users converting HEC-RAS creek cross-section data into a TUFLOW 1D compatible format, whilst the surrounding floodplain in 2D areas are modeled in 2D (not requiring HEC-RAS inputs)

.

Example Syntax

Description: Convert HEC-RAS sdf data to mif format, trimming cross-section at levee markers (default trim option):

sdf_to_gis.exe -mif hecras_example.sdf

Description: Convert HEC-RAS sdf data to shp format, trimming cross-section at levee markers (default trim option):

sdf_to_gis.exe -shp hecras_example.sdf

Description: Convert HEC-RAS sdf data to mif format, not trimming cross-section at levee markers:

sdf_to_gis.exe -mif -notrim hecras_example.sdf

Description: Convert HEC-RAS sdf data to shp format, not trimming cross-section at levee markers:

sdf_to_gis.exe -shp -notrim hecras_example.sdf

Note The above listed syntax assumes that the sdf_to_gis.exe, hecras_example.sdf file and associated batch file are located within the same directory. If not the case, absolute file path referencing will be required. For example:

C:\TUFLOW\Utilities\HECRAS\sdf_to_gis.exe -mif -notrim hecras_example.sdf

Utility Output

sdf_to_gis.exe will output five GIS files and a series of csv files, one for each cross-section.

TUFLOW Input

1. 1d_xs_<sdf_filename>_surf_line:
   This dataset defines the location of the cross-sections. The file uses a format that is compatible with TUFLOW. The field attributes for "Source", "Type" and "Flags" have been pre-filled.
2. Cross-section csv files:
   This dataset defines the cross-section properties. Across channel distance, channel elevation and manning's roughness have been pre-filled with the csv datasets.

Check Files

1. <sdf_filename>_streams:
   This file defines the centerline of the channel. This centerline data can be split using the cross-section data to define the 1D channel (1d_nwk) in a TUFLOW model. The following field attributes should be used if this check file is converted into a TUFLOW input:
   1. "Len_or_ANA"= 0 (the length of the line/polyline is used).
   2. "n_or_n_F" = 1 (materials are being defined in the cross-section csv files. n_or_n_F is a multiplication factor of the cross-section manning’s n value).
   3. "US_Invert"= -99999 (the bed of the channel cross-section is used).
   4. "DS_Invert"= -99999 (the bed of the channel cross-section is used).
2. <sdf_filename>_cut_line:
   Echo of the cross-section line (non-trimmed).
3. <sdf_filename>_levee_pts:
   Points defining the intersection of the cross-section line with the levee used to trim the cross-section dataset.
4. <sdf_filename>_surf_line:
   Point dataset reporting the location of each elevation values within the csv cross-section dataset.