TUFLOW Message 2024: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
|message_desc=Could not find a 1D node snapped to 2d_bc connection (CN) line. |
|message_desc=Could not find a 1D node snapped to 2d_bc connection (CN) line. |
||
|suggestions=Check snapping and location of 2d_bc "CN" type object. This should connect a 1D node to a 2D boundary condition, e.g. "HX" or "SX" type connection. The messages.mif or messages_P.shp file will contain the location of the error.<br> |
|suggestions=Check snapping and location of 2d_bc "CN" type object. This should connect a 1D node to a 2D boundary condition, e.g. "HX" or "SX" type connection. The messages.mif or messages_P.shp file will contain the location of the error.<br> |
||
Check that the "CN" line finishes at a 1D node. In the example below, a single line has been digitised from the HX line to the HX line. Whilst it is snapped to the 1D node, it does not terminate there.<br> |
Check that the "CN" line finishes at a 1D node. In the example below, a single line has been digitised from the HX line to the HX line. Whilst it is snapped to the 1D node, it does not terminate there and therefore will cause Error 2024 to be generated.<br> |
||
[[File:Error 2024.PNG|500px]] |
[[File:Error 2024.PNG|500px]] |
||
<br><br> |
<br><br> |
||
Revision as of 15:40, 22 March 2013
TUFLOW Message
ERROR 2024 - Could not find a 1D node snapped to CN line.
Alternate Message
NA
Message Type
ERROR
Description
Could not find a 1D node snapped to 2d_bc connection (CN) line.
Suggestions
Check snapping and location of 2d_bc "CN" type object. This should connect a 1D node to a 2D boundary condition, e.g. "HX" or "SX" type connection. The messages.mif or messages_P.shp file will contain the location of the error.
Check that the "CN" line finishes at a 1D node. In the example below, a single line has been digitised from the HX line to the HX line. Whilst it is snapped to the 1D node, it does not terminate there and therefore will cause Error 2024 to be generated.
In the next image, this line has been split at the 1D node and the issue is resolved.
| Up |
|---|
 2xxx Messages
|