TUFLOW Message 1005: Difference between revisions

From Tuflow
Jump to navigation Jump to search
Content deleted Content added
No edit summary
No edit summary
 
(One intermediate revision by one other user not shown)
Line 4: Line 4:
|type=[[ERROR]]
|type=[[ERROR]]
|message_desc=1D boundary condition (1d_bc) object is not snapped to a 1D node.
|message_desc=1D boundary condition (1d_bc) object is not snapped to a 1D node.
|suggestions=Check snapping and location of 1d_bc object to ensure it is at a valid 1D node (1d_nwk).
|suggestions=Check snapping and location of 1d_bc object to ensure it is at a valid 1D node (1d_nwk). Check the 1d_bc and 1n_nwk layers have the same projection.



|prelink=[[TUFLOW_Message_1004|Message 1004]]
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]]
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]]
|nextlink=[[TUFLOW_Message_1006|Message 1006]]
}}
}}

Latest revision as of 16:04, 18 June 2025

TUFLOW Message
ERROR 1005 - Failed to find a node snapped to boundary condition with name ",a,

Alternate Message
NA

Message Type
ERROR

Description
1D boundary condition (1d_bc) object is not snapped to a 1D node.

Suggestions
Check snapping and location of 1d_bc object to ensure it is at a valid 1D node (1d_nwk). Check the 1d_bc and 1n_nwk layers have the same projection.


Up
1xxx Messages