Difference between revisions of "TUFLOW Message 2027"
Jump to navigation
Jump to search
Melissa1987 (talk | contribs) |
|||
| 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. | ||
| − | + | ||
| − | |||
| − | |||
|prelink=[[TUFLOW_Message_2026|Message 2026]] | |prelink=[[TUFLOW_Message_2026|Message 2026]] | ||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
|nextlink=[[TUFLOW_Message_2028|Message 2028]] | |nextlink=[[TUFLOW_Message_2028|Message 2028]] | ||
}} | }} | ||
Revision as of 16:04, 5 July 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 |
|---|
 2xxx Messages
|