HEC-RAS to TUFLOW: Difference between revisions

Content deleted Content added
 
(27 intermediate revisions by 7 users not shown)
Line 1:
=Introduction=
This page outlines some utilities that may be used to convert HEC-RAS model files into a format which is compatible with TUFLOW. <br>If you have any suggestions to be included in these pages, please emailcontact <font color="blue"><u>[mailto:support@tuflow.com support@tuflow.com]</u></font>.<br><br>
 
= Geometry Conversion (sdf_to_gis.exe) =
The sdf_to_gisHECRAS_to_TUFLOW.exe utility is available for download from the TUFLOW <u>[httphttps://www.tuflow.com/Tuflow%20Tutorial%20Models.aspxdownloads/#utilities website]</u>, it
converts HEC-RAS geometric data into a TUFLOW compatible GIS (mif and shp) and csv input format. The utility outputs include:
<ol>
<li> Centerline location data in GIS format
Line 10:
<li> Cross-section data in csv format
</ol>
 
''Note: This utility is currently still in its beta testing phase. Output should be carefully quality checked. ''
<br>
 
[[File:HECRAS_SDF_Output_002.JPG|600px]]
Line 24 ⟶ 21:
<li> Double click the batch file in windows explorer to execute the model conversion
</ol>
 
 
 
== Input Data Processing ==
Line 48 ⟶ 43:
 
[[File:HECRAS_SDF_Selection.JPG|600px]]
<br>
 
== Utility Execution ==
Line 60 ⟶ 56:
The utility is currently limited to being run using a batch file. To create a batch file:
<ol>
<li> 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".
<li> Enter the relevant command syntax to the batch file (refer to the 'Input Flags' table and examples provided below).
<li>Double click the batch file in windows explore to execute the model conversion.<br>
Line 73 ⟶ 69:
|"-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, OR 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 ===
Line 93 ⟶ 89:
<u>Note</u> 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:
<li><tt>C:\TUFLOW\Utilities\HECRAS\sdf_to_gis.exe -mif -notrim hecras_example.sdf</tt></li>
<br>
 
== Utility Output ==
Line 123 ⟶ 118:
<li> ''<sdf_filename>_surf_line'': <br>
Point dataset reporting the location of each elevation values within the csv cross-section dataset.
</ol><br>
 
= Geometry Conversion (miTools) =
MiTools is a MapInfo add-on that is available for download from the TUFLOW <u>[httphttps://www.tuflow.com/miToolsTuflow%20Latest%20Release20Utilities.aspx website]</u>.
MiTools can be used to convert HEC-RAS geometry cross-section data into mif/mid spatial and csv tabular format for direct input into TUFLOW.<br><br>
The tool provides various user options, such as:
Line 135 ⟶ 130:
 
Refer to the <u>[[miTools_Tips | miTools Tips and Tricks]]</u> section for more information about miTools.
<br><br>
 
= Boundary Conditions (HEC-DSS) =
The 2023 TUFLOW Release introduced support for time-series data from HEC-DSS files within a TUFLOW boundary condition database.
 
HEC-DSS is a database system for time series, curve, gridded data and more, developed by the U.S. Army Corps of Engineers Hydrologic Engineering Center (HEC). See their website at https://www.hec.usace.army.mil/software/hec-dss/ for more information. The format is used for HEC developed software for data input and output. Rather than convert HEC-DSS time-series curves for use in TUFLOW, DSS data used by a HEC-RAS model can now also be used directly in TUFLOW.<br>
 
HEC-DSS files organise data into paths with six parts (Part A – Part F) that resemble how files are organised on disk. The image below shows an example DSS file with a single path, with the curve plotted below.<br>
[[File:HEC_DSSVue.png]]
 
To use a HEC-DSS time-series curve within a TUFLOW model, save a copy of the HEC-DSS input file to the TUFLOW bc_dbase folder and enter the following information into the TUFLOW boundary condition database:
<ol>
<li> Enter the TUFLOW boundary condition location ID in the "Name" column.
<li> Provide the HEC-DSS filename in the “Source” column.
<li> Leave “Column 1”, which is used for time, blank (DSS files store the time with the curve values).
<li> Identify the pathname in “Column 2”. Event placeholders such as __event__ can be used as part of the pathname. Wilcards (*) can be used for parts of the path, however, ensure the wildcards will not select more than one path within the file.
<li> The “Add” and “Mult” columns can be used to offset or scale the time-series values, the same as non-DSS time-series curves.
</ol>
The image below shows how the time-series curve above could be included in a boundary condition database. A wildcard is used for “Column 2” of the pathname (date range). Note that the pathname must start with a forward slash (/).
<tt>Name, Source, Column 1, Column 2, Add Col 1, Mult Col 2, Add Col 2, Column 3, Column 4
FC01, EG.dss, , /Example/EG01/FLOW/*/5Minute/BC/, , , , , </tt>
By default, TUFLOW uses the first point in the time-series curve as TUFLOW time-zero. This can be changed using the TCF command “HEC-DSS Start Date” to identify the date/time that should be used for time-zero. The date should be in the isodate format: yyyy-mm-dd hh:mm:ss, where the time portions are optional.<br>
:<font color="blue"><tt>HEC-DSS Start Date </tt></font> <font color="red"><tt>== </tt></font> <tt>2022-01-01</tt> <br>
Note: Non-time series data such as gridded data from a HEC-DSS file is not supported at this time. Contact [mailto:support@tuflow.com support@tuflow.com] to request other features that would be beneficial to your workflows.
 
<br>
 
=Frequently Asked Questions (FAQ)=
==Is there a way to transfer a complete HEC-RAS 2D model directly to TUFLOW?==
For 2D HEC-RAS models, we recommend requesting the raw input datasets used in the HEC-RAS model, if possible, and then reconstructing a TUFLOW model from scratch. We have found that this method is easier and results in higher quality data input for TUFLOW, as opposed to using data that has been downscaled to the HEC-RAS grid resolution. Additionally, HEC-RAS and TUFLOW use different grid mesh formations, which makes a direct automated conversion impractical.
<br>
 
{{Tips Navigation
= Boundary Condition Conversion =
|uplink=[[Main_Page| Back to Main Page]]
coming soon
}}