TUFLOW Check Files - Revision history

Anne.Kolega: e.g.

2026-04-01T04:39:42Z

e.g.

← Older revision		Revision as of 14:39, 1 April 2026
Line 67:		Line 67:
	\| [[Check_Files_2d_glo \| _glo_check]]\|\| GIS layer of any gauge level output (GLO) locations.		\| [[Check_Files_2d_glo \| _glo_check]]\|\| GIS layer of any gauge level output (GLO) locations.
	\|-		\|-
	\| [[Check_Files_2d_grd \| _grd_check]]\|\| GIS layer of the final 2D grid. Represents the final grid including modifications from the .tgc file, boundary specifications and flow constrictions. Note that the Material and bed resistance (eg. Mannings_n) attributes do not include any modifications due to flow constrictions as these are applied directly to the cell mid-sides (rather than the cell centre). To view these use the [[Check_Files_2d_uvpt\|_uvpt_check]] file.<br>		\| [[Check_Files_2d_grd \| _grd_check]]\|\| GIS layer of the final 2D grid. Represents the final grid including modifications from the .tgc file, boundary specifications and flow constrictions. Note that the Material and bed resistance (e.g. Mannings_n) attributes do not include any modifications due to flow constrictions as these are applied directly to the cell mid-sides (rather than the cell centre). To view these use the [[Check_Files_2d_uvpt\|_uvpt_check]] file.<br>
	Can also be written at different stages within a .tgc file (see <font color="blue"><tt>Write GIS Grid </tt></font> <font color="red"><tt>==</tt></font> command). The file contains all modifications to the 2D grid at the point in the .tgc file that it is written. <br>		Can also be written at different stages within a .tgc file (see <font color="blue"><tt>Write GIS Grid </tt></font> <font color="red"><tt>==</tt></font> command). The file contains all modifications to the 2D grid at the point in the .tgc file that it is written. <br>
	Note that a number of additional attributes are appended to the_grd_check layer when some features of TUFLOW have been used.		Note that a number of additional attributes are appended to the_grd_check layer when some features of TUFLOW have been used.

Anne.Kolega: /* 2D Check Files */ e.g.

2026-03-30T04:23:41Z

2D Check Files: e.g.

← Older revision		Revision as of 14:23, 30 March 2026
Line 38:		Line 38:
	!colspan="2" \| Tabular Check Files		!colspan="2" \| Tabular Check Files
	\|-		\|-
	\| [[Check_Files_2d_bc_tables \| _2d_bc_tables_check]]\|\| Tabular data as read from the boundary condition database via any 2d_bc layers and after any adjustments (eg. time shift). Provides traceability to original data source. '''Note: the boundary values do not include the effects of any 2d_bc attributes such as f.'''		\| [[Check_Files_2d_bc_tables \| _2d_bc_tables_check]]\|\| Tabular data as read from the boundary condition database via any 2d_bc layers and after any adjustments (e.g. time shift). Provides traceability to original data source. '''Note: the boundary values do not include the effects of any 2d_bc attributes such as f.'''
	\|-		\|-
	!colspan="2" \| Raster Check Files		!colspan="2" \| Raster Check Files

Anne.Kolega: /* 1D Check Files */

2026-02-17T03:03:48Z

1D Check Files

← Older revision		Revision as of 13:03, 17 February 2026
Line 127:		Line 127:
	Any generated pit channels are shown as a small channel flowing from north to south into the pit node. The upstream pit channel node that is generated is also shown. The length of the pit channel is controlled by <font color="blue"><tt>Pit Channel Offset </tt></font> <font color="red"><tt>==</tt></font> command.		Any generated pit channels are shown as a small channel flowing from north to south into the pit node. The upstream pit channel node that is generated is also shown. The length of the pit channel is controlled by <font color="blue"><tt>Pit Channel Offset </tt></font> <font color="red"><tt>==</tt></font> command.
	\|-		\|-
	\| [[Check_Files_1d_nwk_N \| _nwk_N_check]]\|\| GIS layer of the final 1D model network. ~~This file is very valuable for check if the nodes are snapped.~~ <br>		\| [[Check_Files_1d_nwk_N \| _nwk_N_check]]\|\| GIS layer of the final 1D model network. <br>
	'''This is very useful for checking for channel ends or nodes that are not snapped.'''<br>		'''This is very useful for checking for channel ends or nodes that are not snapped.'''<br>
	\|-		\|-

Anne.Kolega: /* 1D Check Files */

2026-02-17T03:02:34Z

1D Check Files

← Older revision		Revision as of 13:02, 17 February 2026
Line 127:		Line 127:
	Any generated pit channels are shown as a small channel flowing from north to south into the pit node. The upstream pit channel node that is generated is also shown. The length of the pit channel is controlled by <font color="blue"><tt>Pit Channel Offset </tt></font> <font color="red"><tt>==</tt></font> command.		Any generated pit channels are shown as a small channel flowing from north to south into the pit node. The upstream pit channel node that is generated is also shown. The length of the pit channel is controlled by <font color="blue"><tt>Pit Channel Offset </tt></font> <font color="red"><tt>==</tt></font> command.
	\|-		\|-
	\| [[Check_Files_1d_nwk_N \| _nwk_N_check]]\|\| GIS layer of the final 1D model network. ~~The~~ ~~attributes~~ ~~provide~~ ~~information~~ on ~~which~~ ~~nodes~~ ~~and~~ ~~channels are~~ ~~upstream~~ or ~~downstream,~~ ~~hence provide an information on the network, etc.~~<br>		\| [[Check_Files_1d_nwk_N \| _nwk_N_check]]\|\| GIS layer of the final 1D model network. This file is very valuable for check if the nodes are snapped. <br>
	'''This is very useful for checking for channel ends or nodes that are not snapped.'''<br>		'''This is very useful for checking for channel ends or nodes that are not snapped.'''<br>
	\|-		\|-
	\| [[ Check_Files_1d_pit_A \|_pit_A_check]]\|\| GIS layer of the 1D pit details.		\| [[ Check_Files_1d_pit_A \|_pit_A_check]]\|\| GIS layer of the 1D pit details.
	\|-		\|-
	\| [[Check_Files_1d_WLLo \| _WLLo_check<br>_xWLLo_check]]\|\| GIS layer of all the WLL objects read. The attributes provide information on which nodes ~~that~~ ~~area~~ ~~associated~~ ~~with~~, etc. <br>		\| [[Check_Files_1d_WLLo \| _WLLo_check<br>_xWLLo_check]]\|\| GIS layer of all the WLL objects read. The attributes provide information on which nodes and channels are upstream or downstream, hence provide an information on the network, etc.<br>
	The _WLLo_check layers are written for ESTRY 1D domains, whereas the _xWLLo_check layers are written for external 1D domains, such as Flood Modeller or XP-SWMM.		The _WLLo_check layers are written for ESTRY 1D domains, whereas the _xWLLo_check layers are written for external 1D domains, such as Flood Modeller or XP-SWMM.
	\|-		\|-

Anne.Kolega: /* 1D Check Files */ corrected grammar

2026-02-17T02:59:04Z

1D Check Files: corrected grammar

← Older revision		Revision as of 12:59, 17 February 2026
Line 127:		Line 127:
	Any generated pit channels are shown as a small channel flowing from north to south into the pit node. The upstream pit channel node that is generated is also shown. The length of the pit channel is controlled by <font color="blue"><tt>Pit Channel Offset </tt></font> <font color="red"><tt>==</tt></font> command.		Any generated pit channels are shown as a small channel flowing from north to south into the pit node. The upstream pit channel node that is generated is also shown. The length of the pit channel is controlled by <font color="blue"><tt>Pit Channel Offset </tt></font> <font color="red"><tt>==</tt></font> command.
	\|-		\|-
	\| [[Check_Files_1d_nwk_N \| _nwk_N_check]]\|\| GIS layer of the final 1D model network. ~~This~~ ~~check~~ ~~layer~~ ~~contains~~ ~~the~~ nodes of ~~the~~ 1D ~~domain~~ ~~only.~~ ~~The~~ ~~_nwk_C_check~~ ~~layer~~ ~~contains~~ the ~~channels~~.<br>		\| [[Check_Files_1d_nwk_N \| _nwk_N_check]]\|\| GIS layer of the final 1D model network. The attributes provide information on which nodes and channels are upstream or downstream, hence provide an information on the network, etc.<br>
	'''This is very useful for checking for channel ends or nodes that are not snapped.'''<br>		'''This is very useful for checking for channel ends or nodes that are not snapped.'''<br>
	\|-		\|-

Emilie Nielsen: /* Tips for Visualising Check Files */

2026-02-16T05:45:04Z

Tips for Visualising Check Files

← Older revision		Revision as of 15:45, 16 February 2026
Line 19:		Line 19:
	<br>		<br>
	=Tips for Visualising Check Files=		=Tips for Visualising Check Files=
	Depending on the size of the model, the check files may contain a large amount of data, ~~for~~ example the _grd_check file may contain thousands or millions of cells. As a ~~modeller~~ ~~you~~ ~~probably won't~~ inspect each cell to ~~ensure~~ ~~that~~ the ~~data~~ is ~~value,~~ ~~however~~ ~~you~~ ~~may~~ ~~want~~ to ~~view~~ ~~this~~ ~~for~~ ~~the~~ ~~entire~~ ~~model.~~ ~~Thematic~~ ~~mapping~~ or ~~styling~~ ~~the~~ ~~input~~ ~~layers~~ ~~can~~ be ~~used~~ in ~~your~~ GIS software to do ~~this.~~		Depending on the size of the model, the check files may contain a large amount of data. For example, the [[Check_Files_2d_grd\|_grd_check]] file may contain thousands or millions of cells. It is not typically practical to inspect each cell, however reviewing the dataset across the entire model is often useful. This can be achieved using thematic mapping or layer styling tools within GIS software. For example, using the styling functionality (thematic mapping) of GIS software, the user could:
			*View the spatial distribution of the Soil Infiltration layer (attribute in [[Check_Files_2d_grd\|_grd_check]] layer).
	Some tips are given below for a range of GIS platforms, however, the functionality is likely to be available in almost all GIS platforms:<br>
			*View the conveyance of 1D channel layers (attribute in [[Check_Files_1d_hydroprop\|_hydroprop_check]] layer).
⚫	* [[MapInfo_Style_Check_Files \| MapInfo style check files]]


		⚫	Some tips are provided for MapInfo style check files: [[MapInfo_Style_Check_Files \| MapInfo style check files]]

	=Check File Types=		=Check File Types=

Emilie Nielsen: /* 2D / 1D Check Files */

2025-07-07T04:31:03Z

2D / 1D Check Files

← Older revision		Revision as of 14:31, 7 July 2025
Line 157:		Line 157:
	\| [[Check_Files_1d_to_2d_bc \| _1d_to_2d_check]]\|\| Displays the 2D cells connected to 1D nodes via 2D HX and 2D SX 2d_bc objects including SX boundaries from 1D features. Additional information is supplied through the attributes.<br>		\| [[Check_Files_1d_to_2d_bc \| _1d_to_2d_check]]\|\| Displays the 2D cells connected to 1D nodes via 2D HX and 2D SX 2d_bc objects including SX boundaries from 1D features. Additional information is supplied through the attributes.<br>
	In the _1d_to_2d_check layer, all SX cells connected to the same 1D node are grouped together as one object, and the Lowest_ZC_2D value is the lowest 2D cell ZC value of all the cells connected to the 1D node. For the _1d_to_2d_check_R layer, it’s not possible to group the cells as one object, each cell is separate, when clicking on the SX cells, note that the value is still the lowest ZC of all 2D cells, not of the individual cell. For 2D HX links, the value is the ZC value of the individual cell.		In the _1d_to_2d_check layer, all SX cells connected to the same 1D node are grouped together as one object, and the Lowest_ZC_2D value is the lowest 2D cell ZC value of all the cells connected to the 1D node. For the _1d_to_2d_check_R layer, it’s not possible to group the cells as one object, each cell is separate, when clicking on the SX cells, note that the value is still the lowest ZC of all 2D cells, not of the individual cell. For 2D HX links, the value is the ZC value of the individual cell.
			\|-
			\| [[Check_Files_1d_to_2d_gw \| _1d_to_2d_gw_check]]\|\| Displays the 2D cells connected to 1D nodes via SX boundaries representing groundwater connections (as defined in the 2d_bc layer using the "GW" flag).
	\|}		\|}

Pavlina Monhartova: /* Tips for Visualising Check Files */

2024-12-31T02:58:26Z

Tips for Visualising Check Files

← Older revision		Revision as of 12:58, 31 December 2024
Line 21:		Line 21:
	Depending on the size of the model, the check files may contain a large amount of data, for example the _grd_check file may contain thousands or millions of cells. As a modeller you probably won't inspect each cell to ensure that the data is value, however you may want to view this for the entire model. Thematic mapping or styling the input layers can be used in your GIS software to do this.		Depending on the size of the model, the check files may contain a large amount of data, for example the _grd_check file may contain thousands or millions of cells. As a modeller you probably won't inspect each cell to ensure that the data is value, however you may want to view this for the entire model. Thematic mapping or styling the input layers can be used in your GIS software to do this.
	Some tips are given below for a range of GIS platforms, however, the functionality is likely to be available in almost all GIS platforms:<br>		Some tips are given below for a range of GIS platforms, however, the functionality is likely to be available in almost all GIS platforms:<br>
	* [[QGIS_Style_Check_Files \| QGIS style check files]]
	* [[MapInfo_Style_Check_Files \| MapInfo style check files]]		* [[MapInfo_Style_Check_Files \| MapInfo style check files]]

	* [[ArcMap_Style_Check_Files \| ArcMap style check files]]
	=Check File Types=		=Check File Types=
	The check files are separated into 2D and 1D check files. The output location for these is controlled by commands in the .tcf and .ecf as described above. Not all check file types will be output for all models, if a model has no 2D Z Shape (2d_zsh) format topography modifiers then the _zsh_zpt check file type will not be output by TUFLOW. A list of the check file types is provided below. For more information on each of these please click on the page link.<br>		The check files are separated into 2D and 1D check files. The output location for these is controlled by commands in the .tcf and .ecf as described above. Not all check file types will be output for all models, if a model has no 2D Z Shape (2d_zsh) format topography modifiers then the _zsh_zpt check file type will not be output by TUFLOW. A list of the check file types is provided below. For more information on each of these please click on the page link.<br>

ElizaCollison: /* 2D Check Files */

2024-11-27T11:52:12Z

2D Check Files

← Older revision		Revision as of 21:52, 27 November 2024
Line 45:		Line 45:
	The DEM_M and DEM_Z check grids are written if the model start up is forced to only process the .tgc file. To do this, don’t specify or comment out, the <font color="blue"><tt> BC Control File </tt></font> command.		The DEM_M and DEM_Z check grids are written if the model start up is forced to only process the .tgc file. To do this, don’t specify or comment out, the <font color="blue"><tt> BC Control File </tt></font> command.
	\|-		\|-
	\|[[Check_Files_2d_DEM_Zmin \| _DEM_Zmin]]\|\| A DEM based on the minimum SGS elevations. This file is only produced when running a model with SGS. The .tcf command <font color="blue"><tt>Grid Format </tt></font> can be used output this check file in ASCII (ASC) or binary (FLT) format rather than the default TIF format.		\|[[Check_Files_2d_DEM_Zmin \| _DEM_Zmin]]\|\| A DEM based on the minimum SGS elevations. This file is only produced when running a model with SGS. The .tcf command <font color="blue"><tt>Grid Format </tt></font> can be used output this check file in ASCII (ASC) or binary (FLT) format rather than the default GeoTIFF (TIF) format.
			\|-
			\|[[Check_Files_2d_DEM_Z_HR \| _DEM_Z_HR]]\|\| A DEM based on the SGS elevations. This file is only produced when running a model with SGS and high resolution outputs. The .tcf command <font color="blue"><tt>Grid Format </tt></font> can be used output this check file in ASCII (ASC) or binary (FLT) format rather than the default GeoTIFF (TIF) format.
	\|-		\|-
	! colspan="2" \| Vector Check Files		! colspan="2" \| Vector Check Files

Emilie Nielsen: /* 2D / 2D Check Files */

2024-08-25T23:24:28Z

2D / 2D Check Files

← Older revision		Revision as of 09:24, 26 August 2024
Line 167:		Line 167:
	!colspan="2" \| Vector Check Files		!colspan="2" \| Vector Check Files
	\|-		\|-
	\| [[Check_Files_2d_to_2d_bc \| _2d_to_2d_check]]\|\| Displays the 2D cells used to link two 2D domains together via a 2d_bc type “2D” boundary. ~~Similar to the [[Check_Files_1d_to_2d_bc\|_1d_to_2d_check]] layer, the cells connected to the same hidden 1D node are given the same colour when using the .mif/.mid format.~~ Use the <font color="blue"><tt>Reveal 1D Nodes</tt></font> <font color="red"><tt>==</tt></font> <tt>ON</tt> command in the .tcf to view the locations of the hidden 1D nodes.		\| [[Check_Files_2d_to_2d_bc \| _2d_to_2d_check]]\|\| Displays the 2D cells used to link two 2D domains together via a 2d_bc type “2D” boundary. Use the <font color="blue"><tt>Reveal 1D Nodes</tt></font> <font color="red"><tt>==</tt></font> <tt>ON</tt> command in the .tcf to view the locations of the hidden 1D nodes.
	\|}		\|}