Re: [Qgis-developer] New GRASS plugin: a test drive

Hi Radim, > Yes, it is now intended for two reasons. First, it could be confusing > for user if some maps were missing from input list. Second is > technical, to get list of layers in vector map may be time consuming, > the info must be read from the map (which was not the case with < 2.11 > wher

Re: [Qgis-developer] New GRASS plugin: a test drive

>> It > >> is compiled with LFS, which adds -D_LARGEFILE_SOURCE > >> -D_FILE_OFFSET_BITS=64 compiler flags. Try to add -D_LARGEFILE_SOURCE > >> -D_FILE_OFFSET_BITS=64 to QGIS cmake CXX_EXTRA_FLAGS > > > > With this flags it also works without problems! > > I added check for _FILE_OFFSET_BITS in Mak

Re: [Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

Hi, On Thu, Oct 22, 2015 at 2:53 AM, Nyall Dawson wrote: > On 22 October 2015 at 19:52, Nyall Dawson wrote: > > On 22 October 2015 at 12:28, Larry Shaffer > wrote: > >> > >> I meant specifically during the porting process. Then, break the API > and add > >> new features. For example, some plug

Re: [Qgis-developer] Improving ftools geoprocessing tools

Giovanni, Would (some of) these datasets be suitable to include in unit tests for processing? It would be very interesting to have these available for this purpose. Matthias On 10/22/2015 05:07 PM, Giovanni Manghi wrote: > On Thu, Oct 22, 2015 at 3:27 PM, Victor Olaya wrote: >>> The issue here

Re: [Qgis-developer] Improving ftools geoprocessing tools

On Thu, Oct 22, 2015 at 3:27 PM, Victor Olaya wrote: >> The issue here is about the lousy performances (and even wrong >> results) of the native qgis vector geoprocessing tools. I think we all >> agree that qgis should have a few (at least the most commonly used) >> ones, without depending on any

Re: [Qgis-developer] problem with GRASS 7 when creation a new mapset

On Thu, Oct 22, 2015 at 3:18 PM, matteo wrote: > Hi Radim, > thanks for the reply.. > >> You are running qgis from build (src in this case) dir? Try to install >> qgis and run it from installation target dir. You will have to add >> path to grass libs to LD_LIBRARY_PATH. > > yes.. I run QGIS from

Re: [Qgis-developer] Improving ftools geoprocessing tools

essing ones (which, in general, are just a copy of the ftools ones), and have them exposed through the menus, as explained above. Regards __ Information from ESET Mail Security, version of virus signature database 12448 (20151022) __ The message was checked by

[Qgis-developer] QGIS 2.12 visual changelog

Hi all, On Sunday I can invest some time to provide more information and screenshots to the visual changelog. Are there other people who can contribute? Andreas ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/ma

Re: [Qgis-developer] Improving ftools geoprocessing tools

> The issue here is about the lousy performances (and even wrong > results) of the native qgis vector geoprocessing tools. I think we all > agree that qgis should have a few (at least the most commonly used) > ones, without depending on any 3rd party software. I fully agree on that Do we have any

Re: [Qgis-developer] Improving ftools geoprocessing tools

> Icon support is already in Processing. The first versions actually > used the same ftools icons, but I removed that because there were new > algorithms being added, and it was quite messy to see some algorithms > with icons and others with the default icon. Instead, I started using > the same ico

Re: [Qgis-developer] Improving ftools geoprocessing tools

from ESET Mail Security, version of virus signature database 12448 (20151022) __ The message was checked by ESET Mail Security. http://www.eset.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Improving ftools geoprocessing tools

ms based on >>>>> Processing to avoid redundant (and more difficult to mantain) code. As >>>>> I said, this has already been discussed, but it is not yet >>>>> implemented. Maybe your funding could help us do it? >>>>> >>

Re: [Qgis-developer] Improving ftools geoprocessing tools

2015-10-22 15:13 GMT+02:00 Andreas Neumann : > If we'd replace the ftools (vector and raster menu) through processing. What > would replace them? Would we do research and see which of the alternative > processing providers provides best speed/reliability - if there are multiple > versions? It may b

Re: [Qgis-developer] Improving ftools geoprocessing tools

Information from ESET Mail Security, version of virus signature database 12448 (20151022) __ The message was checked by ESET Mail Security. http://www.eset.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Improving ftools geoprocessing tools

>> >> Yep. I think the user-friendliness of ftools are that a/ algorithms >> are offered in a simple and accessible menu items, and b/ the menu >> item icons _greatly_ ease the understanding of what algorithms do. >> Icon support is already in Processing. The first versions actually used the same

Re: [Qgis-developer] Improving ftools geoprocessing tools

n of virus signature database 12448 (20151022) __ The message was checked by ESET Mail Security. http://www.eset.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/m

Re: [Qgis-developer] Improving ftools geoprocessing tools

/me adding "icon" to the list of actions Therefore the plan of action should be: * Add icon support to processing * Create menu entries for often used (internal) processing algorithms * Remove ftools algorithms * Identify slow algorithms * Improve performance Cheers Matthias On 10/22/2015

Re: [Qgis-developer] Improving ftools geoprocessing tools

Yep. I think the user-friendliness of ftools are that a/ algorithms are offered in a simple and accessible menu items, and b/ the menu item icons _greatly_ ease the understanding of what algorithms do. Both can be added to processing. On 22 Oct 2015 20:26, "Matthias Kuhn" wrote: > Hi Giovanni, >

Re: [Qgis-developer] Improving ftools geoprocessing tools

Some time ago Carson ported at least some fTools algorithms to QGIS analysis library. Maybe we can revise this code, update it and then reuse in Processing and 3rd party plugins? Core implementation should be faster than Python code, also maybe we can adopt multithreading approach for some alforot

Re: [Qgis-developer] Improving ftools geoprocessing tools

Hi Giovanni, On 10/22/2015 02:38 PM, Giovanni Manghi wrote: > This users are > usually not able to handle (or willingly to) the possible problems of > using a toolbox based on other software. There are a number of internal algorithms available in processing (i.e. no external dependencies). Unfor

Re: [Qgis-developer] Improving ftools geoprocessing tools

tinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer __ Information from ESET Mail Security, version of virus signature database 12448 (20151022) __ The message was

Re: [Qgis-developer] problem with GRASS 7 when creation a new mapset

Hi Radim, thanks for the reply.. > You are running qgis from build (src in this case) dir? Try to install > qgis and run it from installation target dir. You will have to add > path to grass libs to LD_LIBRARY_PATH. yes.. I run QGIS from build (/home/ma7730/lavori/QGIS/QGIS-Master/buildM/output)

Re: [Qgis-developer] Improving ftools geoprocessing tools

QGIS 3.0 seems to be a good moment/opportunity to terminate ftools and replace the menu items to be shortcuts to processing algorithms. M On 22 Oct 2015 19:59, "Victor Olaya" wrote: > > > > * Why is the processing toolbox not an option for your users? (Do you > > require shortcuts (menu entries

Re: [Qgis-developer] Improving ftools geoprocessing tools

If we'd replace the ftools (vector and raster menu) through processing. What would replace them? Would we do research and see which of the alternative processing providers provides best speed/reliability - if there are multiple versions? It may be, that for Algorithm A, Saga works best, whereas

Re: [Qgis-developer] Improving ftools geoprocessing tools

> > * Why is the processing toolbox not an option for your users? (Do you > require shortcuts (menu entries) to the tools? Is it the parameter > interface which is more fine-tuned? Missing functionality?) If what you need is to have the tools in a menu, we have been discussing that before, and t

Re: [Qgis-developer] Improving ftools geoprocessing tools

oaches for this problem to get to a long-term enhancement. > > Best regards, > Matthias > > > -- next part -- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 819 bytes > Desc: OpenPGP digital s

Re: [Qgis-developer] problem with GRASS 7 when creation a new mapset

On Wed, Oct 21, 2015 at 5:04 PM, matteo wrote: > Hi all, > I hope that this problem is not already been discussed.. > I'm trying to test the GRASS 7 plugin but I get always the same error > during the creation of the new mapset: You are running qgis from build (src in this case) dir? Try to insta

Re: [Qgis-developer] Improving ftools geoprocessing tools

Hi João, Nice that there is interest in improving the analysis part of QGIS. There was recently a similar discussion with Bernhard Ströbl who also put some effort into improving the dissolve tool (although it turned out to be complex and will probably only be merged in 2.14). In the discussion t

Re: [Qgis-developer] encoding in custom python functions

Ah... I think I now understand what you are saying. You are saying that expression files are always saved in your system default encoding system. Sorry for the noise. Lauri Kajan escreveu no dia qui, 22/10/2015 às 13:25: > Hi Alexandre, > > The u'ä' works if I tell the file encoding using your

Re: [Qgis-developer] encoding in custom python functions

Hi Alexandre, The u'ä' works if I tell the file encoding using your snippet # -*- coding: utf-8 -*- But this works only in qgis and is not a correct way. I cannot then debug my function in any IDE cause the file is encoded differently than it says. -Lauri On Thu, Oct 22, 2015 at 1:37 PM, Alexan

Re: [Qgis-developer] Improving ftools geoprocessing tools

Am 22.10.2015, 13:30 Uhr, schrieb João Gaspar : Dear QGIS Developers, I'm writing on behalf of my employer, a company that has mixed, proprietary and open source (especially QGIS of course) gis infrastructure, with qgis being adopted each day a little more. Actually in our migration path we hav

[Qgis-developer] Improving ftools geoprocessing tools

Dear QGIS Developers, I'm writing on behalf of my employer, a company that has mixed, proprietary and open source (especially QGIS of course) gis infrastructure, with qgis being adopted each day a little more. Actually in our migration path we have found a road blocker: the very bad performances (

Re: [Qgis-developer] encoding in custom python functions

Have you tried to put the following line in the top of the file? # -*- coding: utf-8 -*- Lauri Kajan escreveu no dia qui, 22/10/2015 às 08:42: > Hi all, > > I'm trying to figure out some encoding problems when using custom python > expression functions. > > I'm using python functions for defi

[Qgis-developer] API : how to rename legend items?

Hi, I need to rename legend items using the qGIS API for python. The legend items are related to a raster layer displayed in pseudocolor. Is there any way to set a label for each value of the legend using the API? Best Regards. Bastien Breteau. ___ Qg

Re: [Qgis-developer] Create grid in Processing: no polygons?

I use processing directly from master branch (symbolic link in my .qgis2/python/plugins folder to QGIS master branch processing folder) And I run a relatively recent build of QGIS binaries, from master branch, under Ubtuntu 14.04. Arnaud Le 22/10/2015 11:11, Paolo Cavallini a écrit : Il 22/

Re: [Qgis-developer] New GRASS plugin: a test drive

On Wed, Oct 21, 2015 at 10:04 PM, Pedro Venâncio wrote: > Hi again Radim, > > I was looking at typemask Option tag, and his definition says "for vector > input option defines allowed types. Only the layers of one of defined type > are displayed in input", but at this moment, all types are displaye

Re: [Qgis-developer] Create grid in Processing: no polygons?

Il 22/10/2015 11:08, Arnaud Morvan ha scritto: > > Hi Paolo, > > Just tested "Vector grid" and "Create grid" from master, > all seems to works as expected. Thanks. Tested on more machines, some work, some not. Trying to understand the reasons. Which version do you use? All the best. -- Paolo C

Re: [Qgis-developer] Create grid in Processing: no polygons?

Hi Paolo, Just tested "Vector grid" and "Create grid" from master, all seems to works as expected. Arnaud Le 22/10/2015 10:56, Paolo Cavallini a écrit : Hi all, with current master from yesterday, the command returns always line layers, never polygons, regardless of the choice of the user: an

Re: [Qgis-developer] New GRASS plugin: a test drive

On Wed, Oct 21, 2015 at 8:33 PM, Pedro Venâncio wrote: >> It >> is compiled with LFS, which adds -D_LARGEFILE_SOURCE >> -D_FILE_OFFSET_BITS=64 compiler flags. Try to add -D_LARGEFILE_SOURCE >> -D_FILE_OFFSET_BITS=64 to QGIS cmake CXX_EXTRA_FLAGS > > With this flags it also works without problems!

[Qgis-developer] Create grid in Processing: no polygons?

Hi all, with current master from yesterday, the command returns always line layers, never polygons, regardless of the choice of the user: anyone confirms? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___

Re: [Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

On 22 October 2015 at 19:52, Nyall Dawson wrote: > On 22 October 2015 at 12:28, Larry Shaffer wrote: >> >> I meant specifically during the porting process. Then, break the API and add >> new features. For example, some plugin devs might need to fix up their >> plugins for all three: Qt5, Py3 and

Re: [Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

On 22 October 2015 at 12:28, Larry Shaffer wrote: > > I meant specifically during the porting process. Then, break the API and add > new features. For example, some plugin devs might need to fix up their > plugins for all three: Qt5, Py3 and API. If we do all three and introduce > new features, du

Re: [Qgis-developer] Possible memory leak in QGIS redraws?

On 22-10-15 09:35, Nyall Dawson wrote: On 21 Oct 2015 6:49 PM, "Nyall Dawson" > wrote: > > > On 21 Oct 2015 3:20 PM, "Nyall Dawson" > wrote: > > > > On 9 October 2015 at 01:45, Régis Haubourg > >

Re: [Qgis-developer] Possible memory leak in QGIS redraws?

Swet! I'm out of office right now. I will test next week. Anyway, thanks a lot for that impressive work. I love that community. Cheers Regis Régis Haubourg Le 22 oct. 2015 09:35, Nyall Dawson a écrit : On 21 Oct 2015 6:49 PM, "Nyall Dawson" mailto:nyall.daw...@gmail.com>> wrote: > > > On

[Qgis-developer] encoding in custom python functions

Hi all, I'm trying to figure out some encoding problems when using custom python expression functions. I'm using python functions for defining some label texts. I need use some special characters like ä and ö. When a new file is created in function editor the file is encoded in my system encodin

Re: [Qgis-developer] Possible memory leak in QGIS redraws?

On 21 Oct 2015 6:49 PM, "Nyall Dawson" wrote: > > > On 21 Oct 2015 3:20 PM, "Nyall Dawson" wrote: > > > > On 9 October 2015 at 01:45, Régis Haubourg > > wrote: > > > Hi all, > > > I try to narrow down a production issue here. > > > In long sessions with lot's of redraws on complex projects, memo