Revision as of 13:47, 6 July 2022 view source Melissa.Moghanloo (talk \| contribs) Bureaucrats, Administrators 2,918 edits No edit summary ← Older edit		Revision as of 16:23, 27 July 2022 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,366 edits No edit summary Newer edit →
Line 1: {{TUFLOW_Message \|tuflow_message=ERROR 2148 - Reading ~~line~~attribute indata ~~MID~~from ~~file~~data ~~or premature end of~~line ~~file~~below. \|alt_msg=ERROR 2148 - Reading ~~attribute~~line ~~data~~in ~~from~~MID ~~data~~file ~~line~~or premature end of ~~below~~file. \|type=[[ERROR]] \|message_desc=~~Reading line in MID file or premature end of file. This indicates that the~~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:~~ ~~<pre>~~ * The data attributes in ~~the~~GIS ~~MapInfo file~~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> ~~Check that~~Review the ~~number of columns in the .MIF and .MID match, exporting from MapInfo should ensure~~Name ~~this~~attribute. If the data has been manipulated, e.g. in .csv file., ~~Check~~check the manipulation process has been successful. Review the Name attributes.<br> Shapefiles ~~ArcGIS:~~might ~~ArcGIS will create~~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~~for 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. ▲* 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]]

TUFLOW Message 2148: Difference between revisions