TUFLOW Message 2051: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
No edit summary |
Added suggestion for SX region needing to be in the same command as the CN line |
||
| Line 5: | Line 5: | ||
|message_desc=Connection object unused or not snapped to a 2D HX or 2D SX object. All connections (CN objects) must be snapped to a 1D/2D interface object. |
|message_desc=Connection object unused or not snapped to a 2D HX or 2D SX object. All connections (CN objects) must be snapped to a 1D/2D interface object. |
||
|suggestions=Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object. |
|suggestions=Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object. |
||
When the SX object is a region, the SX region layer and the CN line layer must be joined with a {{!}} in the same READ GIS BC command. For example: |
|||
Read GIS BC == 2d_bc_M03_culverts_R {{!}} 2d_bc_M03_culverts_L |
|||
Revision as of 16:46, 16 April 2025
TUFLOW Message
ERROR 2051 - Connection object unused or not snapped to a 2D HX or 2D SX object.
Alternate Message
WARNING 2051 - Connection object unused or not snapped to a 2D HX or 2D SX object.
Description
Connection object unused or not snapped to a 2D HX or 2D SX object. All connections (CN objects) must be snapped to a 1D/2D interface object.
Suggestions
Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object.
When the SX object is a region, the SX region layer and the CN line layer must be joined with a | in the same READ GIS BC command. For example:
Read GIS BC == 2d_bc_M03_culverts_R | 2d_bc_M03_culverts_L
| Up |
|---|
 2xxx Messages
|