Re: [Qgis-developer] Testing new network analyses

Hi Paolo, 2016-12-13 20:44 GMT+02:00 Paolo Cavallini : > just compiled, testing the new functions, but I cannot get any result, > starting from OSM unprojected data. Anyone more lucky? I have used RoadGraph plugin several times with OSM data and it worked fine. Also I

Re: [Qgis-developer] Listener for Atlas Change Page

Thanks, that looks like exactly the kind of function that I'm looking for. I'm using QGIS 2.18.0, I'm wondering, is there any way to use this function without having to select a menu item in the the plugin? I'm not sure how to get started, because most of the existing plugins seem to be activated

Re: [Qgis-developer] Add virtual layer equivalent in Processing

Hi Victor, On Mon, Dec 5, 2016 at 6:16 PM, Anita Graser wrote: > Thanks Victor! > > On Mon, Dec 5, 2016 at 1:54 PM, Victor Olaya wrote: > >> Anita, Mathieu >> >> I added both of your requests and it should be possible now to use >> tables on both "execute

[Qgis-developer] Testing new network analyses

Hi all, just compiled, testing the new functions, but I cannot get any result, starting from OSM unprojected data. Anyone more lucky? A few notes: * the new widget to get coordinates from canvas is supernice, can it be uses for other modules (e.g. r.viewsed, and others from GRASS) as well? * in

[Qgis-developer] Plugin [1146] layer2kmz approval notification.

Plugin layer2kmz approval by pcav. The plugin version "[1146] layer2kmz 1.1" is now approved Link: http://plugins.qgis.org/plugins/layer2kmz/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info:

[Qgis-developer] Different file format for GML QGIS vs Processing

Hi all, I'm approaching to do some more test of Processing. I followed the guide on the repo (and also Matthias gav me some super useful advices) but something is strange with the output of Processing itself. I'm using QGIS 3 on a Linux Mint machine (fresh compiled) and when I save a vector as

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

ah - yes, now it works after Martins fix. So a side-effect of your refactoring. No problem Thanks all who gave me hints. I should be fine now. Andreas On 13.12.2016 17:21, Martin Dobias wrote: On Wed, Dec 14, 2016 at 12:00 AM, Andreas Neumann wrote: However, db

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

On Wed, Dec 14, 2016 at 12:00 AM, Andreas Neumann wrote: > > However, db manager still fails to start with error message: > > -- > > 2016-12-13T16:53:211Traceback (most recent call last): > File >

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

yes - I used the instructions from https://github.com/qgis/QGIS/blob/master/INSTALL but all "geo" libraries (geos, gdal, spatialite, postgres/postgis) had been installed from source. Is there a dependency python module list for db manager available? python3-psycopg is installed. Any other

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

Il 13/12/2016 17:00, Andreas Neumann ha scritto: > Can you confirm that DB-manager should work fine with the latest master? I confirm. Probably other py3 packages are missing. Did you insall what is in the requirements? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses:

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

Hi Marco, Thanks - this helped a lot. Apparently it was the missing python3-gdal bindings. I only had the bindings for python2. Processing now seems to work fine (at least the few tests I did). However, db manager still fails to start with error message: --

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

could be, it could also be a PYTHONPATH issue depenndign where you installed the bindings. can you import them in a python prompt? to build gdal with python 3 you need to do some thing like: cd gdal/swig/python python3 setup.py build & python3 setup.py install IIRC gdal compiles in its source

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

Hi, I get a message: Unable to load GdalTools plugin. The required "osgeo [python-gdal]" module is missing. Install it and try again. then there is a new error message: -- ImportError: No module named 'osgeo' -- I installed gdal

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

well, for once most plugins will fail at from PyQt4 import *, then they could fail at any API break. the core plugins go trough 2to3 (https://github.com/qgis/QGIS/blob/master/scripts/2to3) that should fixup most of the problems. on ubuntu 16.10 DBman and processing work. If you are porting a

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

On 12/13/2016 03:51 PM, Andreas Neumann wrote: Hi, I compiled and installed QGIS 3 - which worked fine. But at start of QGIS, none of the Python plugins seem to work, e.g. processing, db-manager, etc. all fail. Is this expected behaviour or is there something in my compile settings that would

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

Processing and db manager works under QGIS. What are the error messages you get? I d suspect missing Python 3 modules/packages being problem here. On Dec 13, 2016 21:51, "Andreas Neumann" wrote: > Hi, > > I compiled and installed QGIS 3 - which worked fine. But at start of

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

Il 13/12/2016 15:51, Andreas Neumann ha scritto: > Hi, > > I compiled and installed QGIS 3 - which worked fine. But at start of > QGIS, none of the Python plugins seem to work, e.g. processing, > db-manager, etc. all fail. Processing etc. working here on master. All the best. -- Paolo

Re: [Qgis-developer] Do Python plugins already work with QGIS 3?

Define "fail", I guess. Most plugins won't work without modification [citation needed], but it would be good to know *how* it fails, as you are right that there could be a more general issue. - Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon -- View this message in context:

[Qgis-developer] Do Python plugins already work with QGIS 3?

Hi, I compiled and installed QGIS 3 - which worked fine. But at start of QGIS, none of the Python plugins seem to work, e.g. processing, db-manager, etc. all fail. Is this expected behaviour or is there something in my compile settings that would make these Python "core" plugins work in

Re: [Qgis-developer] SAGA GIS 3.0

On 2016-12-13 14:30, Ted wrote: The current QGIS ships with SAGA-GIS 2.1.2. There are many version since 2.1.2 and the latest version of SAGA-GIS is 3.0 Wonder if QGIS 3.0 will use SAGA-GIS 3.0. Unlikely since its not a long term supported release. The 2.3.x LTS releases from SAGA are not

Re: [Qgis-developer] Plugin Openoise doesn't work without fTools

Hi Stefano, you need to use processing. FTools algorithms were moved htere. ciao Marco On 13.12.2016 11:39, Stefano Masera wrote: > Hi list, > my plugin OpeNoise uses fTools (it is imported in the code). > In the 2.16 and superior Qgis versions fTools doesn't exist > and consequently my plugin

[Qgis-developer] SAGA GIS 3.0

The current QGIS ships with SAGA-GIS 2.1.2. There are many version since 2.1.2 and the latest version of SAGA-GIS is 3.0 Wonder if QGIS 3.0 will use SAGA-GIS 3.0. http://www.saga-gis.org/saga_tool_doc/index.html Thanks ted ___ Qgis-developer

[Qgis-developer] Plugin Openoise doesn't work without fTools

Hi list, my plugin OpeNoise uses fTools (it is imported in the code). In the 2.16 and superior Qgis versions fTools doesn't exist and consequently my plugin Openoise doesn't work. How can I change my code in an easy way? Thanks. Stefano ___

Re: [Qgis-developer] should core plugins not be available in plugin manager?

2016-12-13 10:10 GMT+01:00 Nathan Woodrow : > IMO anything core is no longer a plugin, processing included. We don't have > these options for stuff like Python console etc so it doesn't make sense to > have it for the rest. > +1. Plugins should be "extra" things. Even if

Re: [Qgis-developer] should core plugins not be available in plugin manager?

IMO anything core is no longer a plugin, processing included. We don't have these options for stuff like Python console etc so it doesn't make sense to have it for the rest. - Nathan On Tue, Dec 13, 2016 at 6:30 PM, Régis Haubourg wrote: > Hi all, > just a reminder

Re: [Qgis-developer] should core plugins not be available in plugin manager?

Hi all, just a reminder that we have a --noplugins startup option that will deactivate plugins for testing purpose. What would be then the intended behaviour with core python plugins like processing? On my side, I would keep an option to do that, and if possible not rename it. So this is an

Re: [Qgis-developer] should core plugins not be available in plugin manager?

Il 13/12/2016 08:08, Neumann, Andreas ha scritto: > I do agree though that some core plugins could be removed or integrated > into the core. One example is the coordinate capture plugin, which could > be easily integrated in core, e.g. integrated in the identify tool or > status bar. big +1 from