[QGIS-Developer] Suggestion to integrate MCG image segmentation in QGIS

[Sophie Crommelinck]

Hello,

For my PhD research, I have developed the BoundaryDelineation QGIS plugin
that aims to facilitate manual digitization from remote sensing imagery. As
an input, it requires object outlines obtained through image segmentation.
I have tested different image segmentations in QGIS, but found that
external approaches from computer vision provide better object outlines.
For the purpose of cadastral mapping that requires to digitize along roads,
buildings, rivers, fences, etc., I obtained accurate contours around
visible objects from drone, aerial and satellite imagery with Multiscale
Combinatorial Grouping (MCG) from Berkeley University. The code is open
source (
https://www2.eecs.berkeley.edu/Research/Projects/CS/vision/grouping/mcg/#).
However, it is partly pre-compiled for Matlab and does not work under
Windows. In order to keep the geo-reference of input images, I have added
two small scripts (
https://github.com/SCrommelinck/Delineation-Tool/tree/master/v3.0/1_image_segmentation).
Here is a video that shows MCG results on rural aerial imagery as well as
the use of the plugin: https://www.youtube.com/watch?v=GrDv8fW53Fs. MCG
results on peri-urban drone imagery can be seen here:
https://arxiv.org/abs/1904.12586

If this image segmentation would be included in QGIS, a user would not rely
on processing input data externally before being able to use the
BoundaryDelineation plugin. Furthermore, QGIS would incorporate and
facilitate the use of a state of the art computer vision image
segmentation. Segmenting an image into larger objects is an often applied
first step in many mapping and classification procedures.

My question is how to check whether someone would be interested to
implement MCG in QGIS. My own programming skills are not elaborated enough.
Should I open a feature request here: https://github.com/qgis/QGIS/issues,
or is posting my suggestion to this mailing list the way to go?

Best,

Sophie
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] How to structure GitHub repository for different plugin versions

[Sophie Crommelinck]

Hi Martin and Richard,

thanks for the fast reply. I will use branches (one master for QGIS3 and
one for QGIS2) instead of folders in GitHub.

Best,

Sophie

On Fri, 24 Aug 2018 at 11:11, Richard Duivenvoorde 
wrote:

> On 08/24/2018 10:57 AM, Sophie Crommelinck wrote:
> > Hi,
> >
> > I would like to upload a QGIS3 version of a plugin that is now available
> > as QGIS2 version. Is there a general approach on how to structure the
> > plugin repository on GitHub accordingly? One idea would be to have two
> > folders e.g. 'QGIS2' and 'QGIS3' in the main plugin repository. Paolo
> > suggested there might be a general code of conduct on this one.
>
> Hi Sophie,
>
> not sure what the 'best' way is, but what I did when I created a new
> version of the pdokservicesplugin, is to create a separate  git branch
> for the qgis2 version, and I keep the master branch for qgis3, see
>
> https://github.com/rduivenvoorde/pdokservicesplugin/tree/qgis2branch
> vs
> https://github.com/rduivenvoorde/pdokservicesplugin/tree/master
>
> I made QGIS3 'master' because the qgis2 branch will get unused in near
> future.
>
> I checked out both branches in different folders on my dev laptop, so
> can code/commit independently from each other.
>
> Regards,
>
> Richard Duivenvoorde
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] How to structure GitHub repository for different plugin versions

[Sophie Crommelinck]

Hi,

I would like to upload a QGIS3 version of a plugin that is now available as
QGIS2 version. Is there a general approach on how to structure the plugin
repository on GitHub accordingly? One idea would be to have two folders
e.g. 'QGIS2' and 'QGIS3' in the main plugin repository. Paolo suggested
there might be a general code of conduct on this one.

Best,

Sophie
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] GRASS r.kappa not working in QGIS plugin

[Sophie Crommelinck]

I just noted that everything works fine, when the module r.kappa is run
once manually via the toolbox in QGIS before running the plugin. When I
open QGIS (I am using the latest QGIS 3.3.0 nightly build version) and run
the plugin directly, the GRASS module r.kappa in the plugin doesn't work.
When I open QGIS, run r.kappa via the toolbox and run the plugin then, the
GRASS module r.kappa in the plugin works fine. Not sure how to fix this.

Best,
Sophie

On Mon, 6 Aug 2018 at 08:10, Sophie Crommelinck <
sophie.crommeli...@gmail.com> wrote:

> Hello,
>
>
> I am working on a QGIS plugin, that should use the module r.kappa from
> GRASS. It looks like this in my plugin source code:
>
> processing.run('grass7:r.kappa',
>{"classification": classificationLayer,
> "reference": referenceLayer,
> "title": 'ACCURACY ASSESSMENT',
> "-h": False,
> "-w": False,
> "GRASS_REGION_CELLSIZE_PARAMETER": cellSize,
> "GRASS_REGION_PARAMETER": None,
> "output": outputFile})
>
> As an error, I get a QgsProcessingException saying 'There were errors
> executing the algorithm'.
>
> If I run the same manually in QGIS via the toolbox, everything works fine.
> Both calls of the module (manually and via the plugin) look similar in the
> log message panel. I have tried providing the inputs as QgsRasterLayer and
> as full filenames/paths, without success. I don't think the error is in the
> GRASS module, as it works fine when executed manually. Maybe someone
> encountered a similar problem?
>
> Thank you in advance,
>
> Sophie
>
>
>
>
>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] GRASS r.kappa not working in QGIS plugin

[Sophie Crommelinck]

Hello,


I am working on a QGIS plugin, that should use the module r.kappa from
GRASS. It looks like this in my plugin source code:

processing.run('grass7:r.kappa',
   {"classification": classificationLayer,
"reference": referenceLayer,
"title": 'ACCURACY ASSESSMENT',
"-h": False,
"-w": False,
"GRASS_REGION_CELLSIZE_PARAMETER": cellSize,
"GRASS_REGION_PARAMETER": None,
"output": outputFile})

As an error, I get a QgsProcessingException saying 'There were errors
executing the algorithm'.

If I run the same manually in QGIS via the toolbox, everything works fine.
Both calls of the module (manually and via the plugin) look similar in the
log message panel. I have tried providing the inputs as QgsRasterLayer and
as full filenames/paths, without success. I don't think the error is in the
GRASS module, as it works fine when executed manually. Maybe someone
encountered a similar problem?

Thank you in advance,

Sophie
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] GRASS processing modules in QGIS3

[Sophie Crommelinck]

Hi Nyall,

thanks a lot for fixing this!

Best,

Sophie

On 26 July 2018 at 00:26, Nyall Dawson  wrote:

> On Tue, 24 Jul 2018 at 21:54, Sophie Crommelinck
>  wrote:
> >
> > Hello,
> >
> > I have observed that some of the GRASS processing modules do not work
> (they run, but produce no result or error) in QGIS3. In particular, I am
> interested in using v.net.steiner, for which I was advised by Markus
> Neteler to open a bug report, which I did here: https://issues.qgis.org/
> issues/19186.
>
> This is now fixed in master and backported to 3.2, so will be fixed in
> the 3.2.2 release. You can grab a "nightly" release if you need the
> fix urgently.
>
> > It is unclear to me, if this also aims to make the GRASS processing
> modules work in QGIS3.
>
> Very much so! Just keep filing bug reports like you've done, and
> they'll eventually get fixed.
>
> Nyall
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] GRASS processing modules in QGIS3

[Sophie Crommelinck]

Hello,

I have observed that some of the GRASS processing modules do not work (they
run, but produce no result or error) in QGIS3. In particular, I am
interested in using v.net.steiner, for which I was advised by Markus
Neteler to open a bug report, which I did here:
https://issues.qgis.org/issues/19186. However, I don't know if anybody is
taking care of this. I found that  Radek Novotný  is working on improving
the GRASS integration in QGIS3 for a Google Summer of Code:
https://trac.osgeo.org/grass/wiki/GSoC/2018/IntegrationInQGIS3

It is unclear to me, if this also aims to make the GRASS processing modules
work in QGIS3. If yes, I would like to know, when the modules are intended
to be usable in QGIS. If no, I would like to know, if there is any other
development in this context currently in progress or planned. Maybe there
is also a better way to solve such questions than scanning through the
mailing list or writing to it?

Thank you in advance,

Sophie
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Unable to compile QGIS3 plugin

[Sophie Crommelinck]

Hey,

My problem is solved.

I just created a new plugin with the QGIS Plug-In Builder and ran in the
OSGeo4W Shell:

cd
C:\Users\xxx\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\myplugin
call qt5_env.bat
call py3_env.bat
pyrcc5 -o resources.py resources.qrc

This created the resources.py file and I could load the plugin without
crash in QGIS.

I am not sure what made QGIS crash when doing exactly this for the previous
plugin, on which I I tried your suggestions. I attached both the
resources.py and resources.qrc files of the previous plugin that caused the
QGIS crashes. I will now continue working with the newly created and
compiled one.

Thanks for your support,

Sophie






2018-03-23 11:54 GMT+01:00 Michel Stuyts <michel.stu...@edegem.be>:

> Sophie,
>
>
>
> This means  there is a probably something in your resources.py that
> causes the crash. Could you share that file and your resources.qrc that you
> used to generate resources.py?
>
>
>
>
>
> Michel
>
>
>
> *Van:* Sophie Crommelinck [mailto:sophie.crommeli...@gmail.com]
> *Verzonden:* vrijdag 23 maart 2018 11:48
> *Aan:* Michel Stuyts <michel.stu...@edegem.be>
> *CC:* qgis-developer@lists.osgeo.org
> *Onderwerp:* Re: [QGIS-Developer] Unable to compile QGIS3 plugin
>
>
>
> @ Michel: Does my answer make sense to you?
>
> Does anyone have an additional idea that I could try to compile the
> resource file successfully?
>
> Best,
>
> Sophie
>
>
>
> 2018-03-16 14:27 GMT+01:00 Sophie Crommelinck <
> sophie.crommeli...@gmail.com>:
>
> Hi,
>
> then again a resources.py file is created that makes QGIS3 crash.
>
> Best,
>
> Sophie
>
>
>
> 2018-03-16 12:24 GMT+01:00 Michel Stuyts <michel.stu...@edegem.be>:
>
> And if you first run:
>
> call C:\OSGeo4W64\bin\py3_env.bat
>
>
>
> and after that:
>
> C:\OSGeo4W64\apps\Python36\Scripts\pyrcc5 –o resources.py resources.qrc
>
>
>
>
>
> Michel
>
>
>
>
>
>
>
>
>
# -*- coding: utf-8 -*-

# Resource object code
#
# Created by: The Resource Compiler for PyQt5 (Qt v5.9.2)
#
# WARNING! All changes made in this file will be lost!

from PyQt5 import QtCore

qt_resource_data = b"\
\x00\x00\x04\x0a\
\x89\
\x50\x4e\x47\x0d\x0a\x1a\x0a\x00\x00\x00\x0d\x49\x48\x44\x52\x00\
\x00\x00\x17\x00\x00\x00\x18\x08\x06\x00\x00\x00\x11\x7c\x66\x75\
\x00\x00\x00\x01\x73\x52\x47\x42\x00\xae\xce\x1c\xe9\x00\x00\x00\
\x06\x62\x4b\x47\x44\x00\xff\x00\xff\x00\xff\xa0\xbd\xa7\x93\x00\
\x00\x00\x09\x70\x48\x59\x73\x00\x00\x0b\x13\x00\x00\x0b\x13\x01\
\x00\x9a\x9c\x18\x00\x00\x00\x07\x74\x49\x4d\x45\x07\xd9\x02\x15\
\x16\x11\x2c\x9d\x48\x83\xbb\x00\x00\x03\x8a\x49\x44\x41\x54\x48\
\xc7\xad\x95\x4b\x68\x5c\x55\x18\xc7\x7f\xe7\xdc\x7b\x67\xe6\xce\
\x4c\x66\x26\x49\xd3\x24\x26\xa6\xc6\xf8\x40\x21\xa5\x04\xb3\x28\
\xda\x98\x20\xa5\x0b\xad\x55\xa8\x2b\xc5\x50\x1f\xa0\x6e\x34\x2b\
\x45\x30\x14\x02\xba\x52\x69\x15\x17\x66\x63\x45\x97\x95\xa0\xad\
\x0b\xfb\xc0\x06\x25\xb6\x71\x61\x12\x41\x50\xdb\x2a\x21\xd1\xe2\
\x24\xf3\x9e\xc9\xcc\xbd\xe7\x1c\x17\x35\x43\x1e\x33\x21\xb6\xfd\
\x56\x87\xf3\x9d\xfb\xfb\x1e\xf7\xff\x9d\x23\x8c\x31\x43\x95\xf4\
\x85\x1e\x3f\x3b\x35\xac\xfd\xcc\x43\xdc\xa4\x49\x3b\xfe\x9d\x1d\
\xdb\x7b\x22\x90\x78\xf8\xb2\x28\xa7\xbe\x7d\xc1\x4b\x9d\x79\xdf\
\x18\x15\xe5\x16\x99\x10\x56\xde\x69\xdc\x3f\x22\xfd\xec\xd4\xf0\
\xad\x04\x03\x18\xa3\xa2\x7e\x76\x6a\x58\xde\x68\x2b\xb4\x36\xf8\
\xbe\xc6\x18\x53\xdb\xef\xe7\xfa\xec\xed\x67\x63\x10\x42\x00\xf0\
\xfb\xd5\x65\x2a\x15\x45\xc7\x6d\x0d\x00\xc4\xa2\xc1\xaa\x6f\x0d\
\x3e\x6c\xab\xc2\x1c\x56\xa4\x77\x4b\xb0\xf2\x35\x15\x5f\x21\x85\
\xe0\xc8\x6b\x5f\x92\x2d\x37\x33\x39\xf9\x03\x27\x8e\x1f\xa2\xf7\
\xbe\x9d\x04\x1c\x0b\x37\xe4\xac\xff\xa6\x30\x87\xbd\xba\x00\x6a\
\x06\x79\xe5\xf5\xaf\x89\xd9\x92\xc5\xcc\x0a\xd9\x7c\x19\xcf\xe9\
\xe2\xe4\xa9\x2f\x78\x7c\xff\x01\x72\x85\x0a\x2b\x65\x1f\xa5\x4c\
\xb5\xb2\x55\x16\x80\xbd\x31\xda\xda\x20\x1f\x7d\x3e\xcd\xc2\xfd\
\x59\xa6\x93\x39\x92\xd1\x22\xea\x9b\x16\xce\x9d\x3f\xce\xe0\x83\
\x03\x24\x82\x59\x3a\xdb\x7b\x88\xc7\x82\x68\x63\x58\xc9\xcc\x62\
\x8c\x21\x18\xb0\x6a\xc3\x37\x06\x49\x16\xff\x24\x6b\xa5\x49\xbb\
\x25\xbc\xa2\xa6\x21\xbb\x40\x7f\xdf\x00\x83\xbd\x01\x8e\x3c\xd5\
\x45\xd7\x8e\x6b\x9c\x9c\x98\x25\x1a\xb6\xe8\xbe\x3d\xc2\xdd\x77\
\x44\x48\xc4\x1c\x22\xe1\xeb\x58\x59\xaf\xcf\xd3\x33\x29\x2e\x34\
\x2d\x91\x93\x3e\xbe\x34\x78\x01\xc5\xe2\x61\xc5\xae\x72\x8e\x70\
\xc8\xc2\x0d\x5a\xbc\xf5\xee\x2f\x9c\xfa\x3e\x86\x69\x7a\x8e\xcf\
\x26\xe6\xf9\x63\xa1\x44\xa1\xa4\xd0\xda\x6c\x0d\x2f\x15\x7c\xb4\
\x67\x28\x59\x0a\xcf\xd6\x54\xe2\x06\x13\x87\x2b\x6f\x68\xa6\x27\
\xaf\x31\x32\x36\xc7\xb2\x7f\x17\xef\x7d\x7c\x8c\x33\x67\xcf\x12\
\x70\x24\x4a\x69\xd6\x6a\x46\xd6\xd3\x70\x72\xa9\x82\x67\x34\x45\
\xad\x28\xdb\x1a\x15\x34\x98\xff\x46\xed\xef\x37\x0d\x99\xbf\x4a\
\x3c\x30\x38\xc0\xc8\x4b\xaf\x92\x5a\

Re: [QGIS-Developer] Unable to compile QGIS3 plugin

[Sophie Crommelinck]

 I think my images broke while sending,

here they are again:

*Jürgen's suggestion:*

*Hannes' suggestion:*


*python-core.bat*


2018-03-16 10:45 GMT+01:00 Sophie Crommelinck <sophie.crommeli...@gmail.com>
:

> Hello Jürgen and Hannes,
>
> thanks for your support. I tried both suggestions, with little success.
>
> *Jürgen's suggestion:*
>
> This creates the resources.py file (attached). However, when I open QGIS3
> it crashes every time I reload the plugin (crash report attached).
>
> *Hannes' suggestion:*
>
> which results in the same as above. However, here I am not entirely sure
> if I followed the suggestion correctly as I go back to the plugin folder
> for compiling.
> Also, I wonder, why the result of calling python-qgis-dev.bat lists win32,
> while I have a win64 machine.
>
>
> I also tried changing the python path as suggested in the stack exchange
> question to Python36 in C:\OSGeo4W64\etc\ini\python-core without success
>
>
> Best,
>
> Sophie
>
>
>
>
>
> 2018-03-16 1:11 GMT+01:00 KOHLMANN Hannes <h.kohlm...@ove.at>:
>
>> Hey Sophie!
>>
>> There is one .bat file that does all the work of setting the Environment
>> variables properly: /osgeo4w_root/bin/python-qgis-dev.bat
>> Call that file in the console and in the same console cd to the directory
>> with the pyrcc.bat file (osgeo4w_root/apps/python36/scripts)
>>
>> Here is the link to a gis.stackexchange question concerning that:
>> https://gis.stackexchange.com/questions/260743/how-to-compil
>> e-qtdesigner-user-interface-ui-and-resource-qrc-files-
>> with-qg/264377#264377
>>
>> Good luck and compiling ;)
>>
>> Cheers,
>> Hannes
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Unable to compile QGIS3 plugin

[Sophie Crommelinck]

Hello Jürgen and Hannes,

thanks for your support. I tried both suggestions, with little success.

*Jürgen's suggestion:*

This creates the resources.py file (attached). However, when I open QGIS3
it crashes every time I reload the plugin (crash report attached).

*Hannes' suggestion:*

which results in the same as above. However, here I am not entirely sure if
I followed the suggestion correctly as I go back to the plugin folder for
compiling.
Also, I wonder, why the result of calling python-qgis-dev.bat lists win32,
while I have a win64 machine.


I also tried changing the python path as suggested in the stack exchange
question to Python36 in C:\OSGeo4W64\etc\ini\python-core without success


Best,

Sophie





2018-03-16 1:11 GMT+01:00 KOHLMANN Hannes :

> Hey Sophie!
>
> There is one .bat file that does all the work of setting the Environment
> variables properly: /osgeo4w_root/bin/python-qgis-dev.bat
> Call that file in the console and in the same console cd to the directory
> with the pyrcc.bat file (osgeo4w_root/apps/python36/scripts)
>
> Here is the link to a gis.stackexchange question concerning that:
> https://gis.stackexchange.com/questions/260743/how-to-
> compile-qtdesigner-user-interface-ui-and-resource-qrc-
> files-with-qg/264377#264377
>
> Good luck and compiling ;)
>
> Cheers,
> Hannes
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
# -*- coding: utf-8 -*-

# Resource object code
#
# Created by: The Resource Compiler for PyQt5 (Qt v5.9.2)
#
# WARNING! All changes made in this file will be lost!

from PyQt5 import QtCore

qt_resource_data = b"\
\x00\x00\x04\x0a\
\x89\
\x50\x4e\x47\x0d\x0a\x1a\x0a\x00\x00\x00\x0d\x49\x48\x44\x52\x00\
\x00\x00\x17\x00\x00\x00\x18\x08\x06\x00\x00\x00\x11\x7c\x66\x75\
\x00\x00\x00\x01\x73\x52\x47\x42\x00\xae\xce\x1c\xe9\x00\x00\x00\
\x06\x62\x4b\x47\x44\x00\xff\x00\xff\x00\xff\xa0\xbd\xa7\x93\x00\
\x00\x00\x09\x70\x48\x59\x73\x00\x00\x0b\x13\x00\x00\x0b\x13\x01\
\x00\x9a\x9c\x18\x00\x00\x00\x07\x74\x49\x4d\x45\x07\xd9\x02\x15\
\x16\x11\x2c\x9d\x48\x83\xbb\x00\x00\x03\x8a\x49\x44\x41\x54\x48\
\xc7\xad\x95\x4b\x68\x5c\x55\x18\xc7\x7f\xe7\xdc\x7b\x67\xe6\xce\
\x4c\x66\x26\x49\xd3\x24\x26\xa6\xc6\xf8\x40\x21\xa5\x04\xb3\x28\
\xda\x98\x20\xa5\x0b\xad\x55\xa8\x2b\xc5\x50\x1f\xa0\x6e\x34\x2b\
\x45\x30\x14\x02\xba\x52\x69\x15\x17\x66\x63\x45\x97\x95\xa0\xad\
\x0b\xfb\xc0\x06\x25\xb6\x71\x61\x12\x41\x50\xdb\x2a\x21\xd1\xe2\
\x24\xf3\x9e\xc9\xcc\xbd\xe7\x1c\x17\x35\x43\x1e\x33\x21\xb6\xfd\
\x56\x87\xf3\x9d\xfb\xfb\x1e\xf7\xff\x9d\x23\x8c\x31\x43\x95\xf4\
\x85\x1e\x3f\x3b\x35\xac\xfd\xcc\x43\xdc\xa4\x49\x3b\xfe\x9d\x1d\
\xdb\x7b\x22\x90\x78\xf8\xb2\x28\xa7\xbe\x7d\xc1\x4b\x9d\x79\xdf\
\x18\x15\xe5\x16\x99\x10\x56\xde\x69\xdc\x3f\x22\xfd\xec\xd4\xf0\
\xad\x04\x03\x18\xa3\xa2\x7e\x76\x6a\x58\xde\x68\x2b\xb4\x36\xf8\
\xbe\xc6\x18\x53\xdb\xef\xe7\xfa\xec\xed\x67\x63\x10\x42\x00\xf0\
\xfb\xd5\x65\x2a\x15\x45\xc7\x6d\x0d\x00\xc4\xa2\xc1\xaa\x6f\x0d\
\x3e\x6c\xab\xc2\x1c\x56\xa4\x77\x4b\xb0\xf2\x35\x15\x5f\x21\x85\
\xe0\xc8\x6b\x5f\x92\x2d\x37\x33\x39\xf9\x03\x27\x8e\x1f\xa2\xf7\
\xbe\x9d\x04\x1c\x0b\x37\xe4\xac\xff\xa6\x30\x87\xbd\xba\x00\x6a\
\x06\x79\xe5\xf5\xaf\x89\xd9\x92\xc5\xcc\x0a\xd9\x7c\x19\xcf\xe9\
\xe2\xe4\xa9\x2f\x78\x7c\xff\x01\x72\x85\x0a\x2b\x65\x1f\xa5\x4c\
\xb5\xb2\x55\x16\x80\xbd\x31\xda\xda\x20\x1f\x7d\x3e\xcd\xc2\xfd\
\x59\xa6\x93\x39\x92\xd1\x22\xea\x9b\x16\xce\x9d\x3f\xce\xe0\x83\
\x03\x24\x82\x59\x3a\xdb\x7b\x88\xc7\x82\x68\x63\x58\xc9\xcc\x62\
\x8c\x21\x18\xb0\x6a\xc3\x37\x06\x49\x16\xff\x24\x6b\xa5\x49\xbb\
\x25\xbc\xa2\xa6\x21\xbb\x40\x7f\xdf\x00\x83\xbd\x01\x8e\x3c\xd5\
\x45\xd7\x8e\x6b\x9c\x9c\x98\x25\x1a\xb6\xe8\xbe\x3d\xc2\xdd\x77\
\x44\x48\xc4\x1c\x22\xe1\xeb\x58\x59\xaf\xcf\xd3\x33\x29\x2e\x34\
\x2d\x91\x93\x3e\xbe\x34\x78\x01\xc5\xe2\x61\xc5\xae\x72\x8e\x70\
\xc8\xc2\x0d\x5a\xbc\xf5\xee\x2f\x9c\xfa\x3e\x86\x69\x7a\x8e\xcf\
\x26\xe6\xf9\x63\xa1\x44\xa1\xa4\xd0\xda\x6c\x0d\x2f\x15\x7c\xb4\
\x67\x28\x59\x0a\xcf\xd6\x54\xe2\x06\x13\x87\x2b\x6f\x68\xa6\x27\
\xaf\x31\x32\x36\xc7\xb2\x7f\x17\xef\x7d\x7c\x8c\x33\x67\xcf\x12\
\x70\x24\x4a\x69\xd6\x6a\x46\xd6\xd3\x70\x72\xa9\x82\x67\x34\x45\
\xad\x28\xdb\x1a\x15\x34\x98\xff\x46\xed\xef\x37\x0d\x99\xbf\x4a\
\x3c\x30\x38\xc0\xc8\x4b\xaf\x92\x5a\x9c\xe2\xe0\x23\x6d\x74\xb4\
\xba\x84\x5d\x0b\x29\x45\x7d\xb8\x94\x82\x96\xb6\x10\xf3\xc5\x12\
\x2a\xef\x53\x11\x1a\x63\xad\x3f\x93\x19\x85\xf1\xb1\x77\x58\x5a\
\xf8\x99\x97\x9f\xe9\xa6\x75\x47\x90\xc6\xb8\x43\xd8\xb5\xb6\xce\
\xfc\xfa\xfd\x00\xfb\x3e\xf4\xc8\x05\x35\xba\x5e\xeb\x46\x21\xf9\
\xcf\x0a\xa9\x8c\x87\xe3\x48\xdc\x90\xb5\x6e\x98\x6a\xaa\x65\xf2\
\x52\x92\x43\x2f\x5e\xc2\x8c\x02\x1a\x10\xf5\x07\xac\xc3\x75\x70\
\x83\x92\x80\xb3\xf9\xd0\x26\xf8\x8f\xb3\x29\xc6\x3e\xb8\x8c\x19\

[QGIS-Developer] Unable to compile QGIS3 plugin

[Sophie Crommelinck]

Hello,

I would like to make a QGIS3 plugin. I have created the template with the
'Plugin Builder', which creates the plugin folder in
C:\Users\xxx\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins.
When I then open the OSGeo4WShell, navigate to the folder and enter 'make',
the following error occurs:

When running 'pyrcc5 -o resources.py resources.qrc' (which should do the
same) the following error occurs:


I thought it might have something to do with Python3 not properly installed
or connected to QGIS3 and reinstalled QGIS and Python with the OSGeo4W
installer without success. I am a little confused by the many pythons
installed somewhere from OSGeo4W and my local Python 2 and 3. I will try
reinstalling all parts to get a better feeling for what comes from where.

Any further idea on what I could try?

Thanks in advance,

Sophie
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Plugin not in repository

[Sophie Crommelinck]

Oh my mistake, I haven't seen that open issue.
I solved it by deleting all .pyc files and closed the ticket.

Best,

Sophie

On 31 May 2017 at 12:02, Paolo Cavallini <cavall...@faunalia.it> wrote:

> Hi Sphie,
>
> Il 31/05/2017 11:51, Sophie Crommelinck ha scritto:
>
> > about 3-4 weeks ago, I uploaded a QGIS Plugin called BoundaryDelineation
> > to the QGIS Plugin Repository via http://plugins.qgis.org/plugins/add/
> > <http://plugins.qgis.org/plugins/add/>.
> >
> > I haven't heard anything about its acceptance or refusal.
>
> I opened a ticket:
> https://github.com/SCrommelinck/BoundaryDelineation/issues
> and received no reply. I'll be glad of publishing it once issues are fixed.
> 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: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] QGIS Plugin not in repository

[Sophie Crommelinck]

Hello,

about 3-4 weeks ago, I uploaded a QGIS Plugin called BoundaryDelineation to
the QGIS Plugin Repository via http://plugins.qgis.org/plugins/add/.

I haven't heard anything about its acceptance or refusal.

I am not sure if this mailing list is the right place to ask: how can I
find out more about the acceptance status of my plugin?

Best,

Sophie Crommelinck
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer