TUFLOW Message 2028: Difference between revisions

Content deleted Content added
No edit summary
m CN object must be in the same READ GIS BC command as the SX object
 
(3 intermediate revisions by 3 users not shown)
Line 4:
|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 linkedsnapped to 1D node foror linked to a 1D node by CN line (connection object) or snapped to 1D node.
 
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>
 
|prelink=[[TUFLOW_Message_2027|Message 2027]]
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
|nextlink=[[TUFLOW_Message_2029|Message 2029]]
}}