TUFLOW Message 1462: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
Created page with "{{TUFLOW_Message |tuflow_message=ERROR 1462 - 1D node "<node_id>" is connected to both 2D SX and 2D HX boundaries. |alt_msg=NA<br> |type=ERROR |message_desc=A 1D node wit..." |
No edit summary |
||
| Line 1: | Line 1: | ||
{{TUFLOW_Message |
{{TUFLOW_Message |
||
|tuflow_message=ERROR 1462 - 1D node "<node_id>" is connected to both 2D SX and 2D HX boundaries. |
|tuflow_message=ERROR 1462 - 1D node "<node_id>" is connected to both 2D SX and 2D HX boundaries. |
||
|alt_msg=CHECK 1462 - 1D node "<node_id>" is connected to both 2D SX and 2D HX boundaries.<br> |
|||
|alt_msg=NA<br> |
|||
|type=[[ERROR]] |
|type=[[ERROR]]<br> |
||
[[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. |
||
|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. |
||
Revision as of 01:13, 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.
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
|