Bug report #15812

Trace digitizing behaves unexpectedly when editing layer is in UTM but the project file is WGS84 OTF.

Added by sand thorn almost 4 years ago. Updated over 1 year ago.

Affected QGIS version:2.18.0 Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:end of life
Crashes QGIS or corrupts data:No Copied to github as #:23732


Version: 2.16 x64, 2.18 x64, 2.19-dev x64
Platform: Windows 10 x64

I'm not sure whether there are any limitations of "Auto Trace" feature.

If I'm trying to auto trace on UTM layers while the project file is set to WGS84,
the feature works in the unexpectedly way and ruins the digitization.

If the project file is set back to the same UTM,
the feature work as expected.

This is reproduced since 2.16.

auto_trace_error.zip - This archive contain sample project. (89.6 KB) sand thorn, 2016-11-04 03:23 AM

auto_trace_error.png - Screen capture of error auto trace. (87.2 KB) sand thorn, 2016-11-04 03:23 AM


#1 Updated by Saber Razmjooei almost 4 years ago

  • Category set to Digitising
  • Subject changed from "Auto Trace" feature behaves unexpectedly when editing layer is in UTM but the project file is WGS84 OTF. to Trace digitizing behaves unexpectedly when editing layer is in UTM but the project file is WGS84 OTF.


#2 Updated by Giovanni Manghi over 3 years ago

  • Easy fix? set to No
  • Regression? set to No

#3 Updated by Giovanni Manghi over 1 year ago

  • Resolution set to end of life
  • Status changed from Open to Closed

End of life notice: QGIS 2.18 LTR


QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.

Also available in: Atom PDF