TUFLOW Message 1111 - Revision history

Melissa.Moghanloo at 05:15, 22 December 2022

2022-12-22T05:15:09Z

← Older revision		Revision as of 15:15, 22 December 2022
Line 13:		Line 13:
	\|suggestions=Check the channel being overwritten is intentional.		\|suggestions=Check the channel being overwritten is intentional.

	\|prelink=[[TUFLOW_Message_1110\|Message 1110]]
	\|uplink=[[1xxx_TUFLOW_Messages\|1xxx Messages]]		\|uplink=[[1xxx_TUFLOW_Messages\|1xxx Messages]]
	\|nextlink=[[TUFLOW_Message_1112\|Message 1112]]
	}}		}}

Melissa.Moghanloo at 06:35, 1 July 2022

2022-07-01T06:35:57Z

← Older revision		Revision as of 16:35, 1 July 2022
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.

	\|discussion_page=* [[Talk:TUFLOW Message 1111\|Discuss Message 1111]]
	\|link3=''
	\|link4=''
	\|prelink=[[TUFLOW_Message_1110\|Message 1110]]		\|prelink=[[TUFLOW_Message_1110\|Message 1110]]
	\|uplink=[[1xxx_TUFLOW_Messages\|1xxx Messages]]		\|uplink=[[1xxx_TUFLOW_Messages\|1xxx Messages]]

Melissa.Moghanloo at 04:06, 23 June 2022

2022-06-23T04:06:19Z

← Older revision		Revision as of 14:06, 23 June 2022
Line 5:		Line 5:
	\|message_desc=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.<br>		\|message_desc=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.<br>
	For example the relevant commands in your 1d control file (.ecf) might look like:<br>		For example the relevant commands in your 1d control file (.ecf) might look like:<br>
	<tt>Read GIS Network == model\mi\1d_nwk_culverts_001.mif<br>		<tt><font color="blue">Read GIS Network </font><font color="red">== </font>model\mi\1d_nwk_culverts_001.mif<br>
	<font color="grey">! Blocked scenario only<br></font>		<font color="grey">! Blocked scenario only<br></font>
	Read GIS Network == model\mi\1d_nwk_blocked_culverts_001.mif</tt><br>		<font color="blue">Read GIS Network </font><font color="red">== </font>model\mi\1d_nwk_blocked_culverts_001.mif</tt><br>
	<br>		<br>
	This could also occur unintentionally if a parallel channel is snapped to the same node and has the same ID.<br>		This could also occur unintentionally if a parallel channel is snapped to the same node and has the same ID.<br>

tuflow>Par at 22:13, 31 January 2011

2011-01-31T22:13:38Z

← Older revision		Revision as of 08:13, 1 February 2011
Line 4:		Line 4:
	\|type=[[CHECK]]		\|type=[[CHECK]]
	\|message_desc=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.<br>		\|message_desc=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.<br>
	For example your .ecf might look like :<br>		For example the relevant commands in your 1d control file (.ecf) might look like:<br>
	Read GIS Network == model\mi\1d_nwk_culverts_001.mif<br>		<tt>Read GIS Network == model\mi\1d_nwk_culverts_001.mif<br>
	~~###~~ Blocked scenario only<br>		<font color="grey">! Blocked scenario only<br></font>
	Read GIS Network == model\mi\1d_nwk_blocked_culverts_001.mif<br>		Read GIS Network == model\mi\1d_nwk_blocked_culverts_001.mif</tt><br>
	<br>		<br>
	This could also occur unintentionally if a parallel channel is snapped to the same node and has the same ID.<br>		This could also occur unintentionally if a parallel channel is snapped to the same node and has the same ID.<br>

tuflow>Par at 22:06, 31 January 2011

2011-01-31T22:06:26Z

@@ Line 3: / Line 3: @@
 |alt_msg=NA
 |type=[[CHECK]]
 |discussion_page=* [[Talk:TUFLOW Message 1111|Discuss Message 1111]]
 |link3=''

tuflow>Par: Created page with '{{TUFLOW_Message |tuflow_message=CHECK 1111 - Overwriting channel ",a," with same ID channel from |alt_msg=NA |type=CHECK |message_desc=???? |suggestions=???? |discussion_pa...'

2010-09-30T23:13:53Z

Created page with '{{TUFLOW_Message |tuflow_message=CHECK 1111 - Overwriting channel ",a," with same ID channel from |alt_msg=NA |type=CHECK |message_desc=???? |suggestions=???? |discussion_pa...'

New page

{{TUFLOW_Message
|tuflow_message=CHECK 1111 - Overwriting channel ",a," with same ID channel from
|alt_msg=NA
|type=[[CHECK]]
|message_desc=????
|suggestions=????
|discussion_page=* [[Talk:TUFLOW Message 1111|Discuss Message 1111]]
|link3=''
|link4=''
|prelink=[[TUFLOW_Message_1110|Message 1110]]
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]]
|nextlink=[[TUFLOW_Message_1112|Message 1112]]
}}