Difference between revisions of "TUFLOW Message 0408"
Melissa1987 (talk | contribs) |
|||
| Line 5: | Line 5: | ||
|message_desc=As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag. | |message_desc=As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag. | ||
|suggestions=If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record. | |suggestions=If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record. | ||
| − | + | <br> | |
| − | |||
| − | |||
|prelink=[[TUFLOW_Message_0407|Message 0407]] | |prelink=[[TUFLOW_Message_0407|Message 0407]] | ||
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | ||
|nextlink=[[TUFLOW_Message_0411|Message 0411]] | |nextlink=[[TUFLOW_Message_0411|Message 0411]] | ||
}} | }} | ||
Revision as of 11:05, 1 July 2022
TUFLOW Message
ERROR 0408 - End of .dbf file encountered whilst reading record.
Alternate Message
NA
Message Type
ERROR
Description
As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag.
Suggestions
If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record.
| Up |
|---|
 0xxx Messages
|