search

qgis / QGIS

QGIS is a free, open source, cross platform (lin/win/mac) geographical information system (GIS)
https://qgis.org
GNU General Public License v2.0
10.56k stars 3k forks source link

Polygon geometries delete themselves when saving .shp files after editing (QGIS 3.22) #48005

Open MoltenRainbow opened 2 years ago

MoltenRainbow commented 2 years ago

What is the bug or the crash?

When saving changes that have been made to polygon geometries during digitizing, they vanish completely.

I work with shapefile vectors when digitizing drawings for my employer and very often entire geometries will simply vanish when I press the save layer edits button after having made any sort of edits. Not just the geometry itself will disappear but also the data in the attribute table will be gone entirely. Sometimes, when it concerns a few connected or overlapping geometries I can salvage things by moving a few nodes that overlap and save again, which might then prompts the vanished polygon to reappear. However this doesn't always work either and more often than not I am forced to re-draw entire sections of my work several times before I finally have a complete dataset.

When digitizing, I have georeferenced raster files as my underlying layer, since these hold the data that I need to digitize for my employer (often drawings made during field work or boundaries and plans of outdoor work areas). I make use of with the basic and advanced digitizing toolbars as well as the toolbar for snapping and editing attribute data.

Does anyone know what could be a possible cause and/or how to fix it?

Steps to reproduce the issue

  1. Create shapefile which allows for polygon geometries
  2. Start digitizing the geometries, I have georeferenced raster files that I base my digitized drawings of.
  3. Edit and save a few times while working in the same .shp file layer. Sometimes it happens after a few edits while other times it starts happening almost immediately
  4. See error.

Versions

QGIS-versie 3.22.5-Białowieża QGIS code revisie c2723178 Qt versie 5.15.2 Python versie 3.9.5 GDAL/OGR versie 3.4.1 PROJ versie 8.2.1 EPSG-register databaseversie v10.041 (2021-12-03) GEOS versie 3.10.2-CAPI-1.16.0 SQLite versie 3.37.2 PDAL versie 2.3.0 PostgreSQL client versie 13.0 SpatiaLite versie 5.0.1 QWT versie 6.1.3 QScintilla2 versie 2.11.5 OS versie Windows Server 2016 Version 1809

Actieve Python plug-ins db_manager 0.1.20 grassprovider 2.12.99 MetaSearch 0.3.5 processing 2.12.99 sagaprovider 2.12.99

Supported QGIS version

New profile

Additional context

I work from home via a remote desktop connection, in case that might be of any influence in causing this bug. Prior to working with version 3.22, I did exactly the same tasks with 3.10 and 3.16 and never had any such things happen before. I digitize using a Wacom Cintiq tablet, which never has been a problem before either. But in the current 3.22 version I have minor bugs happening with that too, such as vanishing or incorrectly displaying cursors and such.

Pedro-Murteira commented 2 years ago

Can't reproduce it, even with a new profile. (QGIS 3.22.5 and 3.24.1)

MoltenRainbow commented 2 years ago

Would that imply that the problem is internal to the remote desktop rather than QGIS itself? Because if so, I'm going to have to try to sort it out with the IT department..

Pedro-Murteira commented 2 years ago

Would that imply that the problem is internal to the remote desktop rather than QGIS itself? Because if so, I'm going to have to try to sort it out with the IT department..

I'm not sure myself, but maybe we can assume that is the case. Let's wait to see if there is anyone else that can also test this, and give some feedback on the issue.

github-actions[bot] commented 2 years ago

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.