Difference between revisions of "TUFLOW Message 2148"
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{TUFLOW_Message | {{TUFLOW_Message | ||
| − | |tuflow_message=ERROR 2148 - Reading line | + | |tuflow_message=ERROR 2148 - Reading attribute data from data line below. |
| − | |alt_msg=ERROR 2148 - Reading | + | |alt_msg=ERROR 2148 - Reading line in MID file or premature end of file. |
|type=[[ERROR]] | |type=[[ERROR]] | ||
| − | |message_desc= | + | |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 geometry attributes in the .MIF file and the field data in the .MID file do not match. | + | * 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 data attributes in GIS layer do not match the TUFLOW file type. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | * The data attributes in | ||
|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 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. | |
| − | + | 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. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | |||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
| − | + | ||
}} | }} | ||
Latest revision as of 13:42, 7 February 2023
TUFLOW Message
ERROR 2148 - Reading attribute data from data line below.
Alternate Message
ERROR 2148 - Reading line in MID file or premature end of file.
Message Type
ERROR
Description
The data in the in .shp or .MID file is not in the format that TUFLOW is expecting. This could be because:
- 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 data attributes in GIS layer do not match the TUFLOW file type.
Suggestions
Use the latest available TUFLOW release from the TUFLOW website.
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.
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.
| Up |
|---|
 2xxx Messages
|