Difference between revisions of "TUFLOW Message 2027"

From Tuflow
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:
 
|message_desc=Found more than one 1D node snapped to 2D SX boundary.
 
|message_desc=Found more than one 1D node snapped to 2D SX boundary.
 
|suggestions=Review boundary configuration. Seperate 2D SX objects should be used for seperate nodes, or link nodes using a "X" type 1D network channel and have only one SX object.  
 
|suggestions=Review boundary configuration. Seperate 2D SX objects should be used for seperate nodes, or link nodes using a "X" type 1D network channel and have only one SX object.  
|discussion_page=* [[Talk:TUFLOW Message 2027|Discuss Message 2027]]
+
 
|link3=''
+
 
|link4=''
 
|prelink=[[TUFLOW_Message_2026|Message 2026]]
 
 
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
 
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
|nextlink=[[TUFLOW_Message_2028|Message 2028]]
 
 
}}
 
}}

Latest revision as of 10:59, 23 December 2022

TUFLOW Message
ERROR 2027 - Found more than one 1D node snapped to 2D SX object.

Alternate Message
NA

Message Type
ERROR

Description
Found more than one 1D node snapped to 2D SX boundary.

Suggestions
Review boundary configuration. Seperate 2D SX objects should be used for seperate nodes, or link nodes using a "X" type 1D network channel and have only one SX object.


Up
Go-up.png 2xxx Messages