<p dir="ltr">Hi</p>
<p dir="ltr">@werner can you please replace. Y little summary table, removing irrelevant items and adding relevant items? <br></p>
<p dir="ltr">I was hoping someone could clearly lay out what is broken, and in which versions. </p>
<p dir="ltr">Thanks! </p>
<p dir="ltr">Regards </p>
<p dir="ltr">Tim </p>
<div class="gmail_quote">On Nov 20, 2015 12:34 AM, "Werner Macho" <<a href="mailto:werner.macho@gmail.com">werner.macho@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hi!<br>
<br>
I tested 2.8.* 2.10 2.12 and master .. And with the attached testcase<br>
the correct result was only visible to the user with 2.8.* ..<br>
Hope the testproject will get through the list ..<br>
<br>
Tested the intersect tool in QGIS(ftools) and processing. Same result.<br>
And I am pretty sure that this happens elsewhere too.<br>
So as Luigi said - the users are currently getting wrong results (or<br>
lets summarize it as "half the truth" :) ) presented.<br>
Since 2.8.3 at least the intersect tool is affected and QGIS should<br>
communicate that .. IMHO I would prefer a crash than getting results I<br>
cannot rely on.<br>
<br>
Hope my testfiles are useful.<br>
<br>
regards<br>
Werner<br>
<br>
On 19/11/15 23:13, Luigi Pirelli wrote:<br>
> Hi Nyall<br>
><br>
> as reported by Giovanni in the first thread mail and confirmed by<br>
> Werner during Hackmeeting... I don't know if they tested in master<br>
> (I suppose they did)<br>
><br>
> Giovanni and Werner have a test data set to stress FTools in the<br>
> new geometry engine context. I don't know if they added this test<br>
> data set in a issue. Thre focus of the thread, imho is 1) what to<br>
> do with the current distributed ftool (How awaring users of<br>
> problem) 2) plan a solution to fix it<br>
><br>
> cheers Luigi Pirelli<br>
><br>
> **********************************************************************<br>
****************************<br>
><br>
><br>
* Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com<br>
> * LinkedIn: <a href="https://www.linkedin.com/in/luigipirelli" rel="noreferrer" target="_blank">https://www.linkedin.com/in/luigipirelli</a> *<br>
> Stackexchange:<br>
> <a href="http://gis.stackexchange.com/users/19667/luigi-pirelli" rel="noreferrer" target="_blank">http://gis.stackexchange.com/users/19667/luigi-pirelli</a> * GitHub:<br>
> <a href="https://github.com/luipir" rel="noreferrer" target="_blank">https://github.com/luipir</a> * Mastering QGIS:<br>
> <a href="https://www.packtpub.com/application-development/mastering-qgis" rel="noreferrer" target="_blank">https://www.packtpub.com/application-development/mastering-qgis</a><br>
> **********************************************************************<br>
****************************<br>
><br>
><br>
><br>
> On 19 November 2015 at 23:04, Nyall Dawson <<a href="mailto:nyall.dawson@gmail.com">nyall.dawson@gmail.com</a>><br>
> wrote:<br>
>> On 20 November 2015 at 07:49, Tim Sutton <<a href="mailto:tim@kartoza.com">tim@kartoza.com</a>><br>
>> wrote:<br>
>><br>
>>>> ftools OK reshape/split tools ok<br>
>>> QGIS 2.8.3 Y* N QGIS<br>
>>> 2.10 N N QGIS 2.12<br>
>>> N N<br>
>><br>
>> I wasn't aware of this... can you summarise (or post a link to)<br>
>> the issues in the reshape/split tools? There was a lot of issues<br>
>> with this fixed in 2.12, and I'm not aware of any outstanding<br>
>> (reported) ones.<br>
>><br>
>>><br>
>>> 1) make small band-aid fixes to fix immediate issues 2) try to<br>
>>> sponsor e.g. Nyall or Jürgen to completely rewrite in C++ and<br>
>>> have python bindings added so that they can be used from<br>
>>> processing 3) try to sponsor e.g. Victor to implement as<br>
>>> processing algs and then just wrap them as actions in the<br>
>>> vector menu<br>
>>><br>
>><br>
>> I'd also like to point out that reimplementing these in c++<br>
>> would allow them to be reused by other (non-processing) plugins<br>
>> too. There's also likely a considerable speed boost possible from<br>
>> this approach.<br>
>><br>
>> Nyall _______________________________________________ Qgis-psc<br>
>> mailing list <a href="mailto:Qgis-psc@lists.osgeo.org">Qgis-psc@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2<br>
<br>
iEYEARECAAYFAlZOTnYACgkQDAH1YiCxBgndjwCfUF0SuJBerteMc1hwByN2SZSQ<br>
NEEAni7DCNrUzkgiNMeMcCnoBUEazQh0<br>
=jgEV<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div>