On 2016-05-04 10:12, Moritz Lennert wrote:
On 03/05/16 22:51, Sebastiaan Couwenberg wrote:
On 03/10/2016 07:42 AM, Sebastiaan Couwenberg wrote:
On 11-12-15 23:19, Sebastiaan Couwenberg wrote:
On 08-12-15 16:05, Sebastiaan Couwenberg wrote:
It seems QGIS doesn't support SAGA 2.2.2 yet:
https://lists.osgeo.org/pipermail/qgis-developer/2015-December/040670.html
QGIS 2.12 and later do support SAGA 2.2, but these changes have not
been
backported to QGIS 2.8 LTR yet. Hopefully they'll be backported for
QGIS
2.8.5.
We have QGIS 2.14 in unstable now, SAGA was updated to 2.2.4 in the
mean
time, but remains unavailable in the processing toolbox.
There are a number of SAGA 2.2.x related commits available in the
2.14
branch which may fix the issue in QGIS 2.14.1 to be released by the
end
of the month.
No SAGA changes in 2.14.2, I'm seriously starting to doubt if we can
support recent SAGA versions in QGIS. It seems the SAGA version in
unstable will always be more current than the supported versions in
QGIS.
I think the question is mainly whether we can aim for compatible
versions in a stable release, or ?
For stable we may be able to support the SAGA version with QGIS in
backports.
It seem that for every SAGA release, the list of support versions in the
QGIS processing plugin needs to be updated. See for example the changes
for SAGA 2.2.3:
https://github.com/qgis/QGIS/commit/607642a562f58652a2939aad64d6476fc50f02de
There is currently no explicit support for SAGA >= 2.2.4. There is an
outstanding issue in the upstream issue tracker about changes required
for SAGA 2.24:
http://hub.qgis.org/issues/14735
With the frequent API breakage in new SAGA releases, and the lack of
manpower in the QGIS project to keep the SAGA processing plugin updated,
I remain sceptical of our ability to support SAGA in QGIS.
https://lists.osgeo.org/pipermail/qgis-developer/2015-December/040797.html
I'd like to hear Johans opinion on SAGA support in QGIS.
Kind Regards,
Bas