Difference between revisions of "TUFLOW Message 1111"
| Line 12: | Line 12: | ||
This check message is generated whenever channel data is overwritten. | This check message is generated whenever channel data is overwritten. | ||
|suggestions=Check the channel being overwritten is intentional. | |suggestions=Check the channel being overwritten is intentional. | ||
| − | + | ||
| − | |||
| − | |||
|prelink=[[TUFLOW_Message_1110|Message 1110]] | |prelink=[[TUFLOW_Message_1110|Message 1110]] | ||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | |uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | ||
|nextlink=[[TUFLOW_Message_1112|Message 1112]] | |nextlink=[[TUFLOW_Message_1112|Message 1112]] | ||
}} | }} | ||
Revision as of 16:35, 1 July 2022
TUFLOW Message
CHECK 1111 - Overwriting channel ",a," with same ID channel from
Alternate Message
NA
Message Type
CHECK
Description
If a channel is snapped to the same nodes and has the same ID, the channel will be overwritten in TUFLOW. This can be useful for setting up blocked case scenarios: a second "blocked" network can be read in after the original data preventing the need to change the original 1d network layers.
For example the relevant commands in your 1d control file (.ecf) might look like:
Read GIS Network == model\mi\1d_nwk_culverts_001.mif
! Blocked scenario only
Read GIS Network == model\mi\1d_nwk_blocked_culverts_001.mif
This could also occur unintentionally if a parallel channel is snapped to the same node and has the same ID.
This check message is generated whenever channel data is overwritten.
Suggestions
Check the channel being overwritten is intentional.
| Up |
|---|
 1xxx Messages
|