Difference between revisions of "TUFLOW Message 2148"
| 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. | ||
Revision as of 11:10, 3 March 2021
TUFLOW Message
ERROR 2148 - Reading line in MID file or premature end of file.
Alternate Message
ERROR 2148 - Reading attribute data from data line below.
Message Type
ERROR
Description
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:
- 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:
Columns 1 Code Integer Data
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:
1
- The data attributes in the MapInfo file do not match the TUFLOW file type.
Suggestions
Use the latest available TUFLOW release from the TUFLOW website.
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.
- 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.
| Up |
|---|
 2xxx Messages
|