-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Parallel multi-core rendering glitches with OTF reprojection #19717
Comments
Author Name: Giovanni Manghi (@gioman) cannot confirm here, tested on master on both Linux and Windows (same project and data).
|
Author Name: Gary Sherman (@g-sherman) Try turning off simplification and/or "Make lines appear less jagged..." and see if it goes away. We had a similar problem years ago and I don't recall the root cause. |
Author Name: Saber Razmjooei (@saberraz) There are layers from outside the OTF CRS. According to this website: http://prj2epsg.org/epsg/5070 Canada and Mexico are outside EPSG:5070's CRS zone. I guess this causes the problem. I have removed Mexico and Canada and the problem seems to have disappeared. |
Author Name: Anita Graser (@anitagraser) @gary: Changing the simplification settings (values, on/off) or deactivating anti-aliasing didn't change the results. @saber: Even if I only use the US states (which should be within the CRS zone), these artifacts appear. |
Author Name: Saber Razmjooei (@saberraz) It has become less frequent. To completely get rid of the problem, I saved western_states in 5070 and used that instead. But that does not explain the source of problem. |
Author Name: Martin Dobias (@wonder-sk) I cannot replicate the problem. @anita / @saber - which version of Proj.4 do you use? Does it happen also if you use a wgs84 for destination CRS? To my (brief) knowledge, the used epsg 5070 uses a grid file. Could you try some other projection for north america that does not involve reading of grid files? (based on parameters only) Apparently the proj library versions < 4.8 were prone to errors when used in multi-threaded environment, but maybe we should also make use of contexts introduced in 4.8: |
Author Name: Giovanni Manghi (@gioman) Martin Dobias wrote:
it seems anyway strange to me as I tested also on Windows (where anyone should have the same libraries) and cannot replicate the issue. |
Author Name: Martin Dobias (@wonder-sk) Giovanni Manghi wrote:
Unfortunately this is not that strange. It is quite common that errors in multi-threaded code appear just for some people, while working flawlessly for others. |
Author Name: Saber Razmjooei (@saberraz) It works fine in both WGS84 and 4269. |
Author Name: Giovanni Manghi (@gioman) still true? |
Author Name: Anita Graser (@anitagraser) Still true for me (Win8 OSGeo4W nightly 64bit). |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Anita Graser (@anitagraser) Still true for 2.8.1 (Win8 OSGeo4W 64bit). |
Author Name: Anita Graser (@anitagraser) Still true for 2.11 today.
|
Author Name: Martin Dobias (@wonder-sk) As far as I can tell from my tests, this problem was caused by a bug in proj.4 library: OSGeo/PROJ#226 It has been fixed in proj 4.9.2 (released Sep 2015) which is now also available in osgeo4w (since end of Nov 2015). Could you please test again with the latest proj4 version to see if the problem is gone?
|
Author Name: Anita Graser (@anitagraser) Unfortunately still around ... even with the new proj .. !projissues.PNG! Please put back to "open".
|
Author Name: Anita Graser (@anitagraser) @martin Can you please change the status back to open? Thanks! |
Author Name: Martin Dobias (@wonder-sk) Maybe we can have a look at it in Girona...
|
Author Name: Giovanni Manghi (@gioman) is there any update on this issue?
|
Author Name: Anita Graser (@anitagraser) Still same error unfortunately. Tested with latest 2.19 in OSGeo4W - so not latest master !glitch219.PNG!
|
Author Name: Jürgen Fischer (@jef-n) Anita Graser wrote:
not even master - qgis-dev is from (removed) master_2. qgis-rel-dev should be more up to date (branched off from master_2 on release of 2.18) |
Author Name: Giovanni Manghi (@gioman) Jürgen Fischer wrote:
There will ever be a master/qgis3 package on osgeo4w? Just a practical question: I do/did most of master testing on Windows because it was very practical, if there will be no more master on osgeo4w I will have to review my strategy and compile daily on Linux.
|
Author Name: Jürgen Fischer (@jef-n) Giovanni Manghi wrote:
sure. |
Author Name: Anita Graser (@anitagraser) Jürgen Fischer wrote:
Ok, I'll try with qgis-rel-dev |
Author Name: Anita Graser (@anitagraser) Same issue in qgis-rel-dev |
Author Name: Giovanni Manghi (@gioman) Anita Graser wrote:
what about the (qgis3) master? any change?
|
Author Name: Anita Graser (@anitagraser) Still same here with 2.99 from OSGeo4W. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Nyall Dawson (@nyalldawson) Anita - please test the next nightly 3.0 release as this is likely fixed now.
Deactivating either OTF or parallel rendering fixes the problem as far as I can tell. !glitch.png! to With active on-the-fly reprojection and parallel rendering, the map renders with big artifacts. I've tested the following project with both the 2.4 release and today's nightly: Deactivating either OTF or parallel rendering fixes the problem as far as I can tell. !glitch.png! |
Author Name: Nyall Dawson (@nyalldawson) Anita -can we close this? Should be fixed in master and recent 2.18 |
Author Name: Anita Graser (@anitagraser) Looks good! Thanks Nyall!
|
Author Name: Anita Graser (@anitagraser)
Original Redmine Issue: 11441
Affected QGIS version: master
Redmine category:map_canvas
With active on-the-fly reprojection and parallel rendering, the map renders with big artifacts. I've tested the following project with both the 2.4 release and today's nightly:
https://github.com/FOSS4GAcademy/GST101FOSS4GLabs/tree/master/Module%204%20Lab/QGIS%202.2/Lab%204%20Data
Deactivating either OTF or parallel rendering fixes the problem as far as I can tell.
!glitch.png!
Related issue(s): #19979 (relates)
Redmine related issue(s): 11746
The text was updated successfully, but these errors were encountered: