8 Commits

Author	SHA1	Message	Date
volaya	519d3dc3b7	[processing] more robust CRS assignation for SAGA outputs	2015-07-10 12:42:22 +02:00
volaya	feb8d386a5	[processing] fixed saga algorithms when input is an sdat file	2015-06-24 18:04:41 +02:00
volaya	32d6275fa3	[processing]changed native raster format for SAGA algorithms from tif to sdat ... This eliminates the need to export to a QGIS compatible format after generating a raster output. The SDAT format is the native SAGA format, and it is supported by GDAL, so it is also supported by QGIS. This was not used before, but now we use that to reduce the nuber of steps and provide a better integration. Conversion to other formats is now done by Processing itself, not by the SAGA algorithm. fixes #10735	2015-06-22 09:11:01 +02:00
Juergen E. Fischer	956c155e8f	fix python pep8 warnings and fix some revealed errors ... pep8 --ignore=E111,E128,E201,E202,E203,E211,E221,E222,E225,E226,E227,E231,E241,E261,E265,E272,E302,E303,E501,E701 \ --exclude="ui_*.py,debian/*,python/ext-libs/*" \ .	2015-02-01 20:46:47 +01:00
volaya	e9228b67c9	[processing] some SAGA fixes ... -fixed raster export -fixed version numbering when no saga installation is found	2015-01-20 11:41:27 +01:00
Alexander Bruy	07462f5476	[processing] i18n support for SAGA provider	2015-01-17 11:24:54 +02:00
volaya	73f184e2e8	[processing] fixed handling of bool values in saga 213	2015-01-15 10:27:19 +01:00
volaya	aa60bfecb2	[processing] New system for handling SAGA versions ... This commit sets a different way of handling SAGA versions and a new way of checking saga installations This is done to fix the messy situation that SAGA causes due to its API changing in each release.	2015-01-15 10:27:18 +01:00