You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Antoine SIG (Antoine SIG)
Original Redmine Issue: 13319
Affected QGIS version: 2.10.1
Hey,
I have a problem : if the shapefile have sbx and/or sbn files, there is an issue with split polygons... only with QGIS 2.10.
To reproduce, using attachment :
On 2.10, open the shapefile, split a polygon, save, and layer appears with bugs. If you delete sbn file, there is no problem.
On 2.8, with the same split, no issue => sbn is here, but QGIS don't use it ?! And if you save the layer (after split) on 2.8, and open with 2.10, there is not problem to.
If you edit the file with multiple operation without saving (split, merge, add features...), the shapefile become corrupt :(
GDAL uses .sbn index read-only. When shapefile is saved after edits GDAL should delete the obsolete .sbn file. You say that it does not happen so I would call that as a bug. Not sure if it is bug in QGIS or GDAL. Perhaps QGIS keeps .sbn locked so it can't be deleted?
Read https://trac.osgeo.org/gdal/ticket/6042. You may be able to help Even who wrote: "a reproducable scenario that would demonstrate a failure in removing them would be interesting."
Author Name: Antoine SIG (Antoine SIG)
Original Redmine Issue: 13319
Affected QGIS version: 2.10.1
Hey,
I have a problem : if the shapefile have sbx and/or sbn files, there is an issue with split polygons... only with QGIS 2.10.
To reproduce, using attachment :
On 2.10, open the shapefile, split a polygon, save, and layer appears with bugs. If you delete sbn file, there is no problem.
On 2.8, with the same split, no issue => sbn is here, but QGIS don't use it ?! And if you save the layer (after split) on 2.8, and open with 2.10, there is not problem to.
If you edit the file with multiple operation without saving (split, merge, add features...), the shapefile become corrupt :(
The text was updated successfully, but these errors were encountered: