[QGIS-Developer] Processing plugin algorithm slows down in graphical modeler

[Clemens Raffler]

Dear QGIS Devs,

Recently, I received two messages from users concerning the speed of 
processing algorithms which are implemented in the QNEAT3 plugin. More 
specifically, they report that the execution time of algorithms slow 
down up to 10 times when the algorithm is used in the graphical modeler 
compared to manual execution from the processing toolbox (used 
algorithm: OD Matrix from Layers as Lines (m:n)). I link the ticket from 
the QNEAT3 repository here for reference: 
https://github.com/root676/QNEAT3/issues/21


I would like to identify the cause of this problem because on the first 
look I can't relate it to any implementation flaws on the plugin side. 
Has anyone else experienced this problem with other processing plugins 
or core algorithms? I didn't have time yet to check if core algorithms 
are affected too. Could it be some kind of bug related to the graphical 
modeler? Do you have any hints what could cause this problem on the 
plugin side so I can fix it? Tanks in advance!


Best regards,
Clemens

___
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] Plugin [1786] Three-D Change Detection approval notification.

[noreply]

Plugin Three-D Change Detection approval by pcav.
The plugin version "[1786] Three-D Change Detection 0.1 Experimental" is now 
approved
Link: http://plugins.qgis.org/plugins/Three_D_Change_Detection-master/
___
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] Pull request #30647 - review / discuss during hackfest?

[Áron Gergely]

Hello Nyall and all contributors,

I while ago I made a PR to improve on the 'world' easter egg (have 
better data under it),

as well as adding two more layers:

 - province/state boundaries
 - disputed borders

Those would not be added to the canvas when invoking the 'world' easter 
egg but could be used in the CRS selection window and as default layer 
in a project template.


Nyall was one of the people who said he would be happy to see this merged,
so he could work on a few ideas around it (mainly what I mentioned 
above: CRS selection window and project template) before the feature 
freeze on August 30th.


Here is the PR:
https://github.com/qgis/QGIS/pull/30647

I know that there are mixed opinions about shipping data with QGIS -
therefore I thought it would be handy to discuss and decide during the 
hackfest whether this PR should be merged or not as it is.


I also have my own concerns, mainly about starting to manage data, and 
their processing pipelines which I think is not a good idea, (discussion 
on the PR is starting to head in that direction now)


Id be glad for to hear your thoughts on this.

And if you are here in Bucharest too, I would be happy to sit together 
and have a chat about it;
can also sum up the story if you want to have a quick understanding 
without reading all comments / commit messages.


Thanks,

Best regards,
Aron



___
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] Issue priorization for bugfixing: go flag your favorite issues

[Matthias Kuhn]

Hi

On 8/24/19 10:39 AM, Giovanni Manghi wrote:
Thanks Matthias, thanks for this, as of course it *is* the eright 
thing to do,


I only hope that next time this will be at least announced a little 
bit more in advance other than a Saturday morning, during August, at 
the start of the dev meeting.


I did in the past several "priority lists" and it takes a while to 
decide, togther with you developers, what is worth prioritizing and 
what not.


Please continue this list. I see the two things as complementary and 
wouldn't want to sacrifice one for the other! I even think that if the 
thumbs up work nicely you can take it as input for your list too.




Speaking  about that, and just to clear air about a thread on a 
similar subject in the PSC list:


There is no "paranoia" (I kindly ask stop using this word around this 
matter) about/around regressions. Regressions *always break someone 
workflow*, and it is not about you or me to decide if not fixing them 
(who are me/you to decide that someone else workflow is not 
important?). They should be always fixed, at least in our LTR release 
(and also thanks to Sandro Santilli for basically saying the same thing).


As someone else said is not true that a "bug is a bug": while 
certainly there are issues that is not easy to classify if they impact 
a lot or not, the vast majoity is easy to to say if they are important 
or not. Do not confound the fact that maybe a ticket do not gets much 
attention or comments: just a few people actually do that (file 
tickets, comment), part of them were also educated to have faith and 
expect fixes (of important issues) at least in the upcoming LTR 
releases, sometimes just to wait in vain (just because the the paid 
bug fixing effort do not comes with any sort of priority list).


Can we move this discussion to a different thread?

I fear this does not help to bring the discussion here forward.



have fun there


Are you not coming?

Thanks anyway, we'll send some pictures :)

Matthias

___
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] Plugin [1794] LandXML2QGIS approval notification.

[noreply]

Plugin LandXML2QGIS approval by pcav.
The plugin version "[1794] LandXML2QGIS 0.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/landxml2qgis/
___
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] Plugin [1790] Easy Processing Tool approval notification.

[noreply]

Plugin Easy Processing Tool approval by pcav.
The plugin version "[1790] Easy Processing Tool 0.1" is now approved
Link: http://plugins.qgis.org/plugins/easy_processing_tool/
___
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] Issue priorization for bugfixing: go flag your favorite issues

[Paolo Cavallini]

Hi Matthias,

On 24/08/19 10:06, Matthias Kuhn wrote:

> I think this is mainly a point of communication.
> 
> If explained well as an "indication" and not as a "guarantee" - online
> and live while teaching - I think we'll get the message out.

agreed, but I'm still unsure we'll be able to convey the right message.
I have see social networks taking strange directions easily, regardless
of the efforts by the transmitter. Of coourse, GH has already a bit of a
barrier for casual users, so we might be sheltered.

> It's an interesting idea, but I am afraid we'll put the project in a bad
> position. In particular, it brings the project into a situation where it
> acts as a service provider proxy,

agreed, this is a real issue

> where it's easy to interpret the
> project as the one to take responsibility for those bugs being fixed
> (just like you wrote above "why the hell has issue X not been solved
> yet", but with money involved this time), and last, it's hard to come up
> with a good process (should there be estimates first? or money first and
> when there's enough someone picks the issue?).

again, it's a matter of communication ;)
I don't think we should expect for the users to pay fully for the fix,
but rather use the money donated as an honest indication of interest,
more reliable than a cheap click.
this approach wouold also alleviate or solve the previous point.

Cheers.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
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] GitHub Issue Tracker Triage Members

[Paolo Cavallini]

good idea, +1
thanks

On 24/08/19 11:19, Tim Sutton wrote:
> Hi all
> 
> Last night we were discussing a bit the GitHub tracker. One thing we
> don’t have is a way for non-core developers to self assign issues. Or
> for example for me to assign a ticket to someone from my company to work
> on. I understand that developers do not want random people to assign
> tickets to them but we do need a way for assignments to be managed, and
> generally to have more people able to triage tickets.
> 
> Our proposal is to liberally assign triage permissions to anyone who
> requests it by adding them to this group (which has no commit rights,
> only triage rights):
> 
> https://github.com/orgs/qgis/teams/community/members
> 
> Members of that group can then be assigned tickets or self assign
> tickets. If anyone misbehaves in that group we can simply remove them
> from the group again.
> 
> Regards
> 
> Tim
> —
> 
> 
> 
> 
> 
> 
> 
> 
> *Tim Sutton*
> 
> *Co-founder:* Kartoza
> *Ex Project chair:* QGIS.org 
> 
> Visit http://kartoza.com  to find out about open
> source:
> 
> Desktop GIS programming services
> Geospatial web development
> GIS Training
> Consulting Services
> 
> *Skype*: timlinux 
> *IRC:* timlinux on #qgis at freenode.net 
> 
> I'd love to connect. Here's my calendar link
>  to make finding time easy.
> 
> 
> ___
> 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
> 

-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
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] Issue priorization for bugfixing: go flag your favorite issues

[Giovanni Manghi]

Hi Nyall,


Putting aside the rest of the conversation regarding regressions for
> now, something I'd like to see clarified is what exactly classifies as
> a regression?
>


in my mind, a regression is some functionality that worked and does not
work anymore. It also does not have an acceptable workaround (or
alternative path to achieve the same result)


- clicking the browse button in the file attachment widgets crashes
> qgis: regression
>

clearly a regression, and it does not matter that is an upstream problem.
We knew about it for about a year and only took action (removing the
button!) only now.
This particular regression should have been handled much more gracefully
than we did.



> - a project which depends on postgres foreign data wrappers to
> evaluate a default field value by performing an aggregate on a related
> layer from the current project breaking in a future release: not a
> regression
>

clear example of something that likely is not used by many, unlike the
previous example, so something that can be discussed if is urgent to fix or
even a won't fix.


In the real of "technically not a regression, but pretty bad one" I could
make a recent  example:

https://github.com/qgis/QGIS/issues/31251

which is clearly something that was overlooked when re-writing/re-designing
that edit tools

-- G --
___
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] GitHub Issue Tracker Triage Members

[Tim Sutton]

Hi all

Last night we were discussing a bit the GitHub tracker. One thing we don’t have 
is a way for non-core developers to self assign issues. Or for example for me 
to assign a ticket to someone from my company to work on. I understand that 
developers do not want random people to assign tickets to them but we do need a 
way for assignments to be managed, and generally to have more people able to 
triage tickets.

Our proposal is to liberally assign triage permissions to anyone who requests 
it by adding them to this group (which has no commit rights, only triage 
rights):

https://github.com/orgs/qgis/teams/community/members

Members of that group can then be assigned tickets or self assign tickets. If 
anyone misbehaves in that group we can simply remove them from the group again.

Regards

Tim
—









Tim Sutton

Co-founder: Kartoza
Ex Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

I'd love to connect. Here's my calendar link  to 
make finding time easy.

___
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] Plugin [1376] GPX Segment Importer approval notification.

[noreply]

Plugin GPX Segment Importer approval by pcav.
The plugin version "[1376] GPX Segment Importer 2.4" is now approved
Link: http://plugins.qgis.org/plugins/GpxSegmentImporter/
___
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] Plugin [1456] EO Time Series Viewer approval notification.

[noreply]

Plugin EO Time Series Viewer approval by pcav.
The plugin version "[1456] EO Time Series Viewer 1.7.20190821T1246.master" is 
now approved
Link: http://plugins.qgis.org/plugins/timeseriesviewerplugin/
___
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] Issue priorization for bugfixing: go flag your favorite issues

[Nyall Dawson]

On Sat, 24 Aug 2019 at 18:40, Giovanni Manghi  wrote:

> As someone else said is not true that a "bug is a bug": while certainly there 
> are issues that is not easy to classify if they impact a lot or not, the vast 
> majoity is easy to to say if they are important or not. Do not confound the 
> fact that maybe a ticket do not gets much attention or comments: just a few 
> people actually do that (file tickets, comment), part of them were also 
> educated to have faith and expect fixes (of important issues) at least in the 
> upcoming LTR releases, sometimes just to wait in vain (just because the the 
> paid bug fixing effort do not comes with any sort of priority list).

Putting aside the rest of the conversation regarding regressions for
now, something I'd like to see clarified is what exactly classifies as
a regression? There's SO much users can potentially do in QGIS which
goes far beyond the original design of any particular feature, and
which works by sheer chance alone. If this breaks in a future release,
is it really a regression? To use a ridiculous example, if I wrote a
custom script which relied on hooking into QGIS dialog's widgets via
raw PyQT api, and then that dialog is rearranged in future and the
button I was tapping into is removed -- is this really a regression?
I'd argue strongly not, and that all along I was playing it dangerous
by relying on unintentional behaviour.

So maybe something explicit like: "a regression is a clearly
documented feature (or a feature with pending documentation ticket),
or a feature covered by existing units tests, which breaks". This
means:
- clicking the browse button in the file attachment widgets crashes
qgis: regression
- a project which depends on postgres foreign data wrappers to
evaluate a default field value by performing an aggregate on a related
layer from the current project breaking in a future release: not a
regression

Nyall

>
> have fun there
>
> -- G --
>
>
>
>
>>
>> Yesterday at a dinner with many well known friendly faces, a discussion
>> started about the priorization of issues.
>>
>> One of the main problems when deciding which issues to tackle is, that a
>> developer perspective often differs from the one from the average user
>> perspective.
>>
>> So we thought it might be a good idea to start giving our users a bigger
>> voice in how bugs are prioritized - and how the projects funds are spent
>> - by giving the developers more information about the "impact footprint"
>> of issue reports.
>>
>> *In short: if you particularly hate an issue (or two or three) go to
>> this issue on github and just give the first post of it a thumbs up.*
>>
>> The following link will then show the leaderboard of annoying things
>>
>> https://github.com/qgis/QGIS/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc+label%3ABug
>>
>> While there is no guarantee that these bugs really will be solved first
>> (there are a couple of other things also to take into account, like a
>> well defined solution being at hand) this should give us a much better
>> (democratic) idea of the often-cited user expectation.
>>
>> Thanks for reading
>>
>> Matthias
>
> ___
> 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] Plugin [1682] Group Transparency approval notification.

[noreply]

Plugin Group Transparency approval by pcav.
The plugin version "[1682] Group Transparency 0.2" is now approved
Link: http://plugins.qgis.org/plugins/group_transparency/
___
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] Plugin [922] CKAN-Browser approval notification.

[noreply]

Plugin CKAN-Browser approval by pcav.
The plugin version "[922] CKAN-Browser 0.4.0" is now approved
Link: http://plugins.qgis.org/plugins/CKANBrowser/
___
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] DBManager TopoViewer silently fails to load edge/node layers

[Sandro Santilli]

On Sat, Aug 24, 2019 at 08:48:01AM +0200, Paolo Cavallini wrote:
> Hi all,
> any news about this? I believe it's a bad regression.
> Sandro, did you open a ticket? Any idea about when this popped up?

I actually fixed it in master branch
(ae0721891b6b521ee0d0a3dd8b8a8b092b017554)
and backported it to 3.4 (f3ce1b44d734a4a3c08d01be04d39779ef001c9a)
and 3.8 (6cbfb360b47580bd854283b5c5cad91b3367ac8c) branches.

Thanks for the followup!

NOTE: next issue I have is a crash on startup, see
  https://github.com/qgis/QGIS/issues/31350

--strk;
___
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] Issue priorization for bugfixing: go flag your favorite issues

[Giovanni Manghi]

> I would say we better leave this role to the developers
>

what role, to choose what to fix? if yes then... no, not completely at
least.

-- G --
___
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] Issue priorization for bugfixing: go flag your favorite issues

[Giovanni Manghi]

Thanks Matthias, thanks for this, as of course it *is* the eright thing to
do,

I only hope that next time this will be at least announced a little bit
more in advance other than a Saturday morning, during August, at the start
of the dev meeting.

I did in the past several "priority lists" and it takes a while to decide,
togther with you developers, what is worth prioritizing and what not.

Speaking  about that, and just to clear air about a thread on a similar
subject in the PSC list:

There is no "paranoia" (I kindly ask stop using this word around this
matter) about/around regressions. Regressions *always break someone
workflow*, and it is not about you or me to decide if not fixing them (who
are me/you to decide that someone else workflow is not important?). They
should be always fixed, at least in our LTR release (and also thanks to
Sandro Santilli for basically saying the same thing).

As someone else said is not true that a "bug is a bug": while certainly
there are issues that is not easy to classify if they impact a lot or not,
the vast majoity is easy to to say if they are important or not. Do not
confound the fact that maybe a ticket do not gets much attention or
comments: just a few people actually do that (file tickets, comment), part
of them were also educated to have faith and expect fixes (of important
issues) at least in the upcoming LTR releases, sometimes just to wait in
vain (just because the the paid bug fixing effort do not comes with any
sort of priority list).

have fun there

-- G --





> Yesterday at a dinner with many well known friendly faces, a discussion
> started about the priorization of issues.
>
> One of the main problems when deciding which issues to tackle is, that a
> developer perspective often differs from the one from the average user
> perspective.
>
> So we thought it might be a good idea to start giving our users a bigger
> voice in how bugs are prioritized - and how the projects funds are spent
> - by giving the developers more information about the "impact footprint"
> of issue reports.
>
> *In short: if you particularly hate an issue (or two or three) go to
> this issue on github and just give the first post of it a thumbs up****.*
>
> The following link will then show the leaderboard of annoying things
>
>
> https://github.com/qgis/QGIS/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc+label%3ABug
>
> While there is no guarantee that these bugs really will be solved first
> (there are a couple of other things also to take into account, like a
> well defined solution being at hand) this should give us a much better
> (democratic) idea of the often-cited user expectation.
>
> Thanks for reading
>
> Matthias
>
___
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] Issue priorization for bugfixing: go flag your favorite issues

[Matthias Kuhn]

Hi Paolo

On 8/24/19 9:21 AM, Paolo Cavallini wrote:

Hi Matthias,

On 24/08/19 09:16, Matthias Kuhn wrote:

Yesterday at a dinner with many well known friendly faces, a discussion
started about the priorization of issues.

One of the main problems when deciding which issues to tackle is, that a
developer perspective often differs from the one from the average user
perspective.

So we thought it might be a good idea to start giving our users a bigger
voice in how bugs are prioritized - and how the projects funds are spent
- by giving the developers more information about the "impact footprint"
of issue reports.

*In short: if you particularly hate an issue (or two or three) go to
this issue on github and just give the first post of it a thumbs up****.*

The following link will then show the leaderboard of annoying things

https://github.com/qgis/QGIS/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc+label%3ABug

While there is no guarantee that these bugs really will be solved first
(there are a couple of other things also to take into account, like a
well defined solution being at hand) this should give us a much better
(democratic) idea of the often-cited user expectation.

I find the idea interesting and positive, but I see a couple of problems:
* this may generate frustration among users (why the hell an issue with
tens of "likes" has not been solved already? You crappy developers don't
listen to us!)


I think this is mainly a point of communication.

If explained well as an "indication" and not as a "guarantee" - online 
and live while teaching - I think we'll get the message out.


And, even if not fixed it will help us triage the important ones and add 
status information (for those who read carefully).



* thumbs up is cheap, and does not necessarily reflect real interest.
I would be more in favour of an honest expression of interest: I put my
money where my mouth is. Can we have a mechanism of donations attached
to a articular ticket?


It's an interesting idea, but I am afraid we'll put the project in a bad 
position. In particular, it brings the project into a situation where it 
acts as a service provider proxy, where it's easy to interpret the 
project as the one to take responsibility for those bugs being fixed 
(just like you wrote above "why the hell has issue X not been solved 
yet", but with money involved this time), and last, it's hard to come up 
with a good process (should there be estimates first? or money first and 
when there's enough someone picks the issue?).


I would say we better leave this role to the developers and have 
earmarked fundings for well defined projects (like the mac builds) or by 
directly advertising current crowdfunding projects from developers.


Cheers


Cheers.


___
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] Plugin [1633] ArcGIS ImageServer Connector approval notification.

[noreply]

Plugin ArcGIS ImageServer Connector approval by pcav.
The plugin version "[1633] ArcGIS ImageServer Connector 2.1.1" is now approved
Link: http://plugins.qgis.org/plugins/ImageServerConnector/
___
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] Plugin [1438] Road Inspection Viewer approval notification.

[noreply]

Plugin Road Inspection Viewer approval by pcav.
The plugin version "[1438] Road Inspection Viewer 1.2.2" is now approved
Link: http://plugins.qgis.org/plugins/road_inspection_viewer/
___
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] Plugin [1195] MPA Post-Hoc Accounting approval notification.

[noreply]

Plugin MPA Post-Hoc Accounting approval by pcav.
The plugin version "[1195] MPA Post-Hoc Accounting 0.22 Experimental" is now 
approved
Link: http://plugins.qgis.org/plugins/MPAPostHocAccounting/
___
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] Plugin [1659] ORS Tools approval notification.

[noreply]

Plugin ORS Tools approval by pcav.
The plugin version "[1659] ORS Tools 1.1.0" is now approved
Link: http://plugins.qgis.org/plugins/ORStools/
___
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] Plugin [1037] Kortforsyningen approval notification.

[noreply]

Plugin Kortforsyningen approval by pcav.
The plugin version "[1037] Kortforsyningen 2.7" is now approved
Link: http://plugins.qgis.org/plugins/Kortforsyningen/
___
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] Plugin [1659] ORS Tools approval notification.

[noreply]

Plugin ORS Tools approval by pcav.
The plugin version "[1659] ORS Tools 1.1.1" is now approved
Link: http://plugins.qgis.org/plugins/ORStools/
___
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] Plugin [1350] Mascaret approval notification.

[noreply]

Plugin Mascaret approval by pcav.
The plugin version "[1350] Mascaret 1.1.0 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/Mascaret/
___
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] Plugin [1350] Mascaret approval notification.

[noreply]

Plugin Mascaret approval by pcav.
The plugin version "[1350] Mascaret 1.0.3" is now approved
Link: http://plugins.qgis.org/plugins/Mascaret/
___
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] Plugin [92] Midvatten approval notification.

[noreply]

Plugin Midvatten approval by pcav.
The plugin version "[92] Midvatten 1.6.1" is now approved
Link: http://plugins.qgis.org/plugins/midvatten/
___
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] Please approve my HCMGIS Plugin new version

[Paolo Cavallini]

Done, thanks for your patience.
Cheers.

On 21/08/19 06:14, Thắng Quách Đồng wrote:
> Dear Approval Team!
> I have been uploaded new version of HCMGIS Plugin for a while but
> received no approval
> So could u please to check and approve my new HCMGIS plugin
> https://plugins.qgis.org/plugins/HCMGIS/ 
> Thanks and best regards!
> 
> -- 
> Quach Dong Thang
> Head - Technology Development Division, HCMC GIS Center, DOST
> Mobile: +84933908919
> Homepage: https://hcmgis.vn
> 
> ___
> 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
> 

-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
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] Issue priorization for bugfixing: go flag your favorite issues

[Paolo Cavallini]

Hi Matthias,

On 24/08/19 09:16, Matthias Kuhn wrote:
> Yesterday at a dinner with many well known friendly faces, a discussion
> started about the priorization of issues.
> 
> One of the main problems when deciding which issues to tackle is, that a
> developer perspective often differs from the one from the average user
> perspective.
> 
> So we thought it might be a good idea to start giving our users a bigger
> voice in how bugs are prioritized - and how the projects funds are spent
> - by giving the developers more information about the "impact footprint"
> of issue reports.
> 
> *In short: if you particularly hate an issue (or two or three) go to
> this issue on github and just give the first post of it a thumbs up****.*
> 
> The following link will then show the leaderboard of annoying things
> 
> https://github.com/qgis/QGIS/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc+label%3ABug
> 
> While there is no guarantee that these bugs really will be solved first
> (there are a couple of other things also to take into account, like a
> well defined solution being at hand) this should give us a much better
> (democratic) idea of the often-cited user expectation.

I find the idea interesting and positive, but I see a couple of problems:
* this may generate frustration among users (why the hell an issue with
tens of "likes" has not been solved already? You crappy developers don't
listen to us!)
* thumbs up is cheap, and does not necessarily reflect real interest.
I would be more in favour of an honest expression of interest: I put my
money where my mouth is. Can we have a mechanism of donations attached
to a articular ticket?
Cheers.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
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] Issue priorization for bugfixing: go flag your favorite issues

[Matthias Kuhn]

Yesterday at a dinner with many well known friendly faces, a discussion 
started about the priorization of issues.


One of the main problems when deciding which issues to tackle is, that a 
developer perspective often differs from the one from the average user 
perspective.


So we thought it might be a good idea to start giving our users a bigger 
voice in how bugs are prioritized - and how the projects funds are spent 
- by giving the developers more information about the "impact footprint" 
of issue reports.


*In short: if you particularly hate an issue (or two or three) go to 
this issue on github and just give the first post of it a thumbs up****.*


The following link will then show the leaderboard of annoying things

https://github.com/qgis/QGIS/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc+label%3ABug

While there is no guarantee that these bugs really will be solved first 
(there are a couple of other things also to take into account, like a 
well defined solution being at hand) this should give us a much better 
(democratic) idea of the often-cited user expectation.


Thanks for reading

Matthias

___
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] Plugin [1791] wpgpDatasets approval notification.

[noreply]

Plugin wpgpDatasets approval by zimbogisgeek.
The plugin version "[1791] wpgpDatasets 0.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/wpgpDatasets/
___
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] Plugin [1780] Hydro Generator approval notification.

[noreply]

Plugin Hydro Generator approval by zimbogisgeek.
The plugin version "[1780] Hydro Generator 0.3 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/hydro_generator/
___
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] Plugin [1780] Hydro Generator approval notification.

[noreply]

Plugin Hydro Generator approval by zimbogisgeek.
The plugin version "[1780] Hydro Generator 0.2 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/hydro_generator/
___
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] Plugin [1779] Geometry Generator approval notification.

[noreply]

Plugin Geometry Generator approval by zimbogisgeek.
The plugin version "[1779] Geometry Generator 0.3 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/geometry_generator/
___
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] DBManager TopoViewer silently fails to load edge/node layers

[Paolo Cavallini]

Hi all,
any news about this? I believe it's a bad regression.
Sandro, did you open a ticket? Any idea about when this popped up?
Cheers.

On 21/08/19 15:32, Sandro Santilli wrote:
> It's been a long time but I just clean-built QGIS from master branch
> (commit 8145f8f9276bb0b71ffb076e9b4115d800c41747) to find that the
> TopoViewer of DBManager is failing to provide proper layers.
> 
> The TopoViewer creates a layer tree composed by a top group
> named after the target topology and 3 sub-groups:
> 
>- Faces
>  - face_mbr
>  - face
>  - face_seed
>- Nodes
>  - node
>  - node_id
>- Edges
>  - edge
>  - directed_edge
>  - edge_id
> 
> Of the 8 layers, only the ones under "Faces" work, while the others
> not only don't show anything but do not even present the user with
> a right-click->Properties (or double-click) menu to inspect
> properties. The right-click menu shows only a few entries
> (copy layer, rename layer, duplicate layer) and show no geometry type.
> 
> Do you have any idea what could cause this ?
> 
> The logs, for one of the layers, report:
> 
>   src/providers/postgres/qgspostgresprovider.cpp:100 : 
> (QgsPostgresProvider) [3ms] URI: dbname='p' port=5432 key='edge_id' 
> estimatedmetadata=true srid=4167 type=LineString checkPrimaryKeyUnicity='1' 
> table="test0"."edge_data" (geom) sql=
>   src/providers/postgres/qgspostgresprovider.cpp:149 : 
> (QgsPostgresProvider) [0ms] Connection info is dbname='p' port=5432
>   src/providers/postgres/qgspostgresprovider.cpp:150 : 
> (QgsPostgresProvider) [0ms] Geometry column is: geom
>   src/providers/postgres/qgspostgresprovider.cpp:151 : 
> (QgsPostgresProvider) [0ms] Schema is: test0
>   src/providers/postgres/qgspostgresprovider.cpp:152 : 
> (QgsPostgresProvider) [0ms] Table name is: edge_data
>   src/providers/postgres/qgspostgresprovider.cpp:153 : 
> (QgsPostgresProvider) [1ms] Query is: "test0"."edge_data"
>   src/providers/postgres/qgspostgresprovider.cpp:154 : 
> (QgsPostgresProvider) [0ms] Where clause is:
>   src/providers/postgres/qgspostgresconn.cpp:168 : (connectDb) [0ms] 
> Using cached connection for dbname='p' port=5432
>   src/providers/postgres/qgspostgresprovider.cpp:1145 : 
> (hasSufficientPermsAndCapabilities) [0ms] Checking for permissions on the 
> relation
>   src/providers/postgres/qgspostgresprovider.cpp:3526 : 
> (getGeometryDetails) [0ms] Getting geometry column: SELECT 
> upper(type),srid,coord_dimension FROM geometry_columns WHERE 
> f_table_name='edge_data' AND f_geometry_column='geom' AND 
> f_table_schema='test0'
>   src/providers/postgres/qgspostgresprovider.cpp:3528 : 
> (getGeometryDetails) [1ms] Geometry column query returned 1 rows
>   src/providers/postgres/qgspostgresprovider.cpp:3769 : 
> (getGeometryDetails) [1ms] Detected SRID is 4167
>   src/providers/postgres/qgspostgresprovider.cpp:3770 : 
> (getGeometryDetails) [0ms] Requested SRID is 4167
>   src/providers/postgres/qgspostgresprovider.cpp:3771 : 
> (getGeometryDetails) [0ms] Detected type is 2
>   src/providers/postgres/qgspostgresprovider.cpp:3772 : 
> (getGeometryDetails) [0ms] Requested type is 2
>   src/providers/postgres/qgspostgresprovider.cpp:3780 : 
> (getGeometryDetails) [0ms] Spatial column type is Geometry
>   src/providers/postgres/qgspostgresprovider.cpp:747 : (loadFields) [0ms] 
> Loading fields for table edge_data
>   src/providers/postgres/qgspostgresprovider.cpp:1344 : 
> (determinePrimaryKey) [2ms] Checking whether SELECT count(*) FROM pg_inherits 
> WHERE inhparent='"test0"."edge_data"'::regclass is a parent table
>   src/providers/postgres/qgspostgresprovider.cpp:1349 : 
> (determinePrimaryKey) [0ms] Retrieving first primary or unique index: SELECT 
> indexrelid FROM pg_index WHERE indrelid='"test0"."edge_data"'::regclass AND 
> (indisprimary OR indisunique) ORDER BY CASE WHEN indisprimary THEN 1 ELSE 2 
> END LIMIT 1
>   src/providers/postgres/qgspostgresprovider.cpp:1352 : 
> (determinePrimaryKey) [1ms] Got 1 rows.
>   src/providers/postgres/qgspostgresprovider.cpp:1442 : 
> (determinePrimaryKey) [0ms] Retrieving key columns: SELECT attname,attnotnull 
> FROM pg_index,pg_attribute WHERE indexrelid=14313569 AND indrelid=attrelid 
> AND pg_attribute.attnum=any(pg_index.indkey)
>   src/providers/postgres/qgspostgresprovider.cpp:1444 : 
> (determinePrimaryKey) [0ms] Got 1 rows.
> 
> 
> --strk; 
> 
>   ()   Free GIS & Flash consultant/developer
>   /\   https://strk.kbt.io/services.html
> ___
> 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
> 

-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
QGIS-Developer 

[QGIS-Developer] Plugin [1324] Ungenerate approval notification.

[noreply]

Plugin Ungenerate approval by zimbogisgeek.
The plugin version "[1324] Ungenerate 1.0 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/Ungenerate/
___
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] Plugin [1785] Format consistency approval notification.

[noreply]

Plugin Format consistency approval by zimbogisgeek.
The plugin version "[1785] Format consistency 0.2" is now approved
Link: http://plugins.qgis.org/plugins/FormatConsistency/
___
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] Plugin [135] mmqgis approval notification.

[noreply]

Plugin mmqgis approval by zimbogisgeek.
The plugin version "[135] mmqgis 2019.8.11" is now approved
Link: http://plugins.qgis.org/plugins/mmqgis/
___
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] Plugin [1773] Forest Roads Network approval notification.

[noreply]

Plugin Forest Roads Network approval by zimbogisgeek.
The plugin version "[1773] Forest Roads Network 1.1" is now approved
Link: http://plugins.qgis.org/plugins/ForestRoadsNetworksUPLOAD/
___
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] Plugin [1538] Land Survey Codes Import approval notification.

[noreply]

Plugin Land Survey Codes Import approval by zimbogisgeek.
The plugin version "[1538] Land Survey Codes Import 0.2.0" is now approved
Link: http://plugins.qgis.org/plugins/LandSurveyCodesImport/
___
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] Plugin [1777] FloodRisk2 approval notification.

[noreply]

Plugin FloodRisk2 approval by zimbogisgeek.
The plugin version "[1777] FloodRisk2 0.2" is now approved
Link: http://plugins.qgis.org/plugins/floodrisk2/
___
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] Plugin [835] DEMto3D approval notification.

[noreply]

Plugin DEMto3D approval by zimbogisgeek.
The plugin version "[835] DEMto3D 3.1.1" is now approved
Link: http://plugins.qgis.org/plugins/DEMto3D/
___
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] Plugin [135] mmqgis approval notification.

[noreply]

Plugin mmqgis approval by zimbogisgeek.
The plugin version "[135] mmqgis 2019.8.11" is now approved
Link: http://plugins.qgis.org/plugins/mmqgis/
___
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] Plugin [1670] XYZ Hub Connector approval notification.

[noreply]

Plugin XYZ Hub Connector approval by zimbogisgeek.
The plugin version "[1670] XYZ Hub Connector 1.7.2" is now approved
Link: http://plugins.qgis.org/plugins/XYZHubConnector/
___
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] Plugin [1778] Cell File Generator approval notification.

[noreply]

Plugin Cell File Generator approval by zimbogisgeek.
The plugin version "[1778] Cell File Generator 0.3 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/cell_file_maker/
___
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