Incorrect winding/orientation/order of polygon's vertices in Memory layers #58333
Closed
2 tasks done
Labels
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Data Provider
Related to specific vector, raster or mesh data providers
Digitizing
Related to feature digitizing map tools or functionality
Regression
Something which used to work, but doesn't anymore
What is the bug or the crash?
Using QGIS 3.38.1 on Windows 10 (OSGeo4W), when digitizing a polygon geometry with a hole in a Memory layer, the resulting order of the vertices in the WKT representation of the polygon is different in some circumstances and the outputs of the
exteriorRing()
,interiorRing()
,orientation()
,forcePolygonClockwise()
,forcePolygonCounterClockwise()
functions are weird and not consistent.The issue doesn't occur using QGIS 3.34.9 on the same system.
Steps to reproduce the issue
Using QGIS 3.38.1:
0 0, 0 3, 3 3, 3 0
1 1, 1 2, 2 2, 2 1
The following Python code executed in the Python console, shows the issues:
The same incorrect behaviour occurs using the corresponding functions (
geom_to_wkt
,force_polygon_cw
,force_polygon_ccw
) in the field calculator.The issue doesn't occur using QGIS 3.34.9 on the same system, following the same steps:
Versions
QGIS version
3.38.1-Grenoble
QGIS code revision
3d4177a
Qt version
5.15.13
Python version
3.12.4
GDAL/OGR version
3.9.1
PROJ version
9.4.0
EPSG Registry database version
v11.004 (2024-02-24)
GEOS version
3.12.2-CAPI-1.18.2
SQLite version
3.45.1
PDAL version
2.6.3
PostgreSQL client version
16.2
SpatiaLite version
5.1.0
QWT version
6.2.0
QScintilla2 version
2.14.1
OS version
Windows 10 Version 1903
Active Python plugins
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
Supported QGIS version
New profile
Additional context
The issue occurs on Windows since QGIS 3.36.0.
May be related to #55306.
The text was updated successfully, but these errors were encountered: