Difference between revisions of "TUFLOW Message 2051"
m |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| 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 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]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
| − | |||
}} | }} | ||
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.
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
|