<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi<div class=""><br class=""><blockquote type="cite" class="">On 23 Nov 2015, at 20:05, ElPaso <<a href="mailto:elpaso@itopen.it" class="">elpaso@itopen.it</a>> wrote:<br class=""><br class="">Il 23/11/2015 18:09, Anita Graser ha scritto:<br class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class="">Hi,<br class=""><br class="">I would like to summarize the statements concerning ftools so far, see statement 1-3 inline.<br class=""><br class="">On Sun, Nov 22, 2015 at 7:23 PM, Matthias Kuhn <<a href="mailto:matthias@opengis.ch" class="">matthias@opengis.ch</a> <mailto:matthias@opengis.ch>> wrote:<br class=""><br class=""> On 11/22/2015 10:45 AM, Radim Blazek wrote:<br class=""> > On Sun, Nov 22, 2015 at 10:07 AM, Nyall Dawson<br class=""> <nyall.dawson@gmail.com <mailto:nyall.dawson@gmail.com>> wrote:<br class=""> >> On 22 November 2015 at 06:19, Anita Graser <anitagraser@gmx.at<br class=""> <mailto:anitagraser@gmx.at>> wrote:<br class=""> >>> On Nov 21, 2015 5:07 PM, "Paolo Cavallini"<br class=""> <cavallini@faunalia.it <mailto:cavallini@faunalia.it>> wrote:<br class=""><br class=""> <br class=""> <br class=""> <br class=""> >>>> I'm still unsure we should replicate existing code: the problems have<br class=""> >>>> been solved over and over in similar code (the closest being<br class=""> saga, also<br class=""> >>>> C++), and redoing things instead of reusing and integrating them does<br class=""> >>>> not sound right to me. I believe the approach we took with<br class=""> GDALTools was<br class=""> >>>> more efficient.<br class=""><br class=""><br class=""> Statement 1: Don't replicate existing code. Build on existing libraries.<br class=""><br class=""> >>>> Il 20/11/2015 18:44, Tim Sutton ha scritto:<br class=""> >>>>> Folks can I ask that we move the thread back to the<br class=""> practical issues of<br class=""> >>>>> plotting a roadmap to solving our FTools issues rather than<br class=""> pursuing<br class=""> >>>>> this avenue which is a dead-end in terms of getting a usable<br class=""> FTools into<br class=""> >>>>> the hands of our users.<br class=""> >>>> I think the best we can do now is do do a minimal fix of<br class=""> broken tools,<br class=""> >>>> spending as little as possible, relying as much as possible<br class=""> on geos7ogr,<br class=""> >>>> waiting for a more solid approach.<br class=""> Agreed, a minimal fix should be shipped soon.<br class=""><br class=""><br class=""> Statement 2: Implement minimal fixes in Python now. Explore other options for the future.<br class=""><br class=""> >> Honestly, I don't think it's a huge amount of work to port<br class=""> these tools<br class=""> >> to c++ implementations. A large amount of the work is already<br class=""> done in<br class=""> >> the geometry classes and there ready for use, and we have some<br class=""> >> existing python code (ftools and processing algs) which we can<br class=""> use as<br class=""> >> a starting point for the port. And the benefit would be that we<br class=""> would<br class=""> >> then have QGIS-optimised implementations ready to go for use by<br class=""> >> core/processing/other plugins. And we'd be able to fix bugs and<br class=""> modify<br class=""> >> these operations as required by QGIS.<br class=""><br class=""> I also think it's worth providing a set of spatial algorithms, by<br class=""> having<br class=""> them in our own code, we can integrate them much better than external<br class=""> tools. No extra conversion into whatever proxy dataformat, better<br class=""> integration with the QGIS architecture and a unified release schedule<br class=""> are good reasons.<br class=""><br class=""><br class=""> Statement 3: QGIS needs it's own core spatial algorithms. Avoid dependencies and unnecessary conversions between data formats.<br class=""><br class="">I think we also need to make a decision. Therefore, I'd like to suggest to make a motion on Statement 2 and set everything in motion to get minimal bug fixes ready for the next release.<br class=""><br class="">Procedure-wise, I'm wondering who should vote on the motion: core devs? PSC?<br class=""><br class="">Best wishes,<br class="">Anita<br class=""><br class=""><br class=""></blockquote><br class=""><br class="">Hi Anita,<br class=""><br class="">thanks for the summary.<br class=""><br class="">I just wonder if discussing on qgis-developer wouldn't be useful.<br class=""><br class="">I'm not sure about ho many developers follow this list, maybe other devs have something interesting to say.<br class=""></blockquote><div class=""><br class=""></div><div class="">I think its fine for doing it but lets:</div><div class=""><br class=""></div><div class="">1) Go to the list with a concrete proposal rather than an open ended discussion</div><div class="">2) Time cap the conversation so we can move over to action ASAP</div><div class=""><br class=""></div><div class="">@Anita thanks for summarising. From my side, I agree with the three points you made.</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim</div><br class=""><blockquote type="cite" class=""><br class="">-- <br class="">Alessandro Pasotti<br class="">w3: <a href="http://www.itopen.it" class="">www.itopen.it</a><br class=""><br class="">_______________________________________________<br class="">Qgis-psc mailing list<br class="">Qgis-psc@lists.osgeo.org<br class="">http://lists.osgeo.org/mailman/listinfo/qgis-psc<br class=""></blockquote><br class=""><div class=""><span><img height="60" width="60" apple-inline="yes" id="A4141186-FD45-4ABB-B900-84C97739DA76" apple-width="yes" apple-height="yes" src="cid:DDEF9B12-67C3-4498-BD7D-EC3563CC35A4" class=""></span><br class=""><br class=""><br class="">Tim Sutton<br class="">QGIS Project Steering Committee Member<br class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a><br class=""><br class=""><br class=""><br class=""></div><br class=""></div></body></html>