Bug report #18985

Tracing issues

Added by Andreas Wicht about 2 years ago. Updated over 1 year ago.

Affected QGIS version:3.4.1 Regression?:No
Operating System:Windows 10 Easy fix?:No
Pull Request or Patch supplied:No Resolution:
Crashes QGIS or corrupts data:No Copied to github as #:26816


First Issue:
Weird snapping when choosing the first vertex to trace. In general I can often observe the behaviour that the tracing starts at one vertex, then traces 2 vertices in the wrong direction and then takes the direct straight line to the initial start, creating a "tracing triangle".

Second Issue:
Tracing does not trace the line until the last selected vertex. The closest it gets is the second to last vertex.

tracing_issue_1.gif - Issue 1 (42 KB) Andreas Wicht, 2018-05-18 12:01 PM

tracing_issue_2.gif - Issue 2 (190 KB) Andreas Wicht, 2018-05-18 12:01 PM

tracing_issue_1_2.gif - Issue 1.2 (85.7 KB) Andreas Wicht, 2018-05-18 12:05 PM

tracing_issue_3.gif (128 KB) Andreas Wicht, 2018-06-27 01:38 PM

tracing_issue_4.gif - Issue 4 (201 KB) Andreas Wicht, 2018-08-07 02:28 PM


#1 Updated by Andreas Wicht about 2 years ago

Issue still persists in 3.2

In my opinion this issue should be changed to high priority as it pretty much makes tracing unusable.

- snapping to vertex with 10px tolerance (active layer)
- topological editing enabled.

#2 Updated by Brian Savage about 2 years ago

I am experiencing the same issues. The problem became more pronounced when I switched the display crs from NAD27 to WGS84. Not sure why that would have been an issue. There were still minor issues with intersections while in NAD27. The shapefiles I am using are in WGS84.

Not sure if this is related or has already been reported, but the auto tracing tool also leaves gaps and overlaps with a difference between the points of around 1e-15 or so.

Using 3.0

#3 Updated by Andreas Wicht almost 2 years ago

Added another gif (tracing_issue_4.gif) showing absolutely unusable tracing behavior.

#4 Updated by Andreas Wicht almost 2 years ago

As Brian mentioned, I also think, that geographic coordinates amplify the problem!

#5 Updated by Bernhard Ströbl over 1 year ago

  • Status changed from Open to Feedback

Have you checked with QGIS 3.4?
If problem persists, can you share data?

#6 Updated by Andreas Wicht over 1 year ago

  • Status changed from Feedback to Open

So the issue here still persists in 3.4 afaik, but not in a reproducible manner.
What helps for sure is to use a metric system (otf projection) while tracing. That greatly reduces the problems.
I am suspecting that maybe rounding issues due to the nature of geographic coordinates might be the issue here, but that is just an educated guess.

It's all in all tricky, because e.g. restarting QGIS also solved the problem in the past when it occured.

As soon as I can reproduce this issue, I will share a subset.

#7 Updated by Giovanni Manghi over 1 year ago

  • Affected QGIS version changed from 3.0.2 to 3.4.1

Also available in: Atom PDF