TUFLOW file types
The table below lists the different types of and groups of files provided with this tutorial. These are listed below by file extension.
TABLE 1: 12da_to_from_mif Options (Switches)
Extension | Description |
---|---|
TUFLOW Text Based Input Files | |
".tcf" | TUFLOW Control File. A small, free form text file that controls the data flow and non-GIS parameters for a TUFLOW simulation. This is at the top of the tree for controlling a TUFLOW simulation. This is essential for every TUFLOW simulation. Can be colour coded in advanced text editors such as UltraEdit or NotePad++. The style is similar to writing a macro in Visual Basic. |
".ecf" | Similar to the .tcf, but for the 1D TUFLOW modelling inputs (Optional, not required for 2D only model). |
".tgc" | Similar to the .tcf, but controls the 2D topography related inputs (Mandatory). |
".tbc" | Similar to the .tcf, but controls the locations of the 2D boundaries (Mandatory). |
".tmf" ".csv" |
TUFLOW materials file, provides a database or lookup to assign Manning's n and other parameters (such as rainfall losses) to land use areas (material categories). |
TUFLOW Text Based Output Files | |
".tlf" | TUFLOW Log File. A text file which keeps a record of the simulation parameters and inputs. This file contains all of the information that is displayed on the DOS console window. This is a very useful file! |
".eof" | ESTRY Output File. A text file containing TUFLOW 1D inputs after processing all the 1D inputs. This file also contains the 1D outputs. Whilst this file is in and old style fixed field format it can be very useful for debugging a model by advanced users. |
TUFLOW Map Output Files | |
".2dm" | 2D Mesh File. This file contains information on the 2D cells and the triangulations between 1D Water Level Lines (WLLs) that allows viewing and animating of 1D and 2D results. This file can be imported to a number of viewing packages such as SMS, WaterRide, XP-SWMM and this file can be converted into a GIS package using the TUFLOW_to_GIS utility. This file designed to be used in conjunction with the .dat and/or .xmdf results files described below. |
".dat" | 2D Results File. This is a binary format results file. A separate .dat file is used for each result parameter, e.g. Depth, Level, Velocity, etc. results are all stored in individual .dat files. Can be converted into a GIS package using the free TUFLOW_to_GIS and DAT_to_DAT utilities. |
".xmdf" | 2D Results File. This is a binary format results file and uses HDF5 for cross-platform data storage and compression. For more inforamtion on the file format please see the XMDF wiki. Multiple parameters can be stored in a single XMDF file using a folder structure. |
".sup" | SMS Scatter Super File. This is a small text file that when opened by SMS will open the .2dm file followed by the relevant .dat or .xmdf file(s). This is a quick way of opening all these files in one operation. |
GIS Inputs and Outputs | |
".mif" ".mid" |
MapInfo Interchange Format files. The .mif and .mid files are a pair of files with the .mif file containing the projection, attribute fields and object information. The .mid file contains the attribute data. These files are used by TUFLOW to import and export GIS files for use in MapInfo. For more information please see the following page: MapInfo File Formats. They are text files and can be easily manipulated or created by customised software if required by advanced users. |
".tab" ".dat" ".map" ".id" ".ind" |
MapInfo Interchange Format files. The .mif and .mid files are a pair of files with the .mif file containing the projection, attribute fields and object information. The .mid file contains the attribute data. These files are used by TUFLOW to import and export GIS files for use in MapInfo. For more information please see the following page: MapInfo File Formats. They are text files and can be easily manipulated or created by customised software if required by advanced users. |