Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

pcav wrote > Il 05/02/2018 22:03, Helmut Kudrnovsky ha scritto: >> and see here for a follow up in the GRASS community: >> >> http://osgeo-org.1560.x6.nabble.com/Keeping-GRASS-OTB-algorithm-in-qgis-processing-td5352828.html >>

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Paolo, pcav wrote > Il 05/02/2018 22:03, Helmut Kudrnovsky ha scritto: >> and see here for a follow up in the GRASS community: >> >> http://osgeo-org.1560.x6.nabble.com/Keeping-GRASS-OTB-algorithm-in-qgis-processing-td5352828.html >>

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 05/02/2018 22:03, Helmut Kudrnovsky ha scritto: > and see here for a follow up in the GRASS community: > > http://osgeo-org.1560.x6.nabble.com/Keeping-GRASS-OTB-algorithm-in-qgis-processing-td5352828.html >

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

rashadkm wrote > Hello all, > > Here is a PR to allow integration of otb smoothly. tests are all passing, > commits are squashed and ready to review. > https://github.com/qgis/QGIS/pull/6272 > I did a small fix to control visibility of parameter from provider. > Addition of specific parameter

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 05/02/2018 18:00, Rashad Kanavath ha scritto: > Hello all, > > Here is a PR to allow integration of otb smoothly. tests are all > passing, commits are squashed and ready to review. > https://github.com/qgis/QGIS/pull/6272 > I did a small fix to control visibility of parameter from provider. >

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hello all, Here is a PR to allow integration of otb smoothly. tests are all passing, commits are squashed and ready to review. https://github.com/qgis/QGIS/pull/6272 I did a small fix to control visibility of parameter from provider. Addition of specific parameter class for OTB is not included in

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

>Otherwise if we don't care and just want to enable others to have QGIS >intgration, they'll have to adopt the plugins. That might work better if there >is real interest. But I think they usally prefer their tools to be used in >their own environment and don't care that much about whether it

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 04/02/2018 12:27, Rashad Kanavath ha scritto: > If my proposal to keep otb provider in qgis was allowed, then it will be > two simple steps. But I don't see that happening soon. nothing is decided yet. > Anyways, if the provider is a plugin or not, it is important to have api > to show/hide

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Juergen, Il 03/02/2018 16:02, Jürgen E. Fischer ha scritto: > The question is who is the driving force behind the provider plugins. If we > want those algorithms in QGIS, we will probably have to maintain the plugins, > if we don't want them to die. > > Otherwise if we don't care and just

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On Mon, Feb 5, 2018 at 7:31 AM, Alexander Bruy wrote: > BTW, there is also another possible issue to consider. Where users > will report tickets related to OTB algorithms and who will address > them? Come on!. Users already reports issue to OTB if that is the problem.

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi all, sorry, I miss a point here: we have a dev who volunteers to maintain a piece of code. He is quite credible. His proposal minimize the overhead to QGIS code, and moves much of the complexity to an external sw. Why do we suggest to keep him out of the door? All the best. Il 05/02/2018

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On Mon, Feb 5, 2018 at 4:43 AM, Nyall Dawson wrote: > On 4 February 2018 at 22:27, Rashad Kanavath > wrote: > > > Well, OTB provider plugin will be able to fetch and install otb > binaries. So > > users installing plugin is the extra step

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On 4 February 2018 at 22:27, Rashad Kanavath wrote: > Well, OTB provider plugin will be able to fetch and install otb binaries. So > users installing plugin is the extra step needed. > 1. Install QGIS > 2. install otb provider plugin > 3. select/download && install

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On Sat, Feb 3, 2018 at 5:02 PM, Jürgen E. Fischer wrote: > Hi Paolo, > > On Thu, 01. Feb 2018 at 11:57:28 +, Paolo Cavallini wrote: > > Il 01/02/2018 11:51, Alexander Bruy ha scritto: > > > IMHO, if it is really important for them, they should find a way to > contact > > >

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Paolo, On Thu, 01. Feb 2018 at 11:57:28 +, Paolo Cavallini wrote: > Il 01/02/2018 11:51, Alexander Bruy ha scritto: > > IMHO, if it is really important for them, they should find a way to contact > > devs and support development. > > R provider was removed from core in May 2017 and as far

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi all, I think this new approach is more or less the same approach used in the early times of Sextante, before it is ported to QGIS core and become Processing. I remember that Sextante at that time had a very good feature, being an external plugin, that was the updates. They were not dependent

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Rashad, Il 02/02/2018 10:47, Rashad Kanavath ha scritto: > A user of application can select -type gaussian -type.gaussian.radius 3 > when launching application. > otb application check for invalid cases such as if type is gaussian then > one cannot use -type.mean.radius > This is okay for

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On Fri, Feb 2, 2018 at 12:36 AM, Nyall Dawson wrote: > On 1 February 2018 at 20:01, Rashad Kanavath > wrote: > > Hello, > > > > Processing plugin allows to integrate other toolboxes. IIUC, this was > one of > > the features of it. > > So when

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 01/02/2018 17:18, Jürgen E. Fischer ha scritto: > Hi Paolo, > > On Thu, 01. Feb 2018 at 11:04:58 +, Paolo Cavallini wrote: >> Il 01/02/2018 11:01, Rashad Kanavath ha scritto: >>> I think jef can do this part. I don't have access to repo > >> OK, thanks. Could you please open a ticket on

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On 1 February 2018 at 20:01, Rashad Kanavath wrote: > Hello, > > Processing plugin allows to integrate other toolboxes. IIUC, this was one of > the features of it. > So when you say integration of so and so toolboxes are total mess, you might > think back. I think

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Paolo, On Thu, 01. Feb 2018 at 11:04:58 +, Paolo Cavallini wrote: > Il 01/02/2018 11:01, Rashad Kanavath ha scritto: > > I think jef can do this part. I don't have access to repo > OK, thanks. Could you please open a ticket on osgeo4w tracker? No need. otb has been marked _obsolete in

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 01/02/2018 12:13, Alexander Bruy ha scritto: > Hi Giovanni, > > my point was that we still can not maintain hundreds of algorithms. well, we did, more or less efficiently, until now. I understand your point, however. all the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses:

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Giovanni, my point was that we still can not maintain hundreds of algorithms. 2018-02-01 14:08 GMT+02:00 Giovanni Manghi : > Hi Alex, > >> I'm afraid it is not true, there are lot of issue even with LTR SAGA, see >> for example https://issues.qgis.org/issues/17726.

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Alex, > I'm afraid it is not true, there are lot of issue even with LTR SAGA, see > for example https://issues.qgis.org/issues/17726. There are also some > recent threads in developers mailing list about broked SAGA and GRASS > modules. ok is not perfect :) but is for sure is much better

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 01/02/2018 11:51, Alexander Bruy ha scritto: > IMHO, if it is really important for them, they should find a way > to contact devs and support development. > > R provider was removed from core in May 2017 and as far as I can see > nobody asked about it in mailing lists. So I suppose it is not

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

IMHO, if it is really important for them, they should find a way to contact devs and support development. R provider was removed from core in May 2017 and as far as I can see nobody asked about it in mailing lists. So I suppose it is not important. 2018-02-01 13:40 GMT+02:00 Paolo Cavallini

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 01/02/2018 11:37, Alexander Bruy ha scritto: > I'm not a bit R fan and user, so updating this provider to QGIS 3 for me is > lower priority then updating other plugins or doing some work on QGIS core. quite understandable, nobody could possibly blame you. the fact remains that before removal

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

2018-02-01 12:59 GMT+02:00 Paolo Cavallini : > and also R provider, which if I understand correctly is orphaned now. > all the best. Well, to be precise it did not received much attention from its inclusion into core, there were tickets filed for this Provider which was not

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

2018-02-01 13:22 GMT+02:00 Giovanni Manghi : > After having decided to support only SAGA LTR (because we know we can't keep > the > pace with non LTR SAGA underlying changes) we are now finally at a > point (at least in QGIS 2.18) where users can reliably count with

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 01/02/2018 11:01, Rashad Kanavath ha scritto: > I think jef can do this part. I don't have access to repo OK, thanks. Could you please open a ticket on osgeo4w tracker? Thanks. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On Thu, Feb 1, 2018 at 11:57 AM, Paolo Cavallini wrote: > Il 01/02/2018 09:35, Rashad Kanavath ha scritto: > > OTB is not using ogeo4w for a long time. So OSGeo4W users are stuck on > > old version. We have zero interest in pushing packages back again > > Windows users can

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 01/02/2018 10:16, Alexander Bruy ha scritto: > code already here: > - grass > https://github.com/qgis/QGIS/tree/master/python/plugins/processing/algs/grass7 > - saga > https://github.com/qgis/QGIS/tree/master/python/plugins/processing/algs/saga > > Only small updates are needed to turn it

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 01/02/2018 10:00, Alexander Bruy ha scritto: > 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). and also R provider, which if I understand correctly is

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 01/02/2018 09:35, Rashad Kanavath ha scritto: > OTB is not using ogeo4w for a long time. So OSGeo4W users are stuck on > old version. We have zero interest in pushing packages back again > Windows users can use otb from its binary package, build from source , > or maintain osgeo4w or whatever

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Werner, code already here: - grass https://github.com/qgis/QGIS/tree/master/python/plugins/processing/algs/grass7 - saga https://github.com/qgis/QGIS/tree/master/python/plugins/processing/algs/saga Only small updates are needed to turn it into plugins. I can turn them into plugins and

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Alex, Thats exactly what I meant. I know that (currently) there are no plugin for SAGA and GRASS but if I understood everything correctly the point is to create such plugins. My Question was more or less if there is already code existing for it or if we have to wait until they are removed

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hello, Processing plugin allows to integrate other toolboxes. IIUC, this was one of the features of it. So when you say integration of so and so toolboxes are total mess, you might think back. Nobody had seen new changes to otb algs so all of your comments are on old version. Why so rush? Okay,

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

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.

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On Thu, Feb 1, 2018 at 9:32 AM, Jürgen E. Fischer wrote: > Hi Paolo, > > On Thu, 01. Feb 2018 at 08:23:30 +, Paolo Cavallini wrote: > > thanks for your offer, much appreciated. Would this include also the > > inclusion of OTB in the standalone installers for Windows? > > The

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

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

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Hi Paolo, On Thu, 01. Feb 2018 at 08:23:30 +, Paolo Cavallini wrote: > thanks for your offer, much appreciated. Would this include also the > inclusion of OTB in the standalone installers for Windows? The standalone installers are made from OSGeo4W packages. So otb should be updated there.

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

+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

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 01/02/2018 07:21, Victor Olaya ha scritto: > +1 from me. This is exactly the reasoning behind my original proposal > of removing providers from core. Whether the plugin is easy to > maintain or not, it is better to do it outside. People responsible of > the plugin can release whenever they

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

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

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

+1 from me. This is exactly the reasoning behind my original proposal of removing providers from core. Whether the plugin is easy to maintain or not, it is better to do it outside. People responsible of the plugin can release whenever they want, and they can do changes without having to do PRs to

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On 31 January 2018 at 20:23, Alexander Bruy wrote: > Another reason to remove providers is that algorithms descriptions > were not updated and maintained. Even now both SAGA and GRASS > providers are not updated to latest stable versions of the corresponding > software.

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On Wed, Jan 31, 2018 at 11:29 AM, Paolo Cavallini wrote: > Il 31/01/2018 10:26, Alexander Bruy ha scritto: > > It is included, but this version is really outdated isn't it? > > we can seek additional resources to maintain it. Perhaps OTB team is > interested in maintaining

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 31/01/2018 10:26, Alexander Bruy ha scritto: > It is included, but this version is really outdated isn't it? we can seek additional resources to maintain it. Perhaps OTB team is interested in maintaining it up to date? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 31/01/2018 10:23, Alexander Bruy ha scritto: > We just simply does not have enough resources to maintain more than > 600 algorithms from GRASS and SAGA. > I still think that Processing should be in core with minimal set of algorithms > (native and GDAL), all other providers should be plugins

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

It is included, but this version is really outdated isn't it? 2018-01-31 12:25 GMT+02:00 Paolo Cavallini : > Il 31/01/2018 10:17, Victor Olaya ha scritto: > >> that OTB has to be installed separately. Otherwise, we will see >> confusion and i think it will not be a good

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

On Wed, Jan 31, 2018 at 10:45 AM, Paolo Cavallini wrote: > Il 31/01/2018 09:40, Rashad Kanavath ha scritto: > > > With that change coming, are you folks interested to put back otb algo > > into processing/algs/otb.? > > I am supportive of this, even though I understand the

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

Il 31/01/2018 09:40, Rashad Kanavath ha scritto: > With that change coming, are you folks interested to put back otb algo > into processing/algs/otb.? I am supportive of this, even though I understand the argument that brought to the removal. All the best. -- Paolo Cavallini - www.faunalia.eu

[QGIS-Developer] Keeping OTB algorithm in qgis processing

Hello all, I would like to check the pros and cons of keeping otb in qgis processing like others. SAGA, GRASS, GDAL etc.. one or only argument, I found interesting is the fixes to otb plugin can be done independent of qgis release and versions. But how does other algorithms won't get this cool