Difference between revisions of "TUFLOW Message 1462"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
|type=[[ERROR]]<br> | |type=[[ERROR]]<br> | ||
[[CHECK]] | [[CHECK]] | ||
| − | |message_desc=A 1D node within the model has been connected to both a 2D SX and a 2D HX boundary. A node should only be connected to one of the boundary types. | + | |message_desc=A 1D node within the model has been connected to both a 2D SX and a 2D HX boundary. A node should only be connected to one of the boundary types. This message is downgraded to a CHECK if tcf command "Defaults == Pre 2024" or ecf command "OVERLAPPING SX HX BOUNDARY == CHECK" is used. |
|suggestions=Reconfigure the model to ensure the 1D node is connected to either a SX boundary OR a HX boundary. The _messages GIS layer spatially displays which node is triggering this error. | |suggestions=Reconfigure the model to ensure the 1D node is connected to either a SX boundary OR a HX boundary. The _messages GIS layer spatially displays which node is triggering this error. | ||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | |uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | ||
}} | }} | ||
Revision as of 01:16, 29 November 2024
TUFLOW Message
ERROR 1462 - 1D node "<node_id>" is connected to both 2D SX and 2D HX boundaries.
Alternate Message
CHECK 1462 - 1D node "<node_id>" is connected to both 2D SX and 2D HX boundaries.
Description
A 1D node within the model has been connected to both a 2D SX and a 2D HX boundary. A node should only be connected to one of the boundary types. This message is downgraded to a CHECK if tcf command "Defaults == Pre 2024" or ecf command "OVERLAPPING SX HX BOUNDARY == CHECK" is used.
Suggestions
Reconfigure the model to ensure the 1D node is connected to either a SX boundary OR a HX boundary. The _messages GIS layer spatially displays which node is triggering this error.
| Up |
|---|
 1xxx Messages
|