TUFLOW Message 2934: Difference between revisions
Content deleted Content added
Teegan.Burke (talk | contribs) No edit summary |
Teegan.Burke (talk | contribs) No edit summary |
||
Line 12:
* 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.▼
|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.
| |||