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.38k stars 2.98k forks source link

Duplicate vertex when digitizing line with filegdb #39680

Closed esnyder-rve closed 2 years ago

esnyder-rve commented 3 years ago

Describe the bug When digitizing lines, a duplicate vertex is added for each segment's starting vertex. I can only produce this with ESRI's File GeoDatabase (.gdb).

How to Reproduce

  1. Have point layer
  2. Have line layer
  3. Vertex snapping enabled
  4. Digitize line between points
  5. Notice duplicate vertices at each line segment's beginning.

2020-10-28

Screencast Walkthrough

  1. Showing that there is only one inlet at each location, there are no overlapped inlets.
  2. Showing the problem with a single line segment. The first vertex gets duplicated.
  3. Looking at the vertex editor to show the duplicate vertex and deleting it.
  4. Showing the problem with multiple segments. The first vertex for each segment gets duplicated.
  5. Looking at the vertex editor to show the duplicate vertices and deleting them.

QGIS and OS versions

QGIS version 3.16.0-Hannover QGIS code revision 43b64b13f3 Compiled against Qt 5.11.2 Running against Qt 5.11.2 Compiled against GDAL/OGR 3.1.4 Running against GDAL/OGR 3.1.4 Compiled against GEOS 3.8.1-CAPI-1.13.3 Running against GEOS 3.8.1-CAPI-1.13.3 Compiled against SQLite 3.29.0 Running against SQLite 3.29.0 PostgreSQL Client Version 11.5 SpatiaLite Version 4.3.0 QWT Version 6.1.3 QScintilla2 Version 2.10.8 Compiled against PROJ 6.3.2 Running against PROJ Rel. 6.3.2, May 1st, 2020 OS Version Windows 10 (10.0) Active python plugins annotationManager; BezierEditing; cartography_tools; firstaid; FreehandRasterGeoreferencer; Go2NextFeature3; joinmultiplelines; latlontools; loadthemall; MemoryLayerSaver; mmqgis; monokai; MultipleLayerSelection; powerpan; processing_r; processing_saga; processing_taudem; processing_wbt; qlyrx; QuickMultiAttributeEdit3; redLayer; searchlayers; SelectWithin; slyr_community; Submission; db_manager; processing

Additional context Tried to reproduce with clean profile and scratch layers, cannot reproduce.

gioman commented 3 years ago

Tried to reproduce with clean profile and scratch layers, cannot reproduce.

@esnyder-rve does it happens with a new profile and fgdb datasource?

esnyder-rve commented 3 years ago

Yes. I also noticed later that of the two duplicate verts, the first had an M value.

gioman commented 3 years ago

Does it happen with any fgdb, or just specific ones? if is the latter please attach a sample.

esnyder-rve commented 3 years ago

I've tried it with a couple of fgdb, and the same thing occurs.

gioman commented 3 years ago

I've tried it with a couple of fgdb, and the same thing occurs.

@esnyder-rve can you attach one of them?

esnyder-rve commented 3 years ago

Stormwater.gdb.zip The area given in the sample is shown in the gif above.

gioman commented 3 years ago

The area given in the sample is shown in the gif above.

@gioman I cannot replicate here on QGIS 3.16 on Windows.

esnyder-rve commented 3 years ago

I guess I just have the fun ones like #37415 (also mine, but this was from my personal account).

gioman commented 3 years ago

@esnyder-rve likely a plugin issue as in https://github.com/qgis/QGIS/issues/39991#issuecomment-725986427

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.

github-actions[bot] commented 2 years ago

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue. Or, if you have any further questions, there are also further support channels that can help you.