Re: [Qgis-developer] Testing new network analyses

[Alexander Bruy]

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 tested Processing algs with projected and not projected OSM data, it
also worked for me. Maybe your points are placed too far from roads or network
itself contains gaps? In this case adjusting topology tolerance may help.

> * 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?

This widget was added about year ago or even later (can't remember exactly when
I made it). And of course it can be used in any Processing algorithm.

> * in case of projected layers, the coords as taken from the canvase
> should be backprojected to original layer CRS.

This is known issue and it is also happens for extent selector. There
are no solution
at the moment, but we (Victor and me) plan to work on it. Hope this
will be fixed before
release. Related ticket https://hub.qgis.org/issues/15680.

> * several commands are still missing to be on par with GRASS v.net
> modules: would it be usefult to make a list of missing functionalities?
> Should I fill tickets not to forget about it?

Well, I never thought about being on par with GRASS and don't know if this makes
sense.


-- 
Alexander Bruy
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Shawn Tse]

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 by a menu item or a toolbar button in the main
editor instead of via the atlas interface.

Thank you and I really appreciate the help!

On Mon, Dec 12, 2016 at 11:02 PM, Nyall Dawson  wrote:
>
>
> On 13 Dec 2016 4:44 PM, "Shawn Tse"  wrote:
>
> Hi all,
>
> I'm interested in being able to make graphs that update depending on
> what the active feature in the atlas is. I know some python and a
> little bit of the QGIS API, but I'm curious - is there some sort of
> listener function for the atlas that gets called whenever the Preview
> Atlas/Prev Feature/Next Feature/First Feature/Last Feature buttons are
> pressed?
>
>
> Try QgsAtlasComposition::featureChanged. See
> https://qgis.org/api/classQgsAtlasComposition.html#ab1a15fdb6d20ebb1254ebb6714254fac
>
> Nyall
>
>
> What I eventually want to do is to manipulate the node items that were
> created in a recent updated version of QGIS, and use them to make a
> line graph, gridlines, etc.
>
> I'm hoping to draw the data directly from the shapefiles themselves or
> from a .csv file.
>
> I originally tried to use an expression in a text box to do this, but
> it seems that expressions are unable to use custom functions to
> manipulate the composer. So I'm hoping that there's some sort of
> Listener method.
>
> Thanks.
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Anita Graser]

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 SQL" and "build virtual vector" algorithms
>>
>> Let me know if you try it (it is on master)
>
>
> The SQL statement I want to execute (and which runs well in Layer | Add
> Layer | Add Virtual Layer) is:
>
> select s_out.y1_statefips, s_out.y2_statefips,
>   st_centroid(f.geometry)
> from fips as f
> join stateoutflow1415 as s_out
> on f.fips = s_out.y1_statefips​
>

​Which Processing tool should I use to create a layer from the above
statement?

Thank you and best wishes,
Anita​
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Testing new network analyses

[Paolo Cavallini]

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 case of projected layers, the coords as taken from the canvase
should be backprojected to original layer CRS.
* several commands are still missing to be on par with GRASS v.net
modules: would it be usefult to make a list of missing functionalities?
Should I fill tickets not to forget about it?
All the best, and thanks Alex!
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[noreply]

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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[matteo]

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 GML as external file with Processing 2 files are created:

1. layer.gml
2. layer.xsd

Instead if I save the same layer from QGIS (or another shapefile) as
GML, QGIS writes 2 files:

1. layer.gml
2. layer.gfs


I saw that in the expected folder of the processing test there are only
gml-gfs file.

Could the .xsd file gave some problem when running tests? Even if not,
why the saving process creates different file whether one uses QGIS or
Processing?


Thanks to all

Matteo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Andreas Neumann]

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 manager still fails to start with error message:

--

2016-12-13T16:53:211Traceback (most recent call last):
   File
"/usr/local/share/qgis/python/plugins/db_manager/db_manager_plugin.py", line
108, in run
 from .db_manager import DBManager
   File "/usr/local/share/qgis/python/qgis/utils.py", line 647,
in _import
 mod = _builtin_import(name, globals, locals, fromlist,
level)
   File
"/usr/local/share/qgis/python/plugins/db_manager/db_manager.py", line 36, in

 from .layer_preview import LayerPreview
   File "/usr/local/share/qgis/python/qgis/utils.py", line 647,
in _import
 mod = _builtin_import(name, globals, locals, fromlist,
level)
   File
"/usr/local/share/qgis/python/plugins/db_manager/layer_preview.py", line 27,
in 
 from qgis.gui import QgsMapCanvas, QgsMapCanvasLayer,
QgsMessageBar
 ImportError: cannot import name 'QgsMapCanvasLayer'

My bad - should be fixed now in latest master.

Cheers
Martin


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Martin Dobias]

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
> "/usr/local/share/qgis/python/plugins/db_manager/db_manager_plugin.py", line
> 108, in run
> from .db_manager import DBManager
>   File "/usr/local/share/qgis/python/qgis/utils.py", line 647,
> in _import
> mod = _builtin_import(name, globals, locals, fromlist,
> level)
>   File
> "/usr/local/share/qgis/python/plugins/db_manager/db_manager.py", line 36, in
> 
> from .layer_preview import LayerPreview
>   File "/usr/local/share/qgis/python/qgis/utils.py", line 647,
> in _import
> mod = _builtin_import(name, globals, locals, fromlist,
> level)
>   File
> "/usr/local/share/qgis/python/plugins/db_manager/layer_preview.py", line 27,
> in 
> from qgis.gui import QgsMapCanvas, QgsMapCanvasLayer,
> QgsMessageBar
> ImportError: cannot import name 'QgsMapCanvasLayer'

My bad - should be fixed now in latest master.

Cheers
Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Andreas Neumann]

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 SQL modules or other modules the 
DB manager requires?


Andreas


On 13.12.2016 17:02, Paolo Cavallini wrote:

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.



___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Paolo Cavallini]

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: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Andreas Neumann]

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:

--

2016-12-13T16:53:211Traceback (most recent call last):
  File 
"/usr/local/share/qgis/python/plugins/db_manager/db_manager_plugin.py", 
line 108, in run

from .db_manager import DBManager
  File "/usr/local/share/qgis/python/qgis/utils.py", line 
647, in _import
mod = _builtin_import(name, globals, locals, fromlist, 
level)
  File 
"/usr/local/share/qgis/python/plugins/db_manager/db_manager.py", line 
36, in 

from .layer_preview import LayerPreview
  File "/usr/local/share/qgis/python/qgis/utils.py", line 
647, in _import
mod = _builtin_import(name, globals, locals, fromlist, 
level)
  File 
"/usr/local/share/qgis/python/plugins/db_manager/layer_preview.py", line 
27, in 
from qgis.gui import QgsMapCanvas, QgsMapCanvasLayer, 
QgsMessageBar

ImportError: cannot import name 'QgsMapCanvasLayer'

--

Can you confirm that DB-manager should work fine with the latest master?

Thanks,

Andreas


On 13.12.2016 16:40, Marco Bernasocchi wrote:

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 dir so for qgis for android I just used
to copy the whole GDAL folder before building to keep a clean copy.

more info:
https://trac.osgeo.org/gdal/wiki/GdalOgrInPython
https://trac.osgeo.org/gdal/wiki/BuildingOnUnix

ciao
Marco


On 13.12.2016 16:23, Andreas Neumann wrote:

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 from source, but enabled Python and also enabled shared
libraries.


Could it be that gdal was compiled with Python 2 while QGIS runs with
Python 3?


If that's the case, how can i compile GDAL with Python 3 support?


Can I compile gdal with Python 2 and 3 support if I want QGIS 2.x and
3.x on the same machine?

Thanks,
Andreas

On 13.12.2016 15:55, Tom Chadwin wrote:

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: 
http://osgeo-org.1560.x6.nabble.com/Do-Python-plugins-already-work-with-QGIS-3-tp5299693p5299694.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer



___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer



___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Marco Bernasocchi]

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 dir so for qgis for android I just used
to copy the whole GDAL folder before building to keep a clean copy.

more info:
https://trac.osgeo.org/gdal/wiki/GdalOgrInPython
https://trac.osgeo.org/gdal/wiki/BuildingOnUnix

ciao
Marco


On 13.12.2016 16:23, Andreas Neumann wrote:
> 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 from source, but enabled Python and also enabled shared
> libraries.
> 
> 
> Could it be that gdal was compiled with Python 2 while QGIS runs with
> Python 3?
> 
> 
> If that's the case, how can i compile GDAL with Python 3 support?
> 
> 
> Can I compile gdal with Python 2 and 3 support if I want QGIS 2.x and
> 3.x on the same machine?
> 
> Thanks,
> Andreas
> 
> On 13.12.2016 15:55, Tom Chadwin wrote:
>> 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: 
>> http://osgeo-org.1560.x6.nabble.com/Do-Python-plugins-already-work-with-QGIS-3-tp5299693p5299694.html
>> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> 
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 

-- 
Marco Bernasocchi
OPENGIS.ch - berna.io - 27summits.ch



signature.asc
Description: OpenPGP digital signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Andreas Neumann]

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 from source, but enabled Python and also enabled shared 
libraries.



Could it be that gdal was compiled with Python 2 while QGIS runs with 
Python 3?



If that's the case, how can i compile GDAL with Python 3 support?


Can I compile gdal with Python 2 and 3 support if I want QGIS 2.x and 
3.x on the same machine?


Thanks,
Andreas

On 13.12.2016 15:55, Tom Chadwin wrote:

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: 
http://osgeo-org.1560.x6.nabble.com/Do-Python-plugins-already-work-with-QGIS-3-tp5299693p5299694.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Marco Bernasocchi]

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 plugin to QGIS3 I suggest you to have a look at the
qgis2compat plugin which will make your life much easier in keeping a
plugin working wut the QGIS 2 and 3 API.

www.opengis.ch/qgis2compat

ciao
Marco

On 13.12.2016 15:55, Tom Chadwin wrote:
> 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: 
> http://osgeo-org.1560.x6.nabble.com/Do-Python-plugins-already-work-with-QGIS-3-tp5299693p5299694.html
> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 

-- 
Marco Bernasocchi
OPENGIS.ch - berna.io - 27summits.ch



signature.asc
Description: OpenPGP digital signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Richard Duivenvoorde]

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 make these Python "core" plugins work in QGIS 3.0 on Python 3?


During compilation there is (was?) a script which fixed python2 lingua 
to python3 (scripts/2to3). You need python3 future for that (on Debian):


pip3 install future

Maybe during your compilation/installation this step failed?

There are also some plugins already (preliminary, as api can still 
change) ported to 3:


https://plugins.qgis.org/plugins/plugins.xml?qgis=3.0

The Core plugins you name, work here with me on Debian testing.

Regards,

Richard


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Mathieu Pellerin]

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 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 QGIS 3.0 on Python 3?
>
> Thanks,
>
> Andreas
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Paolo Cavallini]

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 Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Tom Chadwin]

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: 
http://osgeo-org.1560.x6.nabble.com/Do-Python-plugins-already-work-with-QGIS-3-tp5299693p5299694.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Andreas Neumann]

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 QGIS 3.0 on Python 3?


Thanks,

Andreas

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] SAGA GIS 3.0

[Bas Couwenberg]

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 properly supported in QGIS yet 
either.


Kind Regards,

BAs
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Marco Bernasocchi]

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 Openoise doesn't work.
> 
> How can I change my code in an easy way?
> 
> Thanks.
> Stefano
> 
> 
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 

-- 
Marco Bernasocchi
OPENGIS.ch - berna.io - 27summits.ch



signature.asc
Description: OpenPGP digital signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] SAGA GIS 3.0

[Ted]

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 mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Stefano Masera]

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 

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Victor Olaya]

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 they are formally a
plugin, things like DB manager or Processing should be considered core
and handled just like, for instance, the layers panel or the python
console. Will be clearer for user also, i think. They dont have to
know about the implementation, if it's C++ or Python, or that kind of
things...they just have the functionality in there and use it.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[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.

- Nathan

On Tue, Dec 13, 2016 at 6:30 PM, Régis Haubourg 
wrote:

> 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 argument to support the idea of naming them plugin
> (because they are plugins from a code point of view).
>
> Thinking loudly, maybe a CLI option to choose explicitly the list of
> plugins to load could even be better. That way default behavior will always
> have plugins loaded, but edge uses cases still have a way to avoid loading
> some at all.
> Opinions?
> Régis
>
> 2016-12-13 9:01 GMT+01:00 Paolo Cavallini :
>
>> 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 me
>>
>> > Probably the EVIS plugin is another candidate with lots of overlaps. If
>> > we add the missing functionality the EVIS plugin provides to core, we
>> > could get rid of it.
>>
>> also a big +1 (could be more work though.
>> 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=IT=qgis,arcgis
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Régis Haubourg]

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 argument to support the idea of naming them plugin
(because they are plugins from a code point of view).

Thinking loudly, maybe a CLI option to choose explicitly the list of
plugins to load could even be better. That way default behavior will always
have plugins loaded, but edge uses cases still have a way to avoid loading
some at all.
Opinions?
Régis

2016-12-13 9:01 GMT+01:00 Paolo Cavallini :

> 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 me
>
> > Probably the EVIS plugin is another candidate with lots of overlaps. If
> > we add the missing functionality the EVIS plugin provides to core, we
> > could get rid of it.
>
> also a big +1 (could be more work though.
> 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=IT=qgis,arcgis
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Paolo Cavallini]

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 me

> Probably the EVIS plugin is another candidate with lots of overlaps. If
> we add the missing functionality the EVIS plugin provides to core, we
> could get rid of it.

also a big +1 (could be more work though.
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=IT=qgis,arcgis
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer