Difference between revisions of "TUFLOW Message 2934"
Jump to navigation
Jump to search
| 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 ==' | + | * 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. | ||
Latest revision as of 15:12, 21 January 2025
TUFLOW Message
WARNING 2934 - At least one merge polygon vertex is outside quadtree sub-domain. Current nesting level = n
Alternate Message
CHECK 2934 - At least one merge polygon vertex is located inside quadtree cell(s) from different nesting level. Processing nesting level = n
Description
Issues can occur in the TIN process when 2d_zsh polygons intersect with multiple quadtree levels.
Suggestions
Check by reviewing the _zsh_zpt and DEM_Z 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 TGC command 'Read TIN Zpts =='),
- snap 2d_zsh elevation points to every 2d_zsh polygon vertex, or
- use the "NO MERGE" option and supply elevations as needed.
| Up |
|---|
 2xxx Messages
|