TUFLOW Message 2934 - Revision history

Teegan.Burke at 05:19, 30 January 2026

2026-01-30T05:19:18Z

← Older revision		Revision as of 15:19, 30 January 2026
Line 14:		Line 14:
	In TUFLOW Build 2025.2.0, updates were made to the processing of merge polygons that spread across multiple Quadtree domains (e.g. nest levels). During Quadtree pre-processing, TUFLOW constructs a Quadtree mesh for each nest level, but only updates the ZC/ZU/ZV/ZH elevations in the final Quadtree mesh. For the “hidden” Quadtree mesh illustrated in the image below, the elevations were not being updated. A fix has been made to update both the “hidden” and “active” Quadtree meshes. After this change, a merge polygon that spreads across multiple Quadtree domains can use the elevations from the “hidden” ZC/ZU/ZV/ZH points for merging elevations. This reduces the risk of applying unexpected elevation at the tin vertices of a merge polygon. Reviewing the final elevations with the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files is still recommended, given users are unable to see the elevations used for merging within the hidden mesh areas.		In TUFLOW Build 2025.2.0, updates were made to the processing of merge polygons that spread across multiple Quadtree domains (e.g. nest levels). During Quadtree pre-processing, TUFLOW constructs a Quadtree mesh for each nest level, but only updates the ZC/ZU/ZV/ZH elevations in the final Quadtree mesh. For the “hidden” Quadtree mesh illustrated in the image below, the elevations were not being updated. A fix has been made to update both the “hidden” and “active” Quadtree meshes. After this change, a merge polygon that spreads across multiple Quadtree domains can use the elevations from the “hidden” ZC/ZU/ZV/ZH points for merging elevations. This reduces the risk of applying unexpected elevation at the tin vertices of a merge polygon. Reviewing the final elevations with the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files is still recommended, given users are unable to see the elevations used for merging within the hidden mesh areas.

	[[File:Hidden qpc mesh update.png\|~~Thumb~~]]		[[File:Hidden qpc mesh update.png\|800px]]

	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]

Teegan.Burke at 05:14, 30 January 2026

2026-01-30T05:14:45Z

← Older revision		Revision as of 15:14, 30 January 2026
Line 12:		Line 12:
	* use the "NO MERGE" option and supply elevations as needed.		* use the "NO MERGE" option and supply elevations as needed.

	In TUFLOW Build 2025.2.0, updates were made to ~~process~~ a merge ~~polygon~~ that ~~spreads~~ across multiple Quadtree domains (e.g. nest levels). During Quadtree pre-processing, TUFLOW constructs a Quadtree mesh for each nest level, but only updates the ZC/ZU/ZV/ZH elevations in the final Quadtree mesh. For the “hidden” Quadtree mesh illustrated in the image below, the elevations were not being updated. A fix has been made to update both the “hidden” and “active” Quadtree meshes. After this change, a merge polygon that spreads across multiple Quadtree domains can use the elevations from the “hidden” ZC/ZU/ZV/ZH points for merging elevations. This reduces the risk of applying unexpected elevation at the tin vertices of a merge polygon. Reviewing the final elevations with the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files is still recommended, given users are unable to see the elevations used for merging within the hidden mesh areas.		In TUFLOW Build 2025.2.0, updates were made to the processing of merge polygons that spread across multiple Quadtree domains (e.g. nest levels). During Quadtree pre-processing, TUFLOW constructs a Quadtree mesh for each nest level, but only updates the ZC/ZU/ZV/ZH elevations in the final Quadtree mesh. For the “hidden” Quadtree mesh illustrated in the image below, the elevations were not being updated. A fix has been made to update both the “hidden” and “active” Quadtree meshes. After this change, a merge polygon that spreads across multiple Quadtree domains can use the elevations from the “hidden” ZC/ZU/ZV/ZH points for merging elevations. This reduces the risk of applying unexpected elevation at the tin vertices of a merge polygon. Reviewing the final elevations with the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files is still recommended, given users are unable to see the elevations used for merging within the hidden mesh areas.

	[[File:Hidden qpc mesh update.png\|Thumb]]		[[File:Hidden qpc mesh update.png\|Thumb]]

	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]
	}}		}}

Teegan.Burke at 05:12, 30 January 2026

2026-01-30T05:12:28Z

← Older revision		Revision as of 15:12, 30 January 2026
Line 14:		Line 14:
	In TUFLOW Build 2025.2.0, updates were made to process a merge polygon that spreads across multiple Quadtree domains (e.g. nest levels). During Quadtree pre-processing, TUFLOW constructs a Quadtree mesh for each nest level, but only updates the ZC/ZU/ZV/ZH elevations in the final Quadtree mesh. For the “hidden” Quadtree mesh illustrated in the image below, the elevations were not being updated. A fix has been made to update both the “hidden” and “active” Quadtree meshes. After this change, a merge polygon that spreads across multiple Quadtree domains can use the elevations from the “hidden” ZC/ZU/ZV/ZH points for merging elevations. This reduces the risk of applying unexpected elevation at the tin vertices of a merge polygon. Reviewing the final elevations with the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files is still recommended, given users are unable to see the elevations used for merging within the hidden mesh areas.		In TUFLOW Build 2025.2.0, updates were made to process a merge polygon that spreads across multiple Quadtree domains (e.g. nest levels). During Quadtree pre-processing, TUFLOW constructs a Quadtree mesh for each nest level, but only updates the ZC/ZU/ZV/ZH elevations in the final Quadtree mesh. For the “hidden” Quadtree mesh illustrated in the image below, the elevations were not being updated. A fix has been made to update both the “hidden” and “active” Quadtree meshes. After this change, a merge polygon that spreads across multiple Quadtree domains can use the elevations from the “hidden” ZC/ZU/ZV/ZH points for merging elevations. This reduces the risk of applying unexpected elevation at the tin vertices of a merge polygon. Reviewing the final elevations with the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files is still recommended, given users are unable to see the elevations used for merging within the hidden mesh areas.

	[[File:Hidden qpc mesh update.png]]		[[File:Hidden qpc mesh update.png\|Thumb]]
	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]
	}}		}}

Teegan.Burke at 05:12, 30 January 2026

2026-01-30T05:12:04Z

← Older revision		Revision as of 15:12, 30 January 2026
Line 12:		Line 12:
	* use the "NO MERGE" option and supply elevations as needed.		* use the "NO MERGE" option and supply elevations as needed.

		⚫	In TUFLOW Build 2025.2.0, updates were made to process a merge polygon that spreads across multiple Quadtree domains (e.g. nest levels). During Quadtree pre-processing, TUFLOW constructs a Quadtree mesh for each nest level, but only updates the ZC/ZU/ZV/ZH elevations in the final Quadtree mesh. For the “hidden” Quadtree mesh illustrated in the image below, the elevations were not being updated. A fix has been made to update both the “hidden” and “active” Quadtree meshes. After this change, a merge polygon that spreads across multiple Quadtree domains can use the elevations from the “hidden” ZC/ZU/ZV/ZH points for merging elevations. This reduces the risk of applying unexpected elevation at the tin vertices of a merge polygon. Reviewing the final elevations with the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files is still recommended, given users are unable to see the elevations used for merging within the hidden mesh areas.

		⚫	[[File:Hidden qpc mesh update.png]]
	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]
	}}		}}
⚫	[[File:Hidden qpc mesh update.png~~\|thumb~~]]
⚫	In TUFLOW Build 2025.2.0, updates were made to process a merge polygon that spreads across multiple Quadtree domains (e.g. nest levels). During Quadtree pre-processing, TUFLOW constructs a Quadtree mesh for each nest level, but only updates the ZC/ZU/ZV/ZH elevations in the final Quadtree mesh. For the “hidden” Quadtree mesh illustrated in the image below, the elevations were not being updated. A fix has been made to update both the “hidden” and “active” Quadtree meshes. After this change, a merge polygon that spreads across multiple Quadtree domains can use the elevations from the “hidden” ZC/ZU/ZV/ZH points for merging elevations. This reduces the risk of applying unexpected elevation at the tin vertices of a merge polygon. Reviewing the final elevations with is still recommended, given users are unable to see the elevations used for merging within the hidden mesh areas.

Teegan.Burke at 05:11, 30 January 2026

2026-01-30T05:11:03Z

← Older revision		Revision as of 15:11, 30 January 2026
Line 14:		Line 14:
	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]
	}}		}}
			[[File:Hidden qpc mesh update.png\|thumb]]
			In TUFLOW Build 2025.2.0, updates were made to process a merge polygon that spreads across multiple Quadtree domains (e.g. nest levels). During Quadtree pre-processing, TUFLOW constructs a Quadtree mesh for each nest level, but only updates the ZC/ZU/ZV/ZH elevations in the final Quadtree mesh. For the “hidden” Quadtree mesh illustrated in the image below, the elevations were not being updated. A fix has been made to update both the “hidden” and “active” Quadtree meshes. After this change, a merge polygon that spreads across multiple Quadtree domains can use the elevations from the “hidden” ZC/ZU/ZV/ZH points for merging elevations. This reduces the risk of applying unexpected elevation at the tin vertices of a merge polygon. Reviewing the final elevations with is still recommended, given users are unable to see the elevations used for merging within the hidden mesh areas.

Pavlina Monhartova at 05:01, 18 July 2025

2025-07-18T05:01:50Z

← Older revision		Revision as of 15:01, 18 July 2025
Line 3:		Line 3:
	\|alt_msg=CHECK 2934 - At least one merge polygon vertex is located inside quadtree cell(s) from different nesting level. Processing nesting level = n <br>		\|alt_msg=CHECK 2934 - At least one merge polygon vertex is located inside quadtree cell(s) from different nesting level. Processing nesting level = n <br>

	\|type=[[WARNING]] ~~[[CHECK]]~~		\|type=[[WARNING]]<br>
			[[CHECK]]
	\|message_desc=Issues can occur in the TIN process when 2d_zsh polygons intersect with multiple quadtree levels.		\|message_desc=Issues can occur in the TIN process when 2d_zsh polygons intersect with multiple quadtree levels.
	\|suggestions= Check by reviewing the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files that the appropriate topography modifications have been applied. If they haven't, options include:		\|suggestions= Check by reviewing the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files that the appropriate topography modifications have been applied. If they haven't, options include:

Emilie Nielsen at 05:12, 21 January 2025

2025-01-21T05:12:09Z

← Older revision		Revision as of 15:12, 21 January 2025
Line 5:		Line 5:
	\|type=[[WARNING]] [[CHECK]]		\|type=[[WARNING]] [[CHECK]]
	\|message_desc=Issues can occur in the TIN process when 2d_zsh polygons intersect with multiple quadtree levels.		\|message_desc=Issues can occur in the TIN process when 2d_zsh polygons intersect with multiple quadtree levels.
	\|suggestions= Check by reviewing the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files that the appropriate topography modifications have been applied. If they haven't options include:		\|suggestions= Check by reviewing the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files that the appropriate topography modifications have been applied. If they haven't, options include:
	* extend the 2d_qnl to cover the entire 2d_zsh,		* extend the 2d_qnl to cover the entire 2d_zsh,
	* create a TIN using QGIS or SMS and read the TIN into TUFLOW directly (using the 'Read TIN Zpts ==' ~~command~~),		* create a TIN using QGIS or SMS and read the TIN into TUFLOW directly (using the TGC command '<tt><font color="blue">Read TIN Zpts </font><font color="red">==</font></tt>'),
	* snap 2d_zsh elevation points to every 2d_zsh polygon vertex, or		* snap 2d_zsh elevation points to every 2d_zsh polygon vertex, or
	* use the "NO MERGE" option and supply elevations as needed.		* use the "NO MERGE" option and supply elevations as needed.

ElizaCollison at 16:11, 13 January 2025

2025-01-13T16:11:40Z

← Older revision		Revision as of 02:11, 14 January 2025
Line 5:		Line 5:
	\|type=[[WARNING]] [[CHECK]]		\|type=[[WARNING]] [[CHECK]]
	\|message_desc=Issues can occur in the TIN process when 2d_zsh polygons intersect with multiple quadtree levels.		\|message_desc=Issues can occur in the TIN process when 2d_zsh polygons intersect with multiple quadtree levels.
	\|suggestions= Check by reviewing the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files that the appropriate topography modifications have been applied. If they haven't, ~~either extend the 2d_qnl to cover the entire 2d_zsh or create a TIN using QGIS or SMS and read the TIN into TUFLOW directly (using the 'Read TIN Zpts ==' command).~~		\|suggestions= Check by reviewing the <u>[[Check_Files_2d_zsh_zpt \| _zsh_zpt]]</u> and <u>[[Check_Files_2d_DEM_Z \| DEM_Z]]</u> check files that the appropriate topography modifications have been applied. If they haven't options include:
			* extend the 2d_qnl to cover the entire 2d_zsh,
			* create a TIN using QGIS or SMS and read the TIN into TUFLOW directly (using the 'Read TIN Zpts ==' command),
			* snap 2d_zsh elevation points to every 2d_zsh polygon vertex, or
			* use the "NO MERGE" option and supply elevations as needed.

	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]

ShuangGao: Created page with "{{TUFLOW_Message |tuflow_message=WARNING 2934 - At least one merge polygon vertex is outside quadtree sub-domain. Current nesting level = n |alt_msg=CHECK 2934 - At least on..."

2024-11-27T03:50:07Z

Created page with "{{TUFLOW_Message |tuflow_message=WARNING 2934 - At least one merge polygon vertex is outside quadtree sub-domain. Current nesting level = n |alt_msg=CHECK 2934 - At least on..."

New page

{{TUFLOW_Message
|tuflow_message=WARNING 2934 - At least one merge polygon vertex is outside quadtree sub-domain. Current nesting level = n
|alt_msg=CHECK 2934 - At least one merge polygon vertex is located inside quadtree cell(s) from different nesting level. Processing nesting level = n 

|type=[[WARNING]] [[CHECK]]
|message_desc=Issues can occur in the TIN process when 2d_zsh polygons intersect with multiple quadtree levels.
|suggestions= Check by reviewing the [[Check_Files_2d_zsh_zpt | _zsh_zpt]] and [[Check_Files_2d_DEM_Z | DEM_Z]] check files that the appropriate topography modifications have been applied. If they haven't, either extend the 2d_qnl to cover the entire 2d_zsh or create a TIN using QGIS or SMS and read the TIN into TUFLOW directly (using the 'Read TIN Zpts ==' command).

|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
}}