TUFLOW Message 2028: Difference between revisions
No edit summary |
m CN object must be in the same READ GIS BC command as the SX object |
||
| Line 6: | Line 6: | ||
|suggestions=Check snapping and boundary configuration. 2D SX object should be snapped to 1D node or linked to a 1D node by CN line (connection object). |
|suggestions=Check snapping and boundary configuration. 2D SX object should be snapped to 1D node or linked to a 1D node by CN line (connection object). |
||
When |
When using a CN line object, the SX object and the CN line object must be in the same READ GIS BC command. |
||
SHP example: |
SHP example: |
||
Latest revision as of 20:06, 25 November 2025
TUFLOW Message
ERROR 2028 - Could not find a CN object or 1D node snapped to 2D SX object.
Alternate Message
NA
Message Type
ERROR
Description
Could not find a CN object or 1D node snapped to 2D SX object.
Suggestions
Check snapping and boundary configuration. 2D SX object should be snapped to 1D node or linked to a 1D node by CN line (connection object).
When using a CN line object, the SX object and the CN line object must be in the same READ GIS BC command.
SHP example:
Read GIS BC == 2d_bc_M03_culverts_R.shp | 2d_bc_M03_culverts_L.shp ! SX and CN object in the same command via |
GPKG example:
Read GIS BC == 2d_bc_M03_culverts_R | 2d_bc_M03_culverts_L ! SX and CN object in the same command via |
MIF example:
Read GIS BC == 2d_bc_M03_culverts_SX_CN.mif ! SX and CN object in the same file
| Up |
|---|
 2xxx Messages
|