QGIS » QGIS Application

Giovanni Manghi wrote:

Ger CO wrote:

I am having the same issue+ double features when saving edits. extremely scary and and very severe issue

qgis version? platform? datasource? sample data?
please do not reopen a the tickets unless we know it is the same exact problem. Leave here as much details as you can, then if necessary I will reopen.

Sorry for being to brief in explaining! I am on win 7 64 bit (2.16.12 / 2.18.3/4). I have had this behavior for months now and it is crucial. It affects shapefiles (either created in ArcGIS or QGIS). The problem is very severe when user do´t know they have to close and reopen the attribute table after saving edits. Otherwise data is usually corrupted, attributes and links get messed up completely. But even if you know how to behave without messung up your data, it is just annoying to handle attribute tables like that... and as much as I like QGIS, this makes me feel uncomfortable editing important data. Hence, this issue is really severe and closing this ticket is notthe right solution in my oppinion. Using the data source attached by the thread opener one can observe this behavior very clearly. Again: this affects all shapefiles (at least on windows).

Again: this affects all shapefiles (at least on windows).

Can you attach a sample of data? I ask because seems obvious that this is not a general issue, otherwise we would have heard a lot more about that.

Have you tried disabling or removing all the 3rd party plugins (and then restart qgis of course)? There are ones that are known to mess up things a lot.

Thanks!

Giovanni Manghi wrote:

Again: this affects all shapefiles (at least on windows).

Can you attach a sample of data? I ask because seems obvious that this is not a general issue, otherwise we would have heard a lot more about that.

Have you tried disabling or removing all the 3rd party plugins (and then restart qgis of course)? There are ones that are known to mess up things a lot.

Thanks!

I will share a dataset and screen recording. I can confirm this behavior when all external plugins are disabled. It seems that this issue is consistently found only when attribute table is opened as dock! Can you confirm this behavior under this circumstance? Thanks for your feedback

I will share a dataset and screen recording. I can confirm this behavior when all external plugins are disabled. It seems that this issue is consistently found only when attribute table is opened as dock! Can you confirm this behavior under this circumstance? Thanks for your feedback

just tested with different shapefiles, and cannot confirm.

Maybe, it is an encoding problem.... As a German citizen I usually work in UTF-8, latin1, and iso 8859-1 for shapefiles. Attached you will find a shapefile I just generated in QGIS (maybe set the encoding to one of the three options I mentioned). As soon as you add a polygon and save the edits you might see the phenomenon of duplicated or disappearing features. Thanks a lot for your help!

tried all you suggest, with the shape you provided, on two different operating systems (Windows and Linux) and no problems whatsoever.
I sometimes miss something obvious in issue reports like this one, but more frequently this symptoms are indicating a local issue. Not sure what of the two is in this case, but unless a clear way to replicate the problem on different machines is found let's keep this closed. If you can try on a different machine, possibly in a clean environment/installations would be great. Thanks!

Giovanni Manghi wrote:

Maybe, it is an encoding problem.... As a German citizen I usually work in UTF-8, latin1, and iso 8859-1 for shapefiles. Attached you will find a shapefile I just generated in QGIS (maybe set the encoding to one of the three options I mentioned). As soon as you add a polygon and save the edits you might see the phenomenon of duplicated or disappearing features. Thanks a lot for your help!

tried all you suggest, with the shape you provided, on two different operating systems (Windows and Linux) and no problems whatsoever.
I sometimes miss something obvious in issue reports like this one, but more frequently this symptoms are indicating a local issue. Not sure what of the two is in this case, but unless a clear way to replicate the problem on different machines is found let's keep this closed. If you can try on a different machine, possibly in a clean environment/installations would be great. Thanks!

That is sad, since I am currently on three individual machines: two with win7 64, one with win 10 64. It´s the same on all my machines. And same counts for my collegues at work. I am telling the truth! Really strange. Thanks anyway

That is sad, since I am currently on three individual machines: two with win7 64, one with win 10 64. It´s the same on all my machines. And same counts for my collegues at work. I am telling the truth! Really strange. Thanks anyway

so maybe is me :) anyway, the test on a clean system would tell us a lot, is doable?

Giovanni Manghi wrote:

That is sad, since I am currently on three individual machines: two with win7 64, one with win 10 64. It´s the same on all my machines. And same counts for my collegues at work. I am telling the truth! Really strange. Thanks anyway

so maybe is me :) anyway, the test on a clean system would tell us a lot, is doable?

The windows 10 installation is just one month old, but I can certainly redo it! Just out of interest, I checked the behavior for geopackages. It seems these errors do not apply to that file format.

The windows 10 installation is just one month old, but I can certainly redo it!

I appreciate it. Very curious to see what happens on clean enviroment. Please test with 1) a shape created from scratch on the new installation 2) a shape created (and handled) previously only with QGIS 3) a shape created and handled previously only with another gis package (arcgis?)

of course install 2.18.4

Just out of interest, I checked the behavior for geopackages. It seems these errors do not apply to that file format.

interesting

Giovanni Manghi wrote:

The windows 10 installation is just one month old, but I can certainly redo it!

I appreciate it. Very curious to see what happens on clean enviroment. Please test with 1) a shape created from scratch on the new installation 2) a shape created (and handled) previously only with QGIS 3) a shape created and handled previously only with another gis package (arcgis?)

of course install 2.18.4

Just out of interest, I checked the behavior for geopackages. It seems these errors do not apply to that file format.

interesting

Will do so and be back with the results on the weekend! Thanks

Will do so and be back with the results on the weekend! Thanks

by the way, I also cannot confirm yours #16236 too