You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running topology check 'must not have dangles', it shows red dots for every single end of line point regardless of whether it's snapped to the middle of a segment or vertex. this is regardless of whether its snapping to the same layer or a different one
Steps to reproduce the issue
go to topology
click spanner
select layer and must not have dangles
run
see error
Versions
QGIS version
3.28.4-Firenze
QGIS code revision fd0fb72
Qt version
5.15.3
Python version
3.9.5
GDAL/OGR version
3.6.2
PROJ version
9.1.1
EPSG Registry database version
v10.076 (2022-08-31)
GEOS version
3.11.1-CAPI-1.17.1
SQLite version
3.39.4
PDAL version
2.4.3
PostgreSQL client version
unknown
SpatiaLite version
5.0.1
QWT version
6.1.6
QScintilla2 version
2.13.1
OS version
Windows 10 Version 2009
What is the bug or the crash? - Topology Error
When running topology check 'must not have dangles', it shows red dots for every single end of line point regardless of whether it's snapped to the middle of a segment or vertex. this is regardless of whether its snapping to the same layer or a different one
Steps to reproduce the issue
go to topology
click spanner
select layer and must not have dangles
run
see error
Versions
QGIS version
3.28.4-Firenze
QGIS code revision
fd0fb72
Qt version
5.15.3
Python version
3.9.5
GDAL/OGR version
3.6.2
PROJ version
9.1.1
EPSG Registry database version
v10.076 (2022-08-31)
GEOS version
3.11.1-CAPI-1.17.1
SQLite version
3.39.4
PDAL version
2.4.3
PostgreSQL client version
unknown
SpatiaLite version
5.0.1
QWT version
6.1.6
QScintilla2 version
2.13.1
OS version
Windows 10 Version 2009
Active Python plugins
AnotherDXF2Shape
1.2.5
Comsof-Designer
22.3
Mergin
2023.1
QPackage
1.5
quick_map_services
0.19.33
StreetView
3.2
db_manager
0.1.20
processing
2.12.99
Supported QGIS version
New profile
Additional context
every member of my team experiences the same issue
The text was updated successfully, but these errors were encountered: