Difference between revisions of "TUFLOW Message 1102"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
"X" Type channels do not require an ID. | "X" Type channels do not require an ID. | ||
|suggestions=Give each 1d_nwk a valid and unique ID. | |suggestions=Give each 1d_nwk a valid and unique ID. | ||
| − | + | ||
| − | |||
| − | |||
|prelink=[[TUFLOW_Message_1101|Message 1101]] | |prelink=[[TUFLOW_Message_1101|Message 1101]] | ||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | |uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | ||
|nextlink=[[TUFLOW_Message_1103|Message 1103]] | |nextlink=[[TUFLOW_Message_1103|Message 1103]] | ||
}} | }} | ||
Revision as of 16:33, 1 July 2022
TUFLOW Message
ERROR 1102 - Channel at ",a,",",a," does not have an ID.
Alternate Message
NA
Message Type
ERROR
Description
1d channels (1d_nwk) should have a unique identifier up to 12 characters in length in the "ID" GIS attribute. This may contain any character except for quotes and commas, and cannot be blank. As a general rule, spaces and special characters (eg. “\”) should be avoided, although they are accepted. The same ID can be used for a channel and a node, but no two nodes and no two channels can have the same ID.
Since Build 2005-05-AN, digitised nodes can have their ID left blank and TUFLOW will assign an ID.
"X" Type channels do not require an ID.
Suggestions
Give each 1d_nwk a valid and unique ID.
| Up |
|---|
 1xxx Messages
|