Difference between revisions of "TUFLOW Message 1164"
Jump to navigation
Jump to search
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. |
+ | |||
+ | 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: | ||
+ | <br> [[File:Error 1164.jpg|250px]] | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | |uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | ||
}} | }} |
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 |