TUFLOW Message 0300 - Revision history

Pavlina Monhartova at 12:51, 2 October 2024

2024-10-02T12:51:02Z

← Older revision		Revision as of 22:51, 2 October 2024
Line 7:		Line 7:
	At user request for the 2016 version of TUFLOW these have been added to the _messages.mif or _messages_P.shp file to make these messages more noticeable. For the 2016 version of TUFLOW, non-spatial messages are now written to the GIS messages layer at the top right coordinate of the model domain. However, a number of messages can occur before the geometry control file (.tgc) has been processed and the model domain is not known. To ensure that these are included in the spatial layer, after the model domain is known the _messages.csv is read and the messages written spatially.<br>		At user request for the 2016 version of TUFLOW these have been added to the _messages.mif or _messages_P.shp file to make these messages more noticeable. For the 2016 version of TUFLOW, non-spatial messages are now written to the GIS messages layer at the top right coordinate of the model domain. However, a number of messages can occur before the geometry control file (.tgc) has been processed and the model domain is not known. To ensure that these are included in the spatial layer, after the model domain is known the _messages.csv is read and the messages written spatially.<br>
	Warning 0300 will occur if there is an issue when reading the _messages.csv during initialisation.		Warning 0300 will occur if there is an issue when reading the _messages.csv during initialisation.
	\|suggestions=~~Please contact <font color="blue">support@tuflow.com</font> and send through~~ the ~~log~~ ~~(.tlf)~~ ~~file~~ ~~for~~ ~~the simulation~~. Check the _messages.csv or log file as there may be additional messages that are not in the GIS messages layer.		\|suggestions=Ensure the latest TUFLOW release is used. Check the _messages.csv or log file as there may be additional messages that are not in the GIS messages layer.
	<br>		<br>

Melissa.Moghanloo at 01:10, 22 December 2022

2022-12-22T01:10:57Z

← Older revision		Revision as of 11:10, 22 December 2022
Line 9:		Line 9:
	\|suggestions=Please contact <font color="blue">support@tuflow.com</font> and send through the log (.tlf) file for the simulation. Check the _messages.csv or log file as there may be additional messages that are not in the GIS messages layer.		\|suggestions=Please contact <font color="blue">support@tuflow.com</font> and send through the log (.tlf) file for the simulation. Check the _messages.csv or log file as there may be additional messages that are not in the GIS messages layer.
	<br>		<br>

	\|prelink=[[TUFLOW_Message_0255\|Message 0255]]
	\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]		\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]
	\|nextlink=[[TUFLOW_Message_0301\|Message 0301]]
	}}		}}

Melissa.Moghanloo at 01:11, 4 July 2022

2022-07-04T01:11:44Z

← Older revision		Revision as of 11:11, 4 July 2022
Line 7:		Line 7:
	At user request for the 2016 version of TUFLOW these have been added to the _messages.mif or _messages_P.shp file to make these messages more noticeable. For the 2016 version of TUFLOW, non-spatial messages are now written to the GIS messages layer at the top right coordinate of the model domain. However, a number of messages can occur before the geometry control file (.tgc) has been processed and the model domain is not known. To ensure that these are included in the spatial layer, after the model domain is known the _messages.csv is read and the messages written spatially.<br>		At user request for the 2016 version of TUFLOW these have been added to the _messages.mif or _messages_P.shp file to make these messages more noticeable. For the 2016 version of TUFLOW, non-spatial messages are now written to the GIS messages layer at the top right coordinate of the model domain. However, a number of messages can occur before the geometry control file (.tgc) has been processed and the model domain is not known. To ensure that these are included in the spatial layer, after the model domain is known the _messages.csv is read and the messages written spatially.<br>
	Warning 0300 will occur if there is an issue when reading the _messages.csv during initialisation.		Warning 0300 will occur if there is an issue when reading the _messages.csv during initialisation.
	\|suggestions=Please contact <font color="blue"~~><u~~>support@tuflow.com~~</u>~~</font> and send through the log (.tlf) file for the simulation. Check the _messages.csv or log file as there may be additional messages that are not in the GIS messages layer.		\|suggestions=Please contact <font color="blue">support@tuflow.com</font> and send through the log (.tlf) file for the simulation. Check the _messages.csv or log file as there may be additional messages that are not in the GIS messages layer.
	<br>		<br>
	\|prelink=[[TUFLOW_Message_0255\|Message 0255]]		\|prelink=[[TUFLOW_Message_0255\|Message 0255]]

Melissa.Moghanloo at 04:49, 1 July 2022

2022-07-01T04:49:40Z

← Older revision		Revision as of 14:49, 1 July 2022
Line 4:		Line 4:
	\|alt_msg=NA		\|alt_msg=NA
	\|type=[[WARNING]]		\|type=[[WARNING]]
	\|message_desc=The majority of TUFLOW messages have a spatial location (for example a cell elevation that has not been assigned), however, some messages such as [[TUFLOW_Message_1298]] have no spatial location. The spatial locations are written to the GIS layer (_messages.mif or _messages_P.shp) and also to the _messages.csv file. Prior to the 2016 version of TUFLOW, the non-spatial messages were only written to the _messages.csv.<br>		\|message_desc=The majority of TUFLOW messages have a spatial location (for example a cell elevation that has not been assigned), however, some messages such as <u>[[TUFLOW_Message_1298]]</u> have no spatial location. The spatial locations are written to the GIS layer (_messages.mif or _messages_P.shp) and also to the _messages.csv file. Prior to the 2016 version of TUFLOW, the non-spatial messages were only written to the _messages.csv.<br>
	At user request for the 2016 version of TUFLOW these have been added to the _messages.mif or _messages_P.shp file to make these messages more noticeable. For the 2016 version of TUFLOW, non-spatial messages are now written to the GIS messages layer at the top right coordinate of the model domain. However, a number of messages can occur before the geometry control file (.tgc) has been processed and the model domain is not known. To ensure that these are included in the spatial layer, after the model domain is known the _messages.csv is read and the messages written spatially.<br>		At user request for the 2016 version of TUFLOW these have been added to the _messages.mif or _messages_P.shp file to make these messages more noticeable. For the 2016 version of TUFLOW, non-spatial messages are now written to the GIS messages layer at the top right coordinate of the model domain. However, a number of messages can occur before the geometry control file (.tgc) has been processed and the model domain is not known. To ensure that these are included in the spatial layer, after the model domain is known the _messages.csv is read and the messages written spatially.<br>
	Warning 0300 will occur if there is an issue when reading the _messages.csv during initialisation.		Warning 0300 will occur if there is an issue when reading the _messages.csv during initialisation.
	\|suggestions=Please contact <font color="blue"><u>support@tuflow.com</u></font> and send through the log (.tlf) file for the simulation. Check the _messages.csv or log file as there may be additional messages that are not in the GIS messages layer.		\|suggestions=Please contact <font color="blue"><u>support@tuflow.com</u></font> and send through the log (.tlf) file for the simulation. Check the _messages.csv or log file as there may be additional messages that are not in the GIS messages layer.
			<br>
	\|discussion_page=* [[Talk:TUFLOW Message 0302\|Discuss Message 0302]]
	\|link3=''
	\|link4=''
	\|prelink=[[TUFLOW_Message_0255\|Message 0255]]		\|prelink=[[TUFLOW_Message_0255\|Message 0255]]
	\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]		\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]

Par: Created page with "{{TUFLOW_Message |tuflow_message=WARNING 0300 - Problem with reading messages.csv file - please contact support@tuflow.com.
Some or all non-spatial messages may not appear..."

2016-01-12T01:51:55Z

Created page with "{{TUFLOW_Message |tuflow_message=WARNING 0300 - Problem with reading messages.csv file - please contact support@tuflow.com. Some or all non-spatial messages may not appear..."

New page

{{TUFLOW_Message
|tuflow_message=WARNING 0300 - Problem with reading messages.csv file - please contact support@tuflow.com. 
Some or all non-spatial messages may not appear in _messages GIS layer.
|alt_msg=NA
|type=[[WARNING]]
|message_desc=The majority of TUFLOW messages have a spatial location (for example a cell elevation that has not been assigned), however, some messages such as [[TUFLOW_Message_1298]] have no spatial location. The spatial locations are written to the GIS layer (_messages.mif or _messages_P.shp) and also to the _messages.csv file. Prior to the 2016 version of TUFLOW, the non-spatial messages were only written to the _messages.csv. 
At user request for the 2016 version of TUFLOW these have been added to the _messages.mif or _messages_P.shp file to make these messages more noticeable. For the 2016 version of TUFLOW, non-spatial messages are now written to the GIS messages layer at the top right coordinate of the model domain. However, a number of messages can occur before the geometry control file (.tgc) has been processed and the model domain is not known. To ensure that these are included in the spatial layer, after the model domain is known the _messages.csv is read and the messages written spatially. 
Warning 0300 will occur if there is an issue when reading the _messages.csv during initialisation.
|suggestions=Please contact support@tuflow.com and send through the log (.tlf) file for the simulation. Check the _messages.csv or log file as there may be additional messages that are not in the GIS messages layer.
|discussion_page=* [[Talk:TUFLOW Message 0302|Discuss Message 0302]]
|link3=''
|link4=''
|prelink=[[TUFLOW_Message_0255|Message 0255]]
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]]
|nextlink=[[TUFLOW_Message_0301|Message 0301]]
}}

TUFLOW Message 0300 - Revision history

Pavlina Monhartova at 12:51, 2 October 2024

Melissa.Moghanloo at 01:10, 22 December 2022

Melissa.Moghanloo at 01:11, 4 July 2022

Melissa.Moghanloo at 04:49, 1 July 2022

Par: Created page with "{{TUFLOW_Message |tuflow_message=WARNING 0300 - Problem with reading messages.csv file - please contact support@tuflow.com. Some or all non-spatial messages may not appear..."

Par: Created page with "{{TUFLOW_Message |tuflow_message=WARNING 0300 - Problem with reading messages.csv file - please contact support@tuflow.com.
Some or all non-spatial messages may not appear..."