TUFLOW Message 2051: Difference between revisions

From Tuflow
Jump to navigation Jump to search
Content deleted Content added
Added suggestion for SX region needing to be in the same command as the CN line
Style and extra description for mif added
Line 6: Line 6:
|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.
|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 layer and the CN line layer must be joined with a {{!}} in the same READ GIS BC command. For example:
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:
Read GIS BC == 2d_bc_M03_culverts_R {{!}} 2d_bc_M03_culverts_L


<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]]
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]

Revision as of 17:14, 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 and 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