Difference between revisions of "TUFLOW Viewer - Load Results - Map Outputs"
Jump to navigation
Jump to search
Ellis Symons (talk | contribs) (Created page with "===Tool=== ===Examples=== ===Links=== * Load Results * Back to TUFLOW Viewer Main Page") |
Ellis Symons (talk | contribs) |
||
| Line 1: | Line 1: | ||
===Tool=== | ===Tool=== | ||
| + | Loads "map output" results (i.e. the 2D or 3D results). The following file formats are accepted as inputs: | ||
| + | * '''*.xmdf''' - XMDF files are the preferred output mesh format for TUFLOW Classic / HPC | ||
| + | * '''*.dat''' - DAT files are limited to a single output type (e.g. depth) and miss out on some of the advanced loading mechanics that QGIS employs that greatly reduce load times, memory footprint etc. For this reason it is recommended to use XMDF format which can be output directly from TUFLOW. | ||
| + | * '''*.nc''' - NetCDF mesh outputs are currently unsupported in TUFLOW Classic / HPC and only available from TUFLOW FV. This file format supports both 2D and 3D outputs. TUFLOW Classic / HPC does support a NetCDF grid output and NetCDF cell centred output, however these formats are not yet supported in TUFLOW Viewer. | ||
| + | * '''*.xmdf.sup''' - This file is a text file that lists the location of the XMDF and 2DM files. This is typically used for TUFLOW FV outputs as the *.2dm (mesh file) is typically built separately and used as an input to the model and therefore will be located separately to the XMDF. For TUFLOW Classic / HPC results the 2DM is generated as an output and stored along side the XMDF and TUFLOW Viewer will find it automatically. | ||
| + | * '''*.dat.sup''' - This file is a text file that lists the location of all DAT files and 2DM file. This can be used to bring in all DAT results at once. Superficially TUFLOW Viewer will treat this differently than loading in all DAT files individually - when loading in from a *.dat.sup file, TUFLOW Viewer will group the results and treat them as one (similar to how an XMDF is treated). | ||
===Examples=== | ===Examples=== | ||
| + | |||
===Links=== | ===Links=== | ||
* [[TUFLOW_Viewer_-_Load_Results | Load Results]] | * [[TUFLOW_Viewer_-_Load_Results | Load Results]] | ||
* [[TUFLOW_Viewer#Loading_Results | Back to TUFLOW Viewer Main Page]] | * [[TUFLOW_Viewer#Loading_Results | Back to TUFLOW Viewer Main Page]] | ||
Revision as of 02:25, 23 February 2021
Tool
Loads "map output" results (i.e. the 2D or 3D results). The following file formats are accepted as inputs:
- *.xmdf - XMDF files are the preferred output mesh format for TUFLOW Classic / HPC
- *.dat - DAT files are limited to a single output type (e.g. depth) and miss out on some of the advanced loading mechanics that QGIS employs that greatly reduce load times, memory footprint etc. For this reason it is recommended to use XMDF format which can be output directly from TUFLOW.
- *.nc - NetCDF mesh outputs are currently unsupported in TUFLOW Classic / HPC and only available from TUFLOW FV. This file format supports both 2D and 3D outputs. TUFLOW Classic / HPC does support a NetCDF grid output and NetCDF cell centred output, however these formats are not yet supported in TUFLOW Viewer.
- *.xmdf.sup - This file is a text file that lists the location of the XMDF and 2DM files. This is typically used for TUFLOW FV outputs as the *.2dm (mesh file) is typically built separately and used as an input to the model and therefore will be located separately to the XMDF. For TUFLOW Classic / HPC results the 2DM is generated as an output and stored along side the XMDF and TUFLOW Viewer will find it automatically.
- *.dat.sup - This file is a text file that lists the location of all DAT files and 2DM file. This can be used to bring in all DAT results at once. Superficially TUFLOW Viewer will treat this differently than loading in all DAT files individually - when loading in from a *.dat.sup file, TUFLOW Viewer will group the results and treat them as one (similar to how an XMDF is treated).