[QGIS-Developer] moc_vectorlayer.cpp can't be create in vs2015

2018-01-31 Thread weskerjiang
Hello: I'm using QGIS-master to build QGIS, i use vs2015 msvc2015 x86 ,python 3.6, qt5 and other requirements,everything is ok,but when i build it in vs2015,the moc_vectorlayer.cpp is empty,so there comes a lot of errors like the image below.so who can tell me why moc_vectorlayer.cpp

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

2018-01-31 Thread Victor Olaya
+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] Get rid of Processing scripts in favour of plain alogrithms

2018-01-31 Thread G. Allegri
Cool! Probably it wasn't clear my suggestion, but that's exactly what I meant: keep "scripts" but get rid of the special syntax and implement QgsProcessingAlgorithm subclasses. Giovanni Il 1 feb 2018 06:26, "Nyall Dawson" ha scritto: > On 31 January 2018 at 18:24, G.

Re: [QGIS-Developer] Get rid of Processing scripts in favour of plain alogrithms

2018-01-31 Thread Nyall Dawson
On 31 January 2018 at 18:24, G. Allegri wrote: > I understand your point Victor, and I agree that scripts was a clever idea. > But: > > - with the current shape of Processing (QGIS 3.0) I think the "syntactic > sugar" provided by scripts has less relevance. As I can see from

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

2018-01-31 Thread Nyall Dawson
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] Any work done around flatpak/snap/appimage?

2018-01-31 Thread Jürgen E . Fischer
Hi Andreas, On Wed, 31. Jan 2018 at 16:01:02 +0100, Andreas Neumann wrote: > Is someone working on it? I know there have been discussions around it > already. See https://github.com/qgis/QGIS/pull/3545 Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31

Re: [QGIS-Developer] QgsExpression python pattern

2018-01-31 Thread Nyall Dawson
On 1 February 2018 at 05:45, Chris Crook wrote: > I am updating some plugins which use QgsExpression, and I'm wondering about > the best way to use expressions in QGIS3. It in the past I used a pattern > like: > > exp=QgsExpression(expressionText) > exp.prepare(fields)

Re: [QGIS-Developer] Question about Mac Installer

2018-01-31 Thread Tim Sutton
Hi > On 31 Jan 2018, at 18:55, Alex M wrote: > > Question 1. > The QGIS.org download page > https://qgis.org/en/site/forusers/download.html says: > "This version requires separate installation of dependency framework > (GDAL Complete) , also found at the download

Re: [QGIS-Developer] Any work done around flatpak/snap/appimage?

2018-01-31 Thread Jeremy Palmer
On 1/02/2018 04:01, "Andreas Neumann" wrote: Hi, A member from the German QGIS user group asked me whether QGIS.ORG plans to provide flatpak/snap or appimage versions of QGIS to allow simultaneous installations of different versions on the same machine, e.g. for testing

Re: [QGIS-Developer] QgsExpression python pattern

2018-01-31 Thread Chris Crook
Chris Crook wrote > I am updating some plugins which use QgsExpression, and I'm wondering > about the best way to use expressions in QGIS3. It in the past I used a > pattern like: > > exp=QgsExpression(expressionText) > exp.prepare(fields) > request=QgsFeatureRequest() >

[QGIS-Developer] QgsExpression python pattern

2018-01-31 Thread Chris Crook
I am updating some plugins which use QgsExpression, and I'm wondering about the best way to use expressions in QGIS3. It in the past I used a pattern like: exp=QgsExpression(expressionText) exp.prepare(fields) request=QgsFeatureRequest() request.setSubsetOfAttributes(

Re: [QGIS-Developer] Question about Mac Installer

2018-01-31 Thread Jürgen E . Fischer
Hi Alex, On Wed, 31. Jan 2018 at 08:55:32 -0800, Alex M wrote: > Question 1. > The QGIS.org download page > https://qgis.org/en/site/forusers/download.html says: > "This version requires separate installation of dependency framework > (GDAL Complete) , also found at the download link below."

[QGIS-Developer] Kernel density of SAGA broken?

2018-01-31 Thread matteo
Hi, sorry for continuing bombing the mailing list. I'm testing some random algorithms and it seems that the Kernel density of SAGA is broken. Or worst, it seems working, a kind of output is created (but it is not visible) and no error or stack traces. But from the shell I can read: ERROR 1:

[QGIS-Developer] Question about Mac Installer

2018-01-31 Thread Alex M
Question 1. The QGIS.org download page https://qgis.org/en/site/forusers/download.html says: "This version requires separate installation of dependency framework (GDAL Complete) , also found at the download link below." Kyngchaos says http://www.kyngchaos.com/software/qgis "All required items are

Re: [QGIS-Developer] Apply transparency on pixels in an image with PyQGIS

2018-01-31 Thread HerbertGourout
I'm trying to grab the pixels that intersect with my polygon shapefile and apply transparency to them (that is, I'm trying to create a hole in my raster) For that, I get all the pixels that are in the footprint of the shapefile in a list (see code below) Then I used the

Re: [QGIS-Developer] How are Featured Plugins Chosen?

2018-01-31 Thread C Hamilton
Here are my suggestions taking into account that this is highly subjective and different users are going to have their favorite plugins. Featured plugins should be bug free and have good documentation/tutorials on how to use them. Featured plugins should fall into one of several categories. 1.

[QGIS-Developer] Any work done around flatpak/snap/appimage?

2018-01-31 Thread Andreas Neumann
Hi, A member from the German QGIS user group asked me whether QGIS.ORG plans to provide flatpak/snap or appimage versions of QGIS to allow simultaneous installations of different versions on the same machine, e.g. for testing purposes. Is someone working on it? I know there have been

Re: [QGIS-Developer] How are Featured Plugins Chosen?

2018-01-31 Thread C Hamilton
Ignore that last e-mail. It was fat fingered and automatically sent. I am going to prepare the e-mail outside of firefox so I don't do that again. On Wed, Jan 31, 2018 at 9:46 AM, C Hamilton wrote: > Here are my suggestions taking into account that this is highly

Re: [QGIS-Developer] How are Featured Plugins Chosen?

2018-01-31 Thread C Hamilton
Here are my suggestions taking into account that this is highly subjective and different users are going to have their favorite plugins. I think featured plugins should include... 1. Semi-permanent plugins in the list that are used by a broad user community. The ones on the current list that I

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

2018-01-31 Thread Rashad Kanavath
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

2018-01-31 Thread Paolo Cavallini
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

2018-01-31 Thread Paolo Cavallini
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

2018-01-31 Thread Alexander Bruy
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] update of otb plugin for QGIS

2018-01-31 Thread Paolo Cavallini
Il 31/01/2018 09:53, Rashad Kanavath ha scritto: > yes. the wrapper will provide necessary descriptor file for otb > application that qgis processing can use. so I don't see any problem with this approach. thanks. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses:

Re: [QGIS-Developer] update of otb plugin for QGIS

2018-01-31 Thread Rashad Kanavath
On Wed, Jan 31, 2018 at 10:12 AM, Paolo Cavallini wrote: > Hi Rashad, > > Il 30/01/2018 09:00, Rashad Kanavath ha scritto: > > > Regarding qgis versions, there is nothing much to do if you don't change > > OTB. > > I think I understood better now, thanks. In practice, you

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

2018-01-31 Thread Rashad Kanavath
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

2018-01-31 Thread Paolo Cavallini
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

2018-01-31 Thread Rashad Kanavath
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

Re: [QGIS-Developer] update of otb plugin for QGIS

2018-01-31 Thread Paolo Cavallini
Hi Rashad, Il 30/01/2018 09:00, Rashad Kanavath ha scritto: > Regarding qgis versions, there is nothing much to do if you don't change > OTB. I think I understood better now, thanks. In practice, you mean adding to OTB a small package who would act as a wrapper for OTB algs withing QGIS? So

Re: [QGIS-Developer] Get rid of Processing scripts in favour of plain alogrithms

2018-01-31 Thread Victor Olaya
Right, I see you your point. I havent been able to follow the recent developments in Processing, and i have to admit i am a little bit lost (Nyall has been working too fast!!). So this is just my opinion, but it might not make sense in the current situation. I will try to get up to date as soon

Re: [QGIS-Developer] update of otb plugin for QGIS

2018-01-31 Thread Rashad Kanavath
Hello, On Wed, Jan 31, 2018 at 2:05 AM, Tisham Dhar wrote: > Hi Rashad, > > > > I meant pre-built OTB binaries rather than plugin binaries. I believe QGIS > builds on more platforms than OTB does. > > > plugin code is in python. so nothing much to worry on

Re: [QGIS-Developer] Not able to build QGIS with 3D on Ubuntu 16.04

2018-01-31 Thread matteo
Hi all, I'm writing this mail hoping to help somebody else that experienced the same problem with Ubuntu 16.04 and the build of QGIS with Qt 5.9 Following the instructions on Martin's website I had to adjust some small parameter: 1. **after** running ccmake and generating all the files I had to

Re: [QGIS-Developer] Get rid of Processing scripts in favour of plain alogrithms

2018-01-31 Thread G. Allegri
I understand your point Victor, and I agree that scripts was a clever idea. But: - with the current shape of Processing (QGIS 3.0) I think the "syntactic sugar" provided by scripts has less relevance. As I can see from the refactoring, there's less automation in parameters conversions and