TUFLOW Message 2148: Difference between revisions

Content deleted Content added
No edit summary
No edit summary
 
(8 intermediate revisions by 3 users not shown)
Line 1:
{{TUFLOW_Message
|tuflow_message=ERROR 2148 - Reading lineattribute indata MIDfrom filedata or premature end ofline filebelow.
|alt_msg=ERROR 2148 - Reading attributeline datain fromMID datafile lineor premature end of belowfile.
|type=[[ERROR]]
|message_desc=ReadingThe linedata in MID file or premature end of file. This indicates that the data in the.shp inor .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:
<pre>
* The data attributes in theGIS MapInfo filelayer do not match the TUFLOW file type.
Columns 1
|suggestions=Use the latest available TUFLOW release from the <u>[https://www.tuflow.com/downloads/ TUFLOW website]</u>.<br>
Code Integer
|suggestions=Check thatReview the numberName ofattribute columnsand inremove thespecial .MIFcharacters and/or .MID match, exporting from MapInfo should ensurenew thislines. If the data has been manipulated, e.g. in .csv file., Checkcheck the manipulation process has been successful. Review the Name attributes.<br>
Data
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.
</pre>
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., Forfor example if reading a 1d_nwk layer, the command would be Read GIS Network., Ifif a read GIS BC command was used the data type may not match.
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=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.
|discussion_page=* [[Talk:TUFLOW Message 2148|Discuss Message 2148]]
|link3=''
|link4=''
|prelink=[[TUFLOW_Message_2147|Message 2147]]
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
 
|nextlink=[[TUFLOW_Message_2149|Message 2149]]
}}