TUFLOW Message 2001 - Revision history

Melissa.Moghanloo at 00:51, 23 December 2022

2022-12-23T00:51:53Z

← Older revision		Revision as of 10:51, 23 December 2022
Line 10:		Line 10:
	<br>		<br>


	\|prelink=[[TUFLOW_Message_1991\|Message 1991]]
	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]
	\|nextlink=[[TUFLOW_Message_2002\|Message 2002]]
	}}		}}

Melissa.Moghanloo at 05:52, 5 July 2022

2022-07-05T05:52:30Z

← Older revision		Revision as of 15:52, 5 July 2022
Line 10:		Line 10:
	<br>		<br>

	\|discussion_page=* [[Talk:TUFLOW Message 2001\|Discuss Message 2001]]
	\|link3=''
	\|link4=''
	\|prelink=[[TUFLOW_Message_1991\|Message 1991]]		\|prelink=[[TUFLOW_Message_1991\|Message 1991]]
	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]

Melissa.Moghanloo at 22:53, 23 June 2022

2022-06-23T22:53:09Z

← Older revision		Revision as of 08:53, 24 June 2022
Line 4:		Line 4:
	WARNING 2001 - ",a," "object" at ",a,",",a," is outside 2D model domain		WARNING 2001 - ",a," "object" at ",a,",",a," is outside 2D model domain
	\|type=[[ERROR]] <br> [[WARNING]]		\|type=[[ERROR]] <br> [[WARNING]]
	\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.		\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt><font color="blue">Check Inside Grid </font><font color="red">== </font></tt> command controls whether this message is an ERROR, WARNING or not given.

	\|suggestions=The _messages_P.shp or _messages.mif layer in the log folder contains the locations of the offending boundary objects. Review the <u>[[Check_Files_2d_dom \| _dom_check]]</u> file and the messages layer to ensure that all 2d_bc objects are within the model domain.<br>		\|suggestions=The _messages_P.shp or _messages.mif layer in the log folder contains the locations of the offending boundary objects. Review the <u>[[Check_Files_2d_dom \| _dom_check]]</u> file and the messages layer to ensure that all 2d_bc objects are within the model domain.<br>

Pavlina Monhartova at 01:32, 6 April 2022

2022-04-06T01:32:37Z

← Older revision		Revision as of 11:32, 6 April 2022
Line 6:		Line 6:
	\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.		\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.

	\|suggestions=The _messages_P.shp or _messages.mif layer in the log folder contains the locations of the offending boundary objects. Review the <u>[[Check_Files_2d_dom \| _dom_check]]</u> file and the messages layer to ensure that all 2d_bc objects are within the model domain. ~~Check also that the projection of the boundary layer is the same as the TUFLOW model projection.~~		\|suggestions=The _messages_P.shp or _messages.mif layer in the log folder contains the locations of the offending boundary objects. Review the <u>[[Check_Files_2d_dom \| _dom_check]]</u> file and the messages layer to ensure that all 2d_bc objects are within the model domain.<br>
			Check that the projection of the boundary layer is the same as the TUFLOW model projection.
	<br>		<br>

Pavlina Monhartova at 01:32, 6 April 2022

2022-04-06T01:32:03Z

← Older revision		Revision as of 11:32, 6 April 2022
Line 1:		Line 1:
	{{TUFLOW_Message		{{TUFLOW_Message
	\|tuflow_message=ERROR 2001 - ~~GIS~~ ~~Object~~ is outside 2D model domain		\|tuflow_message=ERROR 2001 - 2d_bc object is outside 2D model domain
	\|alt_msg=~~WARNING~~ 2001 - ~~",a,"~~ ~~"object" at ",a,",",a,"~~ is outside 2D model domain		\|alt_msg=ERROR 2001 - GIS Object is outside 2D model domain<br>
			WARNING 2001 - ",a," "object" at ",a,",",a," is outside 2D model domain
	\|type=[[ERROR]] <br> [[WARNING]]		\|type=[[ERROR]] <br> [[WARNING]]
	\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.		\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.

	\|suggestions=Ensure the 2D model domain (dom_check) has sufficient extent to cover the GIS object. The messages layer located in runs\log folder contains the location of the object outside the model domain in GIS format (.mif or .shp). If the object is not needed for the model, it can be removed from input files. <br>
		⚫	\|suggestions=The _messages_P.shp or _messages.mif layer in the log folder contains the locations of the offending boundary objects. Review the <u>[[Check_Files_2d_dom \| _dom_check]]</u> file and the messages layer to ensure that all 2d_bc objects are within the model domain. Check also that the projection of the boundary layer is the same as the TUFLOW model projection.
	<br>		<br>

	The TUFLOW domain is written in the check files ([[Check_Files_2d_dom \| _dom_check.mif or _dom_check_R.shp]]). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>
	<tt>
	Read GIS Location == gis\2d_loc_L.shp<br>
	Grid Size (X,Y) == 1000,1000<br>
	Write GIS Domain == ..\check\2d_dom_check.shp<br>
	STOP
	</tt>
	<br>
⚫	The ~~'''_messages~~.~~mif'''~~ or ~~'''_messages_P~~.~~shp'''~~ layer in the log folder contains the locations of the offending boundary objects. Review the ~~'''~~_dom_check~~'''~~ file and the messages layer to ensure that all 2d_bc objects are within the model domain. Check also that the projection of the boundary layer is the same as the TUFLOW model projection.
	\|discussion_page=* [[Talk:TUFLOW Message 2001\|Discuss Message 2001]]		\|discussion_page=* [[Talk:TUFLOW Message 2001\|Discuss Message 2001]]
	\|link3=''		\|link3=''

Pavlina Monhartova at 01:23, 6 April 2022

2022-04-06T01:23:25Z

← Older revision		Revision as of 11:23, 6 April 2022
Line 4:		Line 4:
	\|type=[[ERROR]] <br> [[WARNING]]		\|type=[[ERROR]] <br> [[WARNING]]
	\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.		\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.
	\|suggestions=Ensure the 2D model domain (dom_check) has sufficient extent or ~~remove~~ ~~object~~ ~~from input~~ ~~files~~. The messages layer located in runs\log folder contains the location of the object outside the model domain in GIS format (.mif or .shp). <br>		\|suggestions=Ensure the 2D model domain (dom_check) has sufficient extent to cover the GIS object. The messages layer located in runs\log folder contains the location of the object outside the model domain in GIS format (.mif or .shp). If the object is not needed for the model, it can be removed from input files. <br>
	<br>		<br>
	The TUFLOW domain is written in the check files ([[Check_Files_2d_dom \| _dom_check.mif or _dom_check_R.shp]]). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>		The TUFLOW domain is written in the check files ([[Check_Files_2d_dom \| _dom_check.mif or _dom_check_R.shp]]). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>

Pavlina Monhartova at 01:17, 6 April 2022

2022-04-06T01:17:46Z

← Older revision		Revision as of 11:17, 6 April 2022
Line 4:		Line 4:
	\|type=[[ERROR]] <br> [[WARNING]]		\|type=[[ERROR]] <br> [[WARNING]]
	\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.		\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.
	\|suggestions=Ensure the 2D model domain (dom_check) has sufficient extent or remove object from input files. The messages layer contains the location of the object outside the model domain in GIS format (.mif or .shp). <br>		\|suggestions=Ensure the 2D model domain (dom_check) has sufficient extent or remove object from input files. The messages layer located in runs\log folder contains the location of the object outside the model domain in GIS format (.mif or .shp). <br>
	<br>		<br>
	The TUFLOW domain is written in the check files ([[Check_Files_2d_dom \| _dom_check.mif or _dom_check_R.shp]]). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>		The TUFLOW domain is written in the check files ([[Check_Files_2d_dom \| _dom_check.mif or _dom_check_R.shp]]). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>

Pavlina Monhartova at 01:16, 6 April 2022

2022-04-06T01:16:05Z

← Older revision		Revision as of 11:16, 6 April 2022
Line 4:		Line 4:
	\|type=[[ERROR]] <br> [[WARNING]]		\|type=[[ERROR]] <br> [[WARNING]]
	\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.		\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.
	\|suggestions=Ensure the 2D model domain has sufficient extent or remove object from input files. The messages layer contains the location of the object outside the model domain in GIS format (.mif or .shp). <br>		\|suggestions=Ensure the 2D model domain (dom_check) has sufficient extent or remove object from input files. The messages layer contains the location of the object outside the model domain in GIS format (.mif or .shp). <br>
	<br>		<br>
	The TUFLOW domain is written in the check files ([[Check_Files_2d_dom \| _dom_check.mif or _dom_check_R.shp]]). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>		The TUFLOW domain is written in the check files ([[Check_Files_2d_dom \| _dom_check.mif or _dom_check_R.shp]]). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>

Par at 00:21, 10 September 2015

2015-09-10T00:21:46Z

← Older revision		Revision as of 10:21, 10 September 2015
Line 6:		Line 6:
	\|suggestions=Ensure the 2D model domain has sufficient extent or remove object from input files. The messages layer contains the location of the object outside the model domain in GIS format (.mif or .shp). <br>		\|suggestions=Ensure the 2D model domain has sufficient extent or remove object from input files. The messages layer contains the location of the object outside the model domain in GIS format (.mif or .shp). <br>
	<br>		<br>
	The TUFLOW domain is written in the check files (_dom_check.mif or _dom_check_R.shp). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>		The TUFLOW domain is written in the check files ([[Check_Files_2d_dom \| _dom_check.mif or _dom_check_R.shp]]). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>
	<tt>		<tt>
	Read GIS Location == gis\2d_loc_L.shp<br>		Read GIS Location == gis\2d_loc_L.shp<br>
Line 13:		Line 13:
	STOP		STOP
	</tt>		</tt>
			<br>
			The '''_messages.mif''' or '''_messages_P.shp''' layer in the log folder contains the locations of the offending boundary objects. Review the '''_dom_check''' file and the messages layer to ensure that all 2d_bc objects are within the model domain. Check also that the projection of the boundary layer is the same as the TUFLOW model projection.
	\|discussion_page=* [[Talk:TUFLOW Message 2001\|Discuss Message 2001]]		\|discussion_page=* [[Talk:TUFLOW Message 2001\|Discuss Message 2001]]
	\|link3=''		\|link3=''

tuflow>Par at 02:43, 31 August 2012

2012-08-31T02:43:37Z

← Older revision		Revision as of 12:43, 31 August 2012
Line 4:		Line 4:
	\|type=[[ERROR]] <br> [[WARNING]]		\|type=[[ERROR]] <br> [[WARNING]]
	\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.		\|message_desc=An object is located outside the 2D domain that it is assigned to. The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.
	\|suggestions=Ensure the 2D model domain has sufficient extent or remove object from input files.		\|suggestions=Ensure the 2D model domain has sufficient extent or remove object from input files. The messages layer contains the location of the object outside the model domain in GIS format (.mif or .shp). <br>
			<br>
			The TUFLOW domain is written in the check files (_dom_check.mif or _dom_check_R.shp). The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>
			<tt>
			Read GIS Location == gis\2d_loc_L.shp<br>
			Grid Size (X,Y) == 1000,1000<br>
			Write GIS Domain == ..\check\2d_dom_check.shp<br>
			STOP
			</tt>
	\|discussion_page=* [[Talk:TUFLOW Message 2001\|Discuss Message 2001]]		\|discussion_page=* [[Talk:TUFLOW Message 2001\|Discuss Message 2001]]
	\|link3=''		\|link3=''