Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snapping on segment does not create topological points to all layers #56689

Closed
2 tasks done
vaahtokarkki opened this issue Mar 4, 2024 · 1 comment · Fixed by #57723
Closed
2 tasks done

Snapping on segment does not create topological points to all layers #56689

vaahtokarkki opened this issue Mar 4, 2024 · 1 comment · Fixed by #57723
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Digitizing Related to feature digitizing map tools or functionality

Comments

@vaahtokarkki
Copy link
Contributor

vaahtokarkki commented Mar 4, 2024

What is the bug or the crash?

When snapping is enabled for all layers, digitizing a new feature with vertex tool does not create topological points for all layers, if the snapped segment is shared by multiple layers:
qgis

Steps to reproduce the issue

  • Open snapping.zip project (open from - geopackage)
  • Enable editing for all three layers
  • Make sure topological editing is enabled
  • Make sure snapping on segment and all layers is enabled
  • Digitize new feature for line layer
    • Snap to the shared boundary of both polygons
  • Topological point is created only for feature in polygon 1 layer

Versions

<style type="text/css"> p, li { white-space: pre-wrap; } </style>
QGIS version 3.36.0-Maidenhead QGIS code revision 09951dc
Qt version 5.15.3
Python version 3.9.18
GDAL/OGR version 3.8.4
PROJ version 9.3.1
EPSG Registry database version v10.098 (2023-11-24)
GEOS version 3.12.1-CAPI-1.18.1
SQLite version 3.41.1
PDAL version 2.6.0
PostgreSQL client version 16.1
SpatiaLite version 5.1.0
QWT version 6.1.6
QScintilla2 version 2.13.4
OS version Windows 10 Version 2009
       
Active Python plugins
db_manager 0.1.20
grassprovider 2.12.99
MetaSearch 0.3.6
processing 2.12.99
QGIS version 3.36.0-Maidenhead QGIS code revision [09951dc](https://github.com/qgis/QGIS/commit/09951dc0) Qt version 5.15.3 Python version 3.9.18 GDAL/OGR version 3.8.4 PROJ version 9.3.1 EPSG Registry database version v10.098 (2023-11-24) GEOS version 3.12.1-CAPI-1.18.1 SQLite version 3.41.1 PDAL version 2.6.0 PostgreSQL client version 16.1 SpatiaLite version 5.1.0 QWT version 6.1.6 QScintilla2 version 2.13.4 OS version Windows 10 Version 2009

Active Python plugins
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99

<style type="text/css"> p, li { white-space: pre-wrap; } </style>
QGIS version 3.34.1-Prizren QGIS code revision 1339274
Qt version 5.15.3
Python version 3.9.5
GDAL/OGR version 3.8.0
PROJ version 9.3.0
EPSG Registry database version v10.094 (2023-08-08)
GEOS version 3.12.1-CAPI-1.18.1
SQLite version 3.41.1
PDAL version 2.6.0
PostgreSQL client version 15.2
SpatiaLite version 5.1.0
QWT version 6.1.6
QScintilla2 version 2.13.4
OS version Windows 10 Version 2009
       
Active Python plugins
db_manager 0.1.20
grassprovider 2.12.99
MetaSearch 0.3.6
processing 2.12.99
QGIS version 3.34.1-Prizren QGIS code revision [1339274](https://github.com/qgis/QGIS/commit/133927424d) Qt version 5.15.3 Python version 3.9.5 GDAL/OGR version 3.8.0 PROJ version 9.3.0 EPSG Registry database version v10.094 (2023-08-08) GEOS version 3.12.1-CAPI-1.18.1 SQLite version 3.41.1 PDAL version 2.6.0 PostgreSQL client version 15.2 SpatiaLite version 5.1.0 QWT version 6.1.6 QScintilla2 version 2.13.4 OS version Windows 10 Version 2009

Active Python plugins
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

Additional context

No response

@vaahtokarkki vaahtokarkki added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Mar 4, 2024
@agiudiceandrea agiudiceandrea added the Digitizing Related to feature digitizing map tools or functionality label Mar 5, 2024
JuhoErvasti added a commit to GispoCoding/QGIS that referenced this issue Jun 10, 2024
@JuhoErvasti
Copy link
Contributor

I noticed another related issue; if you're trying to edit only one of the layers and it has overlapping segments with the other layer the topological point is added to neither one of them since it is only added to the snapped layer (see #37824).

topobug

The order in which layers are snapped to seems to be dependent on the order in the layer panel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Digitizing Related to feature digitizing map tools or functionality
Projects
None yet
3 participants