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

double line style and acute angle or short line length #55050

Closed
2 tasks done
T3xtM4rk3r opened this issue Oct 25, 2023 · 3 comments
Closed
2 tasks done

double line style and acute angle or short line length #55050

T3xtM4rk3r opened this issue Oct 25, 2023 · 3 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.

Comments

@T3xtM4rk3r
Copy link

What is the bug or the crash?

Hi There,

when using a double line symbology qgis ignores or fails to display the lines wenn acute angle oder short line lengths are present.

Steps to reproduce the issue

linestyle_issue.zip

  1. Load layer pasted from linestyle_issue geopackage. Two closed line loops should be visible.
    grafik

  2. Go to layer symbology, add second line with offset 0,26 and stroke width 0,26

grafik

  1. For one part in each line the doubled line gets ignored
    faulty_style

  2. For both lines the black line appears when zooming in a lot. I assume that for the right loop the short segment at the nordwest part of the single styled part is responsible for the 'faulty' display of the line style. For the left loop maybe the angle at the bottom is too small?
    problematic_parts

Versions

<style type="text/css"> p, li { white-space: pre-wrap; } </style>
QGIS-Version 3.32.3-Lima QGIS-Codeversion 67d4610
Qt-Version 5.15.3
Python-Version 3.9.5
GDAL-Version 3.7.2
PROJ-Version 9.3.0
EPSG-Registraturdatenbankversion v10.094 (2023-08-08)
GEOS-Version 3.12.0-CAPI-1.18.0
SQLite-Version 3.41.1
PDAL-Version 2.5.5
PostgreSQL-Client-Version 15.2
SpatiaLite-Version 5.1.0
QWT-Version 6.1.6
QScintilla2-Version 2.13.4
BS-Version Windows 10 Version 2009
       
Aktive Python-Erweiterungen
db_manager 0.1.20
grassprovider 2.12.99
MetaSearch 0.3.6
processing 2.12.99
QGIS-Version 3.32.3-Lima QGIS-Codeversion [67d4610](https://github.com/qgis/QGIS/commit/67d46100b5) Qt-Version 5.15.3 Python-Version 3.9.5 GDAL-Version 3.7.2 PROJ-Version 9.3.0 EPSG-Registraturdatenbankversion v10.094 (2023-08-08) GEOS-Version 3.12.0-CAPI-1.18.0 SQLite-Version 3.41.1 PDAL-Version 2.5.5 PostgreSQL-Client-Version 15.2 SpatiaLite-Version 5.1.0 QWT-Version 6.1.6 QScintilla2-Version 2.13.4 BS-Version Windows 10 Version 2009

Aktive Python-Erweiterungen
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

@T3xtM4rk3r T3xtM4rk3r added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Oct 25, 2023
@agiudiceandrea
Copy link
Contributor

agiudiceandrea commented Oct 25, 2023

@T3xtM4rk3r, thanks for reporting. It seems to me the issue you are experiencing may be the same previously reported at #51583. Could you please have a look at it?

Copy link

github-actions bot commented Nov 9, 2023

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Nov 9, 2023
Copy link

github-actions bot commented Dec 7, 2023

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2023
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! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.
Projects
None yet
Development

No branches or pull requests

2 participants