[QGIS-Developer] Keeping OTB algorithm in qgis processing

Alexander Bruy alexander.bruy at gmail.com
Thu Feb 1 02:00:13 PST 2018


Hi Werner,

there are no plugins for SAGA and GRASS, but this is just because they
are in core.
Also seems we need to clarify, removal from core does not means wiping
all stuff,
this just mean that existing code will be separated into plugin and
published on GitHub
and QGIS plugins repository. Then interested people can take ownership
and continue
development and maintenance.

Exactly in the same way we removed LiDAR tools provider (now
maintained by Martin Isenburg)
and TauDEM provider (maintained by me, along with several others
Processing providers).

2018-02-01 10:39 GMT+02:00 Werner Macho <werner.macho at gmail.com>:
> Hi all,
>
> I am also in favour of removing all the work that is not directly related to
> QGIS.
> But I'd also like to ask if there is already a plugin available (on github?)
> that for e.g. readds the GRASS functionality?
> Furthermore I'd like to know if it is possible to create a plugin for
> official stable GRASS and GRASS development version, which in the best case
> can be installed side by side?
> (Same applies to SAGA and all the other providers).
>
> I am sure there is a huge possibility that an ecosystem will be created
> around those kind of plugins.
>
> kind regards
> Werner
>
> On Thu, Feb 1, 2018 at 9:33 AM, G. Allegri <giohappy at gmail.com> wrote:
>>
>> +1 also from me to the removal of the providers from core. IMHO I would
>> also remove GRASS, but I understand it could be a tough decision.
>> The provider system + plugin architecture provide all the means to keep
>> them separate from the core.
>>
>> We all agree, I guess, that less is better then more, to guarantee the
>> highest quality we can afford.
>>
>> Giovanni
>>
>> Il 1 feb 2018 09:23, "Paolo Cavallini" <cavallini at faunalia.it> ha scritto:
>>>
>>> Hi Rashad,
>>>
>>> Il 31/01/2018 10:43, Rashad Kanavath ha scritto:
>>>
>>> > What I can propose is to lower the burden on maintenance but the code
>>> > should be put back to qgis if possible.
>>> > So qgis can focus on issue related only to that and after a while
>>> > things
>>> > will stabilize.
>>> >
>>> > Indeed, if there is something broken in this algo otb team will help
>>> > fix it.
>>>
>>> thanks for your offer, much appreciated. Would this include also the
>>> inclusion of OTB in the standalone installers for Windows? It would be
>>> good to make sure we always have the most appropriate version, both for
>>> 32 and 64 bit.
>>> All the best.
>>>
>>> --
>>> Paolo Cavallini - www.faunalia.eu
>>> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
>>> https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
>>> _______________________________________________
>>> QGIS-Developer mailing list
>>> QGIS-Developer at lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer at lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Alexander Bruy


More information about the QGIS-Developer mailing list