https://issues.qgis.org/https://issues.qgis.org/favicon.ico2017-05-08T09:57:10ZQGIS Issue TrackingQGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=795322017-05-08T09:57:10ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li><li><strong>Subject</strong> changed from <i>Geoprocessing Tools->Difference Failing with 2.18.7 and memory layer</i> to <i>Vector difference Failing in 2.18.7 with memory layers (created with the "memory layers" plugin)</i></li><li><strong>Category</strong> changed from <i>Vectors</i> to <i>Processing/QGIS</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Operating System</strong> deleted (<del><i>Windows 7</i></del>)</li></ul><p>In 2.18.7 you don't need such plugin, you have the (core) "new temporary scratch layer" functionality, and with that there are no issues.</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=795972017-05-11T16:00:16ZCalvin Hamilton
<ul></ul><p>It doesn't matter how the memory layer is created it still fails and should be fixed. The memory layers plugin was just an example. Are memory layers going away in 3.0?</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=796032017-05-11T18:23:40ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><p>Calvin Hamilton wrote:</p>
<blockquote>
<p>It doesn't matter how the memory layer is created it still fails and should be fixed. The memory layers plugin was just an example. Are memory layers going away in 3.0?</p>
</blockquote>
<p>the "New Memory Layer" plugin functionality has been replaced by the core "new temporary scratch layer". So if the problem is only about layers created with the plugin then I shouls say we should mark it as obsolete.</p>
<p>If there are other ways to create "memory/scratch" layers that turns to not play well with processing then is another matter. Is this the case? cheers!</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=797792017-05-16T19:21:25ZCalvin Hamilton
<ul></ul><p>Somehow I don't get notified when this is updated. The New Memory Layer plugin was just one example. My own Shape Tools plugin is another example. This is a problem no matter how the memory layer is created. Any layer created by calling</p>
<p>QgsVectorLayer("Polygon?crs=epsg:4326", "Layer Name", "memory")</p>
<p>will fail.</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=797802017-05-16T19:30:41ZCalvin Hamilton
<ul></ul><p>Not to be picky but "(created with the "memory layers" plugin)" really should not be in the title. I first found this problem not using the "memory layers" plugin and then to test to see if it failed using another way I tried the "memory layers" plugin. That was apparently a mistake because the focus has been on that plugin and not on the fact that it fails with any memory layer.</p>
<p>This problem is not about the "memory layers" plugin.</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=797812017-05-16T19:48:43ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li><li><strong>Description</strong> updated (<a href="/journals/diff/79781?detail_id=68524" title="View differences">diff</a>)</li><li><strong>Subject</strong> changed from <i>Vector difference Failing in 2.18.7 with memory layers (created with the "memory layers" plugin)</i> to <i>Processing/geoprocessing operations failing in 2.18 with memory layers</i></li></ul><blockquote>
<p>This problem is not about the "memory layers" plugin.</p>
</blockquote>
<p>ok, now we have w new piece of information that makes the issue clear.</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=831472017-09-26T10:57:26ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Affected QGIS version</strong> changed from <i>2.18.7</i> to <i>2.18.13</i></li></ul> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=836862017-10-19T08:05:34ZVictor Olayavolayaf@gmail.com
<ul></ul><p>Cannot reproduce here</p>
<p>I tried you suggestion of creating two polygons in two memory layers, and difference work fine. Also, i tried creating 2 buffers of different size from a point memory layer, and then computing the difference between them, and it also works fine.</p>
<p>Tried in latest version of Processing, and also in the one corresponding to 2.8.7. Both worked fine.</p>
<p>Any more detail you can provide so we can reproduce?</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=838382017-10-24T07:54:48ZAlexander Bruy
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>I have tested almost all geoprocessing tools and their combinations and also was not able to reproduce this bug.</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=838422017-10-24T12:23:24ZCalvin Hamilton
<ul></ul><p>I have found that it is caused by 3rd party plugins that create memory layers. Something must have changed recently in QGIS with how polygons are created and the 3rd party plugin shapes do not work. Two examples are the old "New Memory Layer" plugin and the "Shape Tools" plugin which I wrote. The geoprocessing operations used to work so the question is what has changed? Do these plugins need to make some change or do the geoprocessing algorithms need to be more robust? I would think that if you have a polygon the algorithms should be able to work with them or at least be able to report that there is a problem.</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=864402018-02-01T17:37:20ZAlexander Bruy
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-6 priority-4 priority- closed" href="/issues/18006">Bug report #18006</a>: Geoprocessing Tools Fail with Memory Layers in QGIS 2.18</i> added</li></ul> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=865132018-02-02T18:47:37ZCalvin Hamilton
<ul><li><strong>File</strong> <a href="/attachments/download/12109/example1.jpg">example1.jpg</a> added</li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li><li><strong>File</strong> <a href="/attachments/download/12110/example2.jpg">example2.jpg</a> added</li><li><strong>File</strong> <a href="/attachments/download/12112/qgis2.18example.jpg">qgis2.18example.jpg</a> added</li><li><strong>File</strong> <a href="/attachments/download/12111/two-polygons.py">two-polygons.py</a><a href="/attachments/12111/two-polygons.py"><img alt="Magnifier" src="/images/magnifier.png" /></a> added</li></ul><p>Since my new ticket <a class="issue tracker-1 status-6 priority-4 priority- closed" href="https://issues.qgis.org/issues/18006" title="Geoprocessing Tools Fail with Memory Layers in QGIS 2.18 (Rejected)">#18006</a> related to this was rejected. Here is the additional information that I wrote in that ticket to diagnose this issue.</p>
<p>I have attached a python script to illustrate this bug. I posted this problem on the qgis-developer group and Richard Duivenvoorde confirmed the problem. This problem appears to only affect QGIS 2.18.x. Richard tested it on QGIS 3.0 and it works fine. example1.jpg and exmple2.jpg were run using 2.14 to show the correct results.</p>
<p>Run two-polygons.py and it will create two polygons (see example1.jpg). Note that I have given Polygon 2 some transparency so you can see how they overlap. Now run "Vector->Geoprocessing Tools->Clip". I used 'Polygon 1' for the 'Input vector layer' and 'Polygon 2' for the 'Clip layer'. QGIS 2.14 produces the correct results as shown by example2.jpg. QGIS 2.18.16 does not clip. It returns 'Polygon 1' as shown by qgis2.18example.jpg.</p>
<p>This example just shows the Clip function but I think all of the Geoprocessing Tools have issues. 'Intersection' gives the same results. 'Symmetrical difference' and 'Difference' don't return any polygon result, but they should both return a result. I have not checked the rest.</p> QGIS Application - Bug report #16524: Processing/geoprocessing operations failing in 2.18 with memory layershttps://issues.qgis.org/issues/16524?journal_id=901232018-06-05T02:13:57ZNyall Dawson
<ul><li><strong>Resolution</strong> set to <i>fixed/implemented</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>Fixed in 3.0</p>