Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid creating of corruption Shapefiles during Editing/saving. #22485

Closed
qgib opened this issue Mar 16, 2016 · 5 comments
Closed

Avoid creating of corruption Shapefiles during Editing/saving. #22485

qgib opened this issue Mar 16, 2016 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption High Priority
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Mar 16, 2016

Author Name: sarra sahbani (sarra sahbani)
Original Redmine Issue: 14512
Affected QGIS version: 2.14.0
Redmine category:unknown


when digitizing some features (lines/polygons) in QGIS 2.14.0 in shapefile format, and after saving the changes, the current dbf ( or in another case the shx and shp ) file(s) seemed to have been created with the '_packed' attached to the end.
This problem happned frequently.

If the dbf file was renamed, we can't restaure the previous state of the shapes.


Related issue(s): #19349 (duplicates)
Redmine related issue(s): 11007


@qgib
Copy link
Contributor Author

qgib commented Mar 22, 2016

Author Name: Matthias Kuhn (@m-kuhn)


When does this happen exactly? Do you have a reproducible way?

For more information, also read this: http://gis.stackexchange.com/a/79677/9839

@qgib
Copy link
Contributor Author

qgib commented Mar 23, 2016

Author Name: sarra sahbani (sarra sahbani)


Matthias Kuhn wrote:

When does this happen exactly? Do you have a reproducible way?

For more information, also read this: http://gis.stackexchange.com/a/79677/9839

when I digitize many features, or I delete some of them then I save, this problem happened.

@qgib
Copy link
Contributor Author

qgib commented Apr 9, 2016

Author Name: Giovanni Manghi (@gioman)


hope this is not #19349 nightmare all over...

Do you have a specific series of steps we can use to replicate the issue? Thanks in advance.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented May 23, 2016

Author Name: Giovanni Manghi (@gioman)


Giovanni Manghi wrote:

hope this is not #19349 nightmare all over...

it is not #19349 apparently and fortunately (I tested and I confirm is fixed, at least with those steps), anyway there are relates of issues editing shapfiles, but none of them seems to have appropriate steps to replicate, that make troubleshooting very hard.

Please reopen if you find those steps (and meanwhile install the latest version available and try disable all 3rd party plugins).


  • resolution was changed from to not reproducable
  • status_id was changed from Feedback to Closed

@qgib
Copy link
Contributor Author

qgib commented Sep 22, 2017

Author Name: Jürgen Fischer (@jef-n)


  • category_id was configured as Unknown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption High Priority
Projects
None yet
Development

No branches or pull requests

1 participant