TUFLOW Message 1164: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
Created page with "{{TUFLOW_Message |tuflow_message=ERROR 1164 - Bridge LC table elevations not in ascending order for bridge channel <channel ID><br> Levels = <value 1, value 2> |alt_msg=NA |ty..." |
No edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 5: | Line 5: | ||
|type=[[ERROR]] |
|type=[[ERROR]] |
||
|message_desc=For the bridge LC or loss coefficient table heights are not in ascending order. |
|message_desc=For the bridge LC or loss coefficient table heights are not in ascending order. |
||
|suggestions=Data in first (elevation) column, should be unique and in ascending order. |
|suggestions=Data in first (elevation) column, should be unique and in ascending order. |
||
|discussion_page=* [[Talk:TUFLOW Message 1164|Discuss Message 1164]] |
|||
Particularly, it would be suggested to check the first column of the bridge height (H) in the file containing the tabular data file which is selected as source for the 1d_bg layer and make sure that the (H) data are in an ascending order and unique, as per the example below: |
|||
|link3='' |
|||
<br> [[File:Error 1164.jpg|250px]] |
|||
|link4='' |
|||
|prelink=[[TUFLOW_Message_1163|Message 1163]] |
|||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] |
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] |
||
|nextlink=[[TUFLOW_Message_1171|Message 1171]] |
|||
}} |
}} |
||
Latest revision as of 23:17, 11 December 2023
TUFLOW Message
ERROR 1164 - Bridge LC table elevations not in ascending order for bridge channel <channel ID>
Levels = <value 1, value 2>
Alternate Message
NA
Message Type
ERROR
Description
For the bridge LC or loss coefficient table heights are not in ascending order.
Suggestions
Data in first (elevation) column, should be unique and in ascending order.
Particularly, it would be suggested to check the first column of the bridge height (H) in the file containing the tabular data file which is selected as source for the 1d_bg layer and make sure that the (H) data are in an ascending order and unique, as per the example below:
| Up |
|---|
 1xxx Messages
|