TUFLOW Message 2051: Difference between revisions

From Tuflow
Jump to navigation Jump to search
Content deleted Content added
Style and extra description for mif added
mNo edit summary
 
Line 8: Line 8:
When the SX object is a region, the SX region object and the CN line object must be in the same READ GIS BC command.
When the SX object is a region, the SX region object and the CN line object must be in the same READ GIS BC command.


SHP and GPKG example:
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>
<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>

Latest revision as of 17:27, 16 April 2025

TUFLOW Message
ERROR 2051 - Connection object unused or not snapped to a 2D HX or 2D SX object.

Alternate Message
WARNING 2051 - Connection object unused or not snapped to a 2D HX or 2D SX object.

Message Type
ERROR
WARNING

Description
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.

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 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