TUFLOW Message 2934: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 15:11, 30 January 2026 view source Teegan.Burke (talk \| contribs) Bureaucrats, Administrators 436 edits No edit summary Tag: Visual edit ← Older edit		Latest revision as of 15:19, 30 January 2026 view source Teegan.Burke (talk \| contribs) Bureaucrats, Administrators 436 edits No edit summary Tag: Visual edit: Switched
(3 intermediate revisions by the same user not shown)
Line 11: * snap 2d_zsh elevation points to every 2d_zsh polygon vertex, or * use the "NO MERGE" option and supply elevations as needed. In TUFLOW Build 2025.2.0, updates were made to ~~process~~the aprocessing of merge ~~polygon~~polygons that ~~spreads~~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~~800px]]▼ \|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.