TUFLOW Message 2051: Difference between revisions
Content deleted Content added
Added suggestion for SX region needing to be in the same command as the CN line |
m CN and SX objects must be in the same Read GIS BC command |
||
| (2 intermediate revisions by the same user not shown) | |||
Line 3:
|alt_msg=WARNING 2051 - Connection object unused or not snapped to a 2D HX or 2D SX object.
|type=[[ERROR]] <br> [[WARNING]]
|message_desc=Connection object unused or not snapped to a 2D HX or 2D SX object. All connections (CN objects) must be snapped to a 1D/2D interface object found in the same Read GIS BC command.
|suggestions=Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object.
When the SX object is a region, the SX region
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]]
| |||