Difference between revisions of "TUFLOW Message 1353"
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
|suggestions=Set the 'UCS' attribute to 'T' in the 1D network layer or manually assign storage via a "NA" table. For missing CS data, ensure that a cross-section has been correctly specified.<br> | |suggestions=Set the 'UCS' attribute to 'T' in the 1D network layer or manually assign storage via a "NA" table. For missing CS data, ensure that a cross-section has been correctly specified.<br> | ||
If this error occurs at a node or pit location, ensure that this is correctly snapped to a channel. | If this error occurs at a node or pit location, ensure that this is correctly snapped to a channel. | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | |uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 10:37, 23 December 2022
TUFLOW Message
ERROR 1353 - No NA data for Node <Node ID>
Alternate Message
ERROR 1353 - No CS data for Chan <Chan ID>
Message Type
ERROR
Description
If the message is "No NA data for Node" TUFLOW has encountered a 1D Node with no storage allocation. This typically occurs if the 'UCS' (use channel storage) attribute in a 1D network layer is set to 'F' (false).
If the message is "No CS data for Chan" no cross-sectional information has been provided for channel.
This error can also occur if you have a pit or node object, which is not correctly snapped to a channel.
Suggestions
Set the 'UCS' attribute to 'T' in the 1D network layer or manually assign storage via a "NA" table. For missing CS data, ensure that a cross-section has been correctly specified.
If this error occurs at a node or pit location, ensure that this is correctly snapped to a channel.
| Up |
|---|
 1xxx Messages
|