Difference between revisions of "TUFLOW Message 2148"
| Line 3: | Line 3: | ||
|alt_msg=NA | |alt_msg=NA | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
| − | |message_desc=Reading line in MID file or premature end of file. | + | |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> |
| − | |suggestions= | + | * 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: |
| + | <pre> | ||
| + | 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=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]] | |discussion_page=* [[Talk:TUFLOW Message 2148|Discuss Message 2148]] | ||
|link3='' | |link3='' | ||
Revision as of 13:47, 6 March 2012
TUFLOW Message
ERROR 2148 - Reading line in MID file or premature end of file.
Alternate Message
NA
Message Type
ERROR
Description
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:
- 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:
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
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.
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.
| Up |
|---|
 2xxx Messages
|