TUFLOW Message 2340: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
|message_desc=The file being read into the 2D model (.tbc file) using the <tt><font color="blue">Read GIS BC </font><font color="red">== </font></tt> does not appear to be a 2d_bc format file. This has less than the required 8 attributes for this layer.<br> |
|message_desc=The file being read into the 2D model (.tbc file) using the <tt><font color="blue">Read GIS BC </font><font color="red">== </font></tt> does not appear to be a 2d_bc format file. This has less than the required 8 attributes for this layer.<br> |
||
The primary reason for this to occur is that a 1d boundary layer (1d_bc) file is being read into the .tbc file and not into the 1d domain (.ecf file). If the filename contains the text '''1d_bc''' the additional output <tt>File appears to be a 1d_bc file and not a 2d_bc </tt> is also included in the output message.<br> |
The primary reason for this to occur is that a 1d boundary layer (1d_bc) file is being read into the .tbc file and not into the 1d domain (.ecf file). If the filename contains the text '''1d_bc''' the additional output <tt>File appears to be a 1d_bc file and not a 2d_bc </tt> is also included in the output message.<br> |
||
Prior to the 2016 version of TUFLOW the accidental reading of a 1d_bc layer into the 2D boundary control file .tbc could cause an [[TUFLOW_Message_2056 | ERROR 2056]] to occur. |
Prior to the 2016 version of TUFLOW the accidental reading of a 1d_bc layer into the 2D boundary control file .tbc could cause an <u>[[TUFLOW_Message_2056 | ERROR 2056]]</u> to occur. |
||
|suggestions=Check that the 2d_bc file has the correct attributes and if a 1D boundary is being specified, please read this into the 1D control file (.ecf) or within a Start 1D Domain --> End 1D Domain block of commands in the .tcf.<br> |
|suggestions=Check that the 2d_bc file has the correct attributes and if a 1D boundary is being specified, please read this into the 1D control file (.ecf) or within a Start 1D Domain --> End 1D Domain block of commands in the .tcf.<br> |
||
Check that other type of layer, such as 2d_sa isn't read with the <tt><font color="blue">Read GIS BC </font><font color="red">== </font></tt> command. |
Check that other type of layer, such as 2d_sa isn't read with the <tt><font color="blue">Read GIS BC </font><font color="red">== </font></tt> command. |
||
|discussion_page=* [[Talk:TUFLOW Message 2340|Discuss Message 2340]] |
|||
|link3='' |
|||
|link4='' |
|||
|prelink=[[TUFLOW_Message_2336|Message 2336]] |
|||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] |
||
|nextlink=[[TUFLOW_Message_2343|Message 2343]] |
|||
}} |
}} |
||
Latest revision as of 15:09, 7 February 2023
TUFLOW Message
ERROR 2340 - Less than 8 attributes for 2d_bc file: <filename>
Alternate Message
NA
Message Type
ERROR
Description
The file being read into the 2D model (.tbc file) using the Read GIS BC == does not appear to be a 2d_bc format file. This has less than the required 8 attributes for this layer.
The primary reason for this to occur is that a 1d boundary layer (1d_bc) file is being read into the .tbc file and not into the 1d domain (.ecf file). If the filename contains the text 1d_bc the additional output File appears to be a 1d_bc file and not a 2d_bc is also included in the output message.
Prior to the 2016 version of TUFLOW the accidental reading of a 1d_bc layer into the 2D boundary control file .tbc could cause an ERROR 2056 to occur.
Suggestions
Check that the 2d_bc file has the correct attributes and if a 1D boundary is being specified, please read this into the 1D control file (.ecf) or within a Start 1D Domain --> End 1D Domain block of commands in the .tcf.
Check that other type of layer, such as 2d_sa isn't read with the Read GIS BC == command.
| Up |
|---|
 2xxx Messages
|