TUFLOW Message 0320 - Revision history

Emilie Nielsen at 05:04, 28 May 2025

2025-05-28T05:04:08Z

← Older revision		Revision as of 15:04, 28 May 2025
Line 4:		Line 4:
	\|type=[[WARNING]]		\|type=[[WARNING]]
	\|message_desc=A number of error messages can be triggered before TUFLOW initialises any GIS properties (projection, format etc.) and therefore these messages cannot be written to the messsage_P.shp file immediately. When the GIS properties are initialised, any messages that occurred prior to this will be copied into the messages_P.shp file. This error occurs when the message.csv cannot be opened (or does not exist) and therefore it is unable to copy any prior messages. TUFLOW will be able to write any subsequent messages to the message_P.shp but the GIS layer may be missing some message entries that occurred very early on in the pre-processing.		\|message_desc=A number of error messages can be triggered before TUFLOW initialises any GIS properties (projection, format etc.) and therefore these messages cannot be written to the messsage_P.shp file immediately. When the GIS properties are initialised, any messages that occurred prior to this will be copied into the messages_P.shp file. This error occurs when the message.csv cannot be opened (or does not exist) and therefore it is unable to copy any prior messages. TUFLOW will be able to write any subsequent messages to the message_P.shp but the GIS layer may be missing some message entries that occurred very early on in the pre-processing.
	\|suggestions=Double check the existence of the messages.csv file. This warning should not stop the simulation, but the user should be aware that the message_P.shp layer may be missing some initial logging. Please ~~get into~~ contact ~~with~~		\|suggestions=Double check the existence of the messages.csv file. This warning should not stop the simulation, but the user should be aware that the message_P.shp layer may be missing some initial logging. Please contact
	[mailto:support@tuflow.com support@tuflow.com] if this ~~error message~~ persists.		[mailto:support@tuflow.com support@tuflow.com] if this warning persists.
	\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]		\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]
	}}		}}

Ellis Symons at 12:52, 27 May 2025

2025-05-27T12:52:17Z

← Older revision		Revision as of 22:52, 27 May 2025
Line 4:		Line 4:
	\|type=[[WARNING]]		\|type=[[WARNING]]
	\|message_desc=A number of error messages can be triggered before TUFLOW initialises any GIS properties (projection, format etc.) and therefore these messages cannot be written to the messsage_P.shp file immediately. When the GIS properties are initialised, any messages that occurred prior to this will be copied into the messages_P.shp file. This error occurs when the message.csv cannot be opened (or does not exist) and therefore it is unable to copy any prior messages. TUFLOW will be able to write any subsequent messages to the message_P.shp but the GIS layer may be missing some message entries that occurred very early on in the pre-processing.		\|message_desc=A number of error messages can be triggered before TUFLOW initialises any GIS properties (projection, format etc.) and therefore these messages cannot be written to the messsage_P.shp file immediately. When the GIS properties are initialised, any messages that occurred prior to this will be copied into the messages_P.shp file. This error occurs when the message.csv cannot be opened (or does not exist) and therefore it is unable to copy any prior messages. TUFLOW will be able to write any subsequent messages to the message_P.shp but the GIS layer may be missing some message entries that occurred very early on in the pre-processing.
	\|suggestions=Double check the existence of the messages.csv file. This warning should not stop the simulation, but the user should be aware that the message_P.shp layer may be missing some initial logging.		\|suggestions=Double check the existence of the messages.csv file. This warning should not stop the simulation, but the user should be aware that the message_P.shp layer may be missing some initial logging. Please get into contact with
			[mailto:support@tuflow.com support@tuflow.com] if this error message persists.

	\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]		\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]
	}}		}}

Ellis Symons at 12:49, 27 May 2025

2025-05-27T12:49:36Z

← Older revision		Revision as of 22:49, 27 May 2025
Line 3:		Line 3:
	\|alt_msg=NA		\|alt_msg=NA
	\|type=[[WARNING]]		\|type=[[WARNING]]
			\|message_desc=A number of error messages can be triggered before TUFLOW initialises any GIS properties (projection, format etc.) and therefore these messages cannot be written to the messsage_P.shp file immediately. When the GIS properties are initialised, any messages that occurred prior to this will be copied into the messages_P.shp file. This error occurs when the message.csv cannot be opened (or does not exist) and therefore it is unable to copy any prior messages. TUFLOW will be able to write any subsequent messages to the message_P.shp but the GIS layer may be missing some message entries that occurred very early on in the pre-processing.
	\|message_desc=
			\|suggestions=Double check the existence of the messages.csv file. This warning should not stop the simulation, but the user should be aware that the message_P.shp layer may be missing some initial logging.
	\|suggestions=

	\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]		\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]

Emilie Nielsen: Created page with "{{TUFLOW_Message |tuflow_message=WARNING 0320 – Unable to open messages.csv file – please contact support@tuflow.com. Non-spatial messages will not appear in the _messages..."

2025-05-14T02:57:20Z

Created page with "{{TUFLOW_Message |tuflow_message=WARNING 0320 – Unable to open messages.csv file – please contact support@tuflow.com. Non-spatial messages will not appear in the _messages..."

New page

{{TUFLOW_Message
|tuflow_message=WARNING 0320 – Unable to open messages.csv file – please contact support@tuflow.com. Non-spatial messages will not appear in the _messages GIS layer.
|alt_msg=NA
|type=[[WARNING]]
|message_desc=
|suggestions=

|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]]
}}