[Qgis-developer] (Yet again) SAGA support badly broken in QGIS

[Victor Olaya]

I am familiar with SAGA source code, and algorithms are independent
and self contained, very modular structure, so it should be easy to
use them. There is a lot of work in there, since the number of
algorithms is very large, but it can be a progressive thing. Having
the in the QGIS source code would be fantastic.

If we decide to go in this direction, we can maybe get rid of the SAGA
provider in core, and have it as a separate plugin (and maybe a ship
SAGA itself with the plugin??), for those wanting to run SAGA itself.
In core we would add native Processing algorithms that would use the
QGIS native functionality that we clone from SAGA. There is no need to
port everything, at first just the most common ones or those that have
no equivalent in other providers. Better a reduced set of robust and
commonly used algs than a large colelction of them that is not so
stable as it should.

Not sure how we can tackle this, but definitely it is an option to
consider. It would solve all issues with format conversions, etc... so
it's clearly worth a try.

My 2 cents

Cheerss


2016-06-01 11:11 GMT+02:00 Paolo Cavallini <cavallini at faunalia.it>:
> Il 01/06/2016 10:51, Tom Chadwin ha scritto:
>
>> Would it be fair to say that non-Windows users are more likely to be able to
>> handle other ways around this issue?
>
> not in an easy and clean way.
> Better a general solution than a hack.
> All the best.
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer