TUFLOW Message 2148 - Revision history

Melissa.Moghanloo at 03:42, 7 February 2023

2023-02-07T03:42:19Z

← Older revision		Revision as of 13:42, 7 February 2023
Line 13:		Line 13:



	\|prelink=[[TUFLOW_Message_2147\|Message 2147]]
	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]

	\|nextlink=[[TUFLOW_Message_2149\|Message 2149]]
	}}		}}

Pavlina Monhartova at 06:45, 27 July 2022

2022-07-27T06:45:15Z

← Older revision		Revision as of 16:45, 27 July 2022
Line 8:		Line 8:
	* The data attributes in GIS layer do not match the TUFLOW file type.		* The data attributes in GIS layer do not match the TUFLOW file type.
	\|suggestions=Use the latest available TUFLOW release from the <u>[https://www.tuflow.com/downloads/ TUFLOW website]</u>.<br>		\|suggestions=Use the latest available TUFLOW release from the <u>[https://www.tuflow.com/downloads/ TUFLOW website]</u>.<br>
	Review the Name attribute. If the data has been manipulated, e.g. in .csv file, check the manipulation process has been successful. Review the Name attributes.<br>		Review the Name attribute and remove special characters and/or new lines. If the data has been manipulated, e.g. in .csv file, check the manipulation process has been successful. Review the Name attributes.<br>
	Shapefiles might have a dummy value in the TUFLOW empty files. The dummy value does not have a geometry feature associated with it. This will be the first entry shown in the files attribute table. Delete the dummy entry.		Shapefiles might have a dummy value in the TUFLOW empty files. The dummy value does not have a geometry feature associated with it. This will be the first entry shown in the files attribute table. Delete the dummy entry.
	For MapInfo files, check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. Check the file is being read in correctly, for example if reading a 1d_nwk layer, the command would be Read GIS Network, if a read GIS BC command was used the data type may not match.		For MapInfo files, check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. Check the file is being read in correctly, for example if reading a 1d_nwk layer, the command would be Read GIS Network, if a read GIS BC command was used the data type may not match.

Pavlina Monhartova at 06:23, 27 July 2022

2022-07-27T06:23:15Z

← Older revision		Revision as of 16:23, 27 July 2022
Line 1:		Line 1:
	{{TUFLOW_Message		{{TUFLOW_Message
	\|tuflow_message=ERROR 2148 - Reading ~~line~~ in ~~MID~~ ~~file~~ ~~or premature end of~~ ~~file~~.		\|tuflow_message=ERROR 2148 - Reading attribute data from data line below.
	\|alt_msg=ERROR 2148 - Reading ~~attribute~~ ~~data~~ ~~from~~ ~~data~~ ~~line~~ ~~below~~.		\|alt_msg=ERROR 2148 - Reading line in MID file or premature end of file.
	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=~~Reading line in MID file or premature end of file. This indicates that the~~ data in the in .shp or .MID file is not in the format that TUFLOW is expecting. This could be because:<br>		\|message_desc=The data in the in .shp or .MID file is not in the format that TUFLOW is expecting. This could be because:<br>
			* The attributes have some special characters or additional new lines.
	* The geometry attributes in the .MIF file and the field data in the .MID file do not match. ~~The following is an extract from the .MIF file for a 2d_code layer:~~		* The geometry attributes in the .MIF file and the field data in the .MID file do not match.
	<pre>
		⚫	* The data attributes in GIS layer do not match the TUFLOW file type.
	Columns 1
	Code Integer
	Data
	</pre>
	This indicates that there is a single data column (attribute), this is named "Code" and is an integer type attribute. The corresponding .MIF should have only a single entry on each line:
	<pre>
	1
	</pre>
⚫	* The data attributes in ~~the~~ ~~MapInfo file~~ do not match the TUFLOW file type.
	\|suggestions=Use the latest available TUFLOW release from the <u>[https://www.tuflow.com/downloads/ TUFLOW website]</u>.<br>		\|suggestions=Use the latest available TUFLOW release from the <u>[https://www.tuflow.com/downloads/ TUFLOW website]</u>.<br>
	~~Check that~~ the ~~number of columns in the .MIF and .MID match, exporting from MapInfo should ensure~~ ~~this~~. If the data has been manipulated, e.g. in .csv file. ~~Check~~ the manipulation process has been successful.<br>		Review the Name attribute. If the data has been manipulated, e.g. in .csv file, check the manipulation process has been successful. Review the Name attributes.<br>
		⚫	Shapefiles might have a dummy value in the TUFLOW empty files. The dummy value does not have a geometry feature associated with it. This will be the first entry shown in the files attribute table. Delete the dummy entry.
	* MapInfo: Check the file is being read in correctly. ~~For~~ example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.		For MapInfo files, check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. Check the file is being read in correctly, for example if reading a 1d_nwk layer, the command would be Read GIS Network, if a read GIS BC command was used the data type may not match.
⚫	* ~~ArcGIS:~~ ~~ArcGIS will create~~ a dummy value in the TUFLOW empty files. The dummy value does not have a geometry feature associated with it. This will be the first entry shown in the files attribute table. Delete the dummy entry.


	\|prelink=[[TUFLOW_Message_2147\|Message 2147]]		\|prelink=[[TUFLOW_Message_2147\|Message 2147]]

Melissa.Moghanloo at 03:47, 6 July 2022

2022-07-06T03:47:32Z

← Older revision		Revision as of 13:47, 6 July 2022
Line 19:		Line 19:
	* MapInfo: Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.		* MapInfo: Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.
	* ArcGIS: ArcGIS will create a dummy value in the TUFLOW empty files. The dummy value does not have a geometry feature associated with it. This will be the first entry shown in the files attribute table. Delete the dummy entry.		* ArcGIS: ArcGIS will create a dummy value in the TUFLOW empty files. The dummy value does not have a geometry feature associated with it. This will be the first entry shown in the files attribute table. Delete the dummy entry.

	\|discussion_page=* [[Talk:TUFLOW Message 2148\|Discuss Message 2148]]
	\|link3=''
	\|link4=''
	\|prelink=[[TUFLOW_Message_2147\|Message 2147]]		\|prelink=[[TUFLOW_Message_2147\|Message 2147]]
	\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]		\|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]]

Pavlina Monhartova at 01:10, 3 March 2021

2021-03-03T01:10:35Z

← Older revision		Revision as of 11:10, 3 March 2021
Line 15:		Line 15:
	</pre>		</pre>
	* The data attributes in the MapInfo file do not match the TUFLOW file type.		* The data attributes in the MapInfo file do not match the TUFLOW file type.
	\|suggestions=Use the latest available TUFLOW release from the [https://www.tuflow.com/downloads/ TUFLOW website].<br>		\|suggestions=Use the latest available TUFLOW release from the <u>[https://www.tuflow.com/downloads/ TUFLOW website]</u>.<br>
	Check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. If the data has been manipulated, e.g. in .csv file. Check the manipulation process has been successful.<br>		Check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. If the data has been manipulated, e.g. in .csv file. Check the manipulation process has been successful.<br>
	* MapInfo: Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.		* MapInfo: Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.

Pavlina Monhartova at 01:10, 3 March 2021

2021-03-03T01:10:09Z

← Older revision		Revision as of 11:10, 3 March 2021
Line 15:		Line 15:
	</pre>		</pre>
	* The data attributes in the MapInfo file do not match the TUFLOW file type.		* The data attributes in the MapInfo file do not match the TUFLOW file type.
			\|suggestions=Use the latest available TUFLOW release from the [https://www.tuflow.com/downloads/ TUFLOW website].<br>
	~~\|suggestions=~~Check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. If the data has been manipulated, e.g. in .csv file. Check the manipulation process has been successful.<br>		Check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. If the data has been manipulated, e.g. in .csv file. Check the manipulation process has been successful.<br>
	* MapInfo: Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.		* MapInfo: Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.
	* ArcGIS: ArcGIS will create a dummy value in the TUFLOW empty files. The dummy value does not have a geometry feature associated with it. This will be the first entry shown in the files attribute table. Delete the dummy entry.		* ArcGIS: ArcGIS will create a dummy value in the TUFLOW empty files. The dummy value does not have a geometry feature associated with it. This will be the first entry shown in the files attribute table. Delete the dummy entry.

Chris Huxley at 19:17, 20 May 2015

2015-05-20T19:17:24Z

← Older revision		Revision as of 05:17, 21 May 2015
Line 17:		Line 17:
	\|suggestions=Check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. If the data has been manipulated, e.g. in .csv file. Check the manipulation process has been successful.<br>		\|suggestions=Check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. If the data has been manipulated, e.g. in .csv file. Check the manipulation process has been successful.<br>
	* MapInfo: Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.		* MapInfo: Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.
	* ArcGIS: ArcGIS will create a dummy value in the TUFLOW empty files. The dummy value does not have geometry ~~features~~ associated with it. ~~this~~ will be the first entry shown in the files attribute table. Delete the dummy entry.		* ArcGIS: ArcGIS will create a dummy value in the TUFLOW empty files. The dummy value does not have a geometry feature associated with it. This will be the first entry shown in the files attribute table. Delete the dummy entry.
	\|discussion_page=* [[Talk:TUFLOW Message 2148\|Discuss Message 2148]]		\|discussion_page=* [[Talk:TUFLOW Message 2148\|Discuss Message 2148]]
	\|link3=''		\|link3=''

Chris Huxley at 18:52, 20 May 2015

2015-05-20T18:52:38Z

← Older revision		Revision as of 04:52, 21 May 2015
Line 3:		Line 3:
	\|alt_msg=ERROR 2148 - Reading attribute data from data line below.		\|alt_msg=ERROR 2148 - Reading attribute data from data line below.
	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=Reading line in MID file or premature end of file. This indicates that the data in the in .MID file is not in the format that TUFLOW is expecting. This could be because:<br>		\|message_desc=Reading line in MID file or premature end of file. This indicates that the data in the in .shp or .MID file is not in the format that TUFLOW is expecting. This could be because:<br>
	* The attributes in the .MIF file and the data in the .MID file do not match. The following is an extract from the .MIF file for a 2d_code layer:		* The geometry attributes in the .MIF file and the field data in the .MID file do not match. The following is an extract from the .MIF file for a 2d_code layer:
	<pre>		<pre>
	Columns 1		Columns 1

Chris Huxley at 18:16, 20 May 2015

2015-05-20T18:16:52Z

← Older revision		Revision as of 04:16, 21 May 2015
Line 16:		Line 16:
	* The data attributes in the MapInfo file do not match the TUFLOW file type.		* The data attributes in the MapInfo file do not match the TUFLOW file type.
	\|suggestions=Check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. If the data has been manipulated, e.g. in .csv file. Check the manipulation process has been successful.<br>		\|suggestions=Check that the number of columns in the .MIF and .MID match, exporting from MapInfo should ensure this. If the data has been manipulated, e.g. in .csv file. Check the manipulation process has been successful.<br>
	Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.		* MapInfo: Check the file is being read in correctly. For example if reading a 1d_nwk layer, the command would be Read GIS Network. If a read GIS BC command was used the data type may not match.
			* ArcGIS: ArcGIS will create a dummy value in the TUFLOW empty files. The dummy value does not have geometry features associated with it. this will be the first entry shown in the files attribute table. Delete the dummy entry.
	\|discussion_page=* [[Talk:TUFLOW Message 2148\|Discuss Message 2148]]		\|discussion_page=* [[Talk:TUFLOW Message 2148\|Discuss Message 2148]]
	\|link3=''		\|link3=''

Chris Huxley at 18:13, 20 May 2015

2015-05-20T18:13:42Z

← Older revision		Revision as of 04:13, 21 May 2015
Line 1:		Line 1:
	{{TUFLOW_Message		{{TUFLOW_Message
	\|tuflow_message=ERROR 2148 - Reading line in MID file or premature end of file.		\|tuflow_message=ERROR 2148 - Reading line in MID file or premature end of file.
			\|alt_msg=ERROR 2148 - Reading attribute data from data line below.
	\|alt_msg=NA
	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=Reading line in MID file or premature end of file. This indicates that the data in the in .MID file is not in the format that TUFLOW is expecting. This could be because:<br>		\|message_desc=Reading line in MID file or premature end of file. This indicates that the data in the in .MID file is not in the format that TUFLOW is expecting. This could be because:<br>