TUFLOW Message 2028: Difference between revisions
Content deleted Content added
Created page with '{{TUFLOW_Message |tuflow_message=???? |message_desc=Could not find a CN object or 1D node snapped to 2D SX object. |suggestions=???? |discussion_page=* [[Talk:TUFLOW Message 2028...' |
m CN object must be in the same READ GIS BC command as the SX object |
||
| (6 intermediate revisions by 4 users not shown) | |||
Line 1:
{{TUFLOW_Message
|tuflow_message=ERROR 2028 - Could not find a CN object or 1D node snapped to 2D SX object.
|alt_msg=NA
|type=[[ERROR]]
|message_desc=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:
<font color="blue"><tt>Read GIS BC </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>2d_bc_M03_culverts_R.shp {{!}} 2d_bc_M03_culverts_L.shp</tt></font> <font color="green"><tt> ! SX and CN object in the same command via {{!}}</tt></font> <br>
GPKG example:
<font color="blue"><tt>Read GIS BC </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>2d_bc_M03_culverts_R {{!}} 2d_bc_M03_culverts_L</tt></font> <font color="green"><tt> ! SX and CN object in the same command via {{!}}</tt></font> <br>
MIF example:
<font color="blue"><tt>Read GIS BC </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>2d_bc_M03_culverts_SX_CN.mif </tt></font> <font color="green"><tt> ! SX and CN object in the same file</tt></font> <br>
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
}}
| |||