Re: [Qgis-developer] Future of OpenLayers plugin - time to deprecate?

[Paolo Cavallini]

Hi all,

Il 16/06/2016 00:06, Tim Sutton ha scritto:

> I’m wondering what the first storm was? The OpenLayers Plugin is a great
> tool for QGIS and I agree we could have approached this discussion more
> sensitively - e.g. by first approaching you and Maxim and other devs
> building similar tools to look for a way to reduce duplication of effort
> and solve the issues that users experience with printing etc. So please
> do accept our apologies.

I join Tim in apologizing. I'm pretty sure nobody had intention to
diminute Pirmin contribution to QGIS, and the plugin itself, just
motivated by the desire to improve the current situation for our users.

> But yes, I agree with you that having plugins which do illegal things in
> our repo is not good. Admittedly QuickMapServices does not ship with the
> potentially illegal services out of the box, but it does make it very
> easy to add them. @Paolo it would probably be good to add a clause to
> the plugin upload policy page indicating that plugins should not do
> illegal things (though this itself is subject to regional interpretation). 

Done: http://plugins.qgis.org/
Please see if it can be improved.
Thanks for the suggestion.
All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
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] Groups not desappearing from legend when filtered

[Paolo Cavallini]

Il 16/06/2016 04:59, Nyall Dawson ha scritto:
> On 16 June 2016 at 07:19, Paolo Cavallini  wrote:
>> I don't see when one would want to show an empty group.
>> Thanks!
> 
> Ok - I've forward ported Sourcepole's fix.

Thanks a lot. Any hope to have it backported to 2.14?
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
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] Groups not desappearing from legend when filtered

[Nyall Dawson]

On 16 June 2016 at 07:19, Paolo Cavallini  wrote:
> I don't see when one would want to show an empty group.
> Thanks!

Ok - I've forward ported Sourcepole's fix.

Nyall

>
>
> Il 16 giugno 2016 00:07:14 EEST, Nyall Dawson  ha
> scritto:
>>
>>
>> On 16 Jun 2016 6:05 AM, "Paolo Cavallini"  wrote:
>> >
>> > Il 15/06/2016 21:22, DelazJ ha scritto:
>> > > Hi,
>> > > already reported (see http://hub.qgis.org/issues/12969)
>> >
>> > Thanks to all for confirmation.
>> > Nyall, Martin, others: would a fix be complicated?
>> > All the best.
>>
>> Sourcepole's fork has a fix. I just wasn't sure if forward porting it was
>> safe. Do we *always* want to hide these? Is there any circumstance where
>> someone would want to show them?
>>
>> Nyall
>>
>> >
>> > --
>> > Paolo Cavallini - www.faunalia.eu
>> > QGIS & PostGIS courses: http://www.faunalia.eu/training.html
>> > ___
>> > 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
>
>
> --
> Paolo Cavallini
> www.faunalia.eu
___
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 QGIS and QGIS plugins fall under the same usage rights for scientific publication?

[Fox Underwood]

Hi Nathan,

Well, that's good news. Thank you for the answer! (And sorry for the
bother!)

Cheers,

On 15 June 2016 at 15:54, Nathan Woodrow  wrote:

> Hey Fox,
>
> QGIS plugins are always GPL no matter what (unless you don't share them).
> So yes QGIS and QGIS plugins both have the same copyright (well copyleft
> really) licence.
>
> You are free to use a plugin for what ever purpose you see fit.
>
> Regards,
>
> On Thu, Jun 16, 2016 at 2:08 AM, Fox Underwood 
> wrote:
>
>> QGIS, with citation, can be used for research. Can QGIS plugins
>> (installable from the plugin list within QGIS Desktop), with citation, also
>> be used for research? In other words, if someone creates a plugin that's
>> added to the repository, does the plugin then fall under all the same usage
>> and copyright rules that QGIS does?
>>
>> I realise it's splitting hairs and I'm sure it's alright to use the
>> plugin in research (citing both QGIS and the plugin creator separately),
>> but I was asked to look into plugin use for copyright reasons before
>> creating more figures and submitting a paper. I emailed the plugin
>> developer to ask permission to use the plugin for research purposes. Since
>> I haven't heard back, I thought I'd ask QGIS developers about usage of
>> plugins found in the repository.
>>
>> This page referred me to the QGIS developer mailing list:
>> http://hub.qgis.org/projects/quantum-gis/wiki/QGIS_Citation_Repository
>>
>> Clarification would be much appreciated. I'm quite happy to be using QGIS
>> for research now!
>>
>> Fox
>>
>> ___
>> 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] Future of OpenLayers plugin - time to deprecate?

[Tim Sutton]

Hi Pirmin


> On 15 Jun 2016, at 18:58, Pirmin Kalberer  wrote:
> 
> Hi all,
> 
> Am Mittwoch, 15. Juni 2016, 08.20:13 schrieb Richard Duivenvoorde:
>> Maybe first discuss with Author (in cc)?
> 
> Thanks Richard. Today was the 7th annual Swiss QGIS User meeting and 
> therefore 
> no time to answer to this second shit storm wave earlier.

> 
> First some history for QGIS newbies:
> The OpenLayers plugin was presented at the first QGIS User meeting six years 
> ago [1]. It was built to integrate Google Maps layers using the Google API 
> via 
> OpenLayers. At this time only the illegal (but well known) way using a GDAL 
> VRT supported this functionality. In the meantime there have been at least 
> three plugins reimplementing this illegal TMS access method, the latest (and 
> best) is QuickMapServices. The OpenLayers plugin got the first major breakage 
> with the QGIS 2.0 API change. The multithreaded rendering in QGIS 2.4 caused 
> a 
> complete rewrite of the plugin. Between and after that other QGIS or Google 
> Maps changes have broken the OpenLayers plugin from time to time and it was a 
> matter of course that we "fix" it to adapt these (usually paid) changes.
> 
> I personally don't think that the name of this or another plugin is the main 
> reason for more than 700'000 downloads of the OpenLayers plugin. I know of 
> quite a few users staying with old QGIS version (even 1.x) just to be able to 
> display and print Google Maps base layers. For some of them the plugin was 
> important enough, to pay a few hundred Swiss Francs for another "bug fix". 
> Apart of this, OpenLayers was always done in my limited spare time at home or 
> at hackfests (travelling sponsored by Sourcepole). Even when I pointed at a 
> possible breakages of PluginLayers, like before merging the map rotation 
> feature, it seemed never to have any priority to test a change with the OL 
> plugin or even preventing to break it. This attitude and the destructive 
> Trump-syle tone with the +1 frency in this community mailing list are 
> definitely not the motivation I would need for another bug fix. And regarding 
> the reputation of QGIS, I find promoting a plugin for doing  illegal things 
> worse than not fixing printing problems.
> 
> Enough of getting my frustration out - I have also a constructive proposal: 
> Please pass a customRenderFlag during composer rendering to give PluginLayers 
> a chance to handle this case without adventurous workarounds (and besides 
> make 
> it possible to fix WMTS printing with more than 90dpi's). I would then at 
> least 
> turn off OL layers and display a message.


I’m wondering what the first storm was? The OpenLayers Plugin is a great tool 
for QGIS and I agree we could have approached this discussion more sensitively 
- e.g. by first approaching you and Maxim and other devs building similar tools 
to look for a way to reduce duplication of effort and solve the issues that 
users experience with printing etc. So please do accept our apologies.

I do think it is worth discussing this though because we want to try to tidy up 
the plugin repository and make things clearer for users (for example by not 
having multiple plugins which ostensibly do the same thing). In the situation 
where we do have multiple plugins which do the same or similar things, then it 
would be nice to a) encourage the developers to work together on one version if 
possible and b) make it easier for the user to figure out which is the best one 
to install.

Specifically with reference to the legalities, is it really the case that 
OpenLayers plugin is on firm legal footing and the others are not?

I’m reading here:

https://developers.google.com/maps/faq#getting-started

and here:

https://developers.google.com/maps/terms

Things that may apply here:


• "No access to APIs or Content except through the Service. You will not access 
the Maps API(s) or the Content except through the Service. For example, you 
must not access map tiles or imagery through interfaces or channels (including 
undocumented Google interfaces) other than the Maps API(s)."

So my understanding for this is: OpenLayers Plugin uses the API so its fine, 
TMS wrappers in GDAL do not so it probably contravenes the license.

• "No use of Content with a non-Google map. You must not use the Content in a 
Maps API Implementation that contains a non-Google map."

This is a bit harder as it seems to impact all plugins using Google Maps - it 
pretty much excludes any typical use case a QGIS user might have - combining 
google maps as a backdrop layer with your own data? Or do I interpret this 
incorrectly?


But yes, I agree with you that having plugins which do illegal things in our 
repo is not good. Admittedly QuickMapServices does not ship with the 
potentially illegal services out of the box, but it does make it very easy to 
add them. @Paolo it would probably be good to add a clause to the plugin upload 
policy page indicating 

Re: [Qgis-developer] Do QGIS and QGIS plugins fall under the same usage rights for scientific publication?

[Nathan Woodrow]

Hey Fox,

QGIS plugins are always GPL no matter what (unless you don't share them).
So yes QGIS and QGIS plugins both have the same copyright (well copyleft
really) licence.

You are free to use a plugin for what ever purpose you see fit.

Regards,

On Thu, Jun 16, 2016 at 2:08 AM, Fox Underwood 
wrote:

> QGIS, with citation, can be used for research. Can QGIS plugins
> (installable from the plugin list within QGIS Desktop), with citation, also
> be used for research? In other words, if someone creates a plugin that's
> added to the repository, does the plugin then fall under all the same usage
> and copyright rules that QGIS does?
>
> I realise it's splitting hairs and I'm sure it's alright to use the plugin
> in research (citing both QGIS and the plugin creator separately), but I was
> asked to look into plugin use for copyright reasons before creating more
> figures and submitting a paper. I emailed the plugin developer to ask
> permission to use the plugin for research purposes. Since I haven't heard
> back, I thought I'd ask QGIS developers about usage of plugins found in the
> repository.
>
> This page referred me to the QGIS developer mailing list:
> http://hub.qgis.org/projects/quantum-gis/wiki/QGIS_Citation_Repository
>
> Clarification would be much appreciated. I'm quite happy to be using QGIS
> for research now!
>
> Fox
>
> ___
> 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] Groups not desappearing from legend when filtered

[Paolo Cavallini]

I don't see when one would want to show an empty group.
Thanks!

Il 16 giugno 2016 00:07:14 EEST, Nyall Dawson  ha 
scritto:
>On 16 Jun 2016 6:05 AM, "Paolo Cavallini" 
>wrote:
>>
>> Il 15/06/2016 21:22, DelazJ ha scritto:
>> > Hi,
>> > already reported (see http://hub.qgis.org/issues/12969)
>>
>> Thanks to all for confirmation.
>> Nyall, Martin, others: would a fix be complicated?
>> All the best.
>
>Sourcepole's fork has a fix. I just wasn't sure if forward porting it
>was
>safe. Do we *always* want to hide these? Is there any circumstance
>where
>someone would want to show them?
>
>Nyall
>
>>
>> --
>> Paolo Cavallini - www.faunalia.eu
>> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
>> ___
>> 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

-- 
Paolo Cavallini
www.faunalia.eu___
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] Groups not desappearing from legend when filtered

[Nyall Dawson]

On 16 Jun 2016 6:05 AM, "Paolo Cavallini"  wrote:
>
> Il 15/06/2016 21:22, DelazJ ha scritto:
> > Hi,
> > already reported (see http://hub.qgis.org/issues/12969)
>
> Thanks to all for confirmation.
> Nyall, Martin, others: would a fix be complicated?
> All the best.

Sourcepole's fork has a fix. I just wasn't sure if forward porting it was
safe. Do we *always* want to hide these? Is there any circumstance where
someone would want to show them?

Nyall

>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> ___
> 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] Groups not desappearing from legend when filtered

[Paolo Cavallini]

Il 15/06/2016 21:22, DelazJ ha scritto:
> Hi,
> already reported (see http://hub.qgis.org/issues/12969)

Thanks to all for confirmation.
Nyall, Martin, others: would a fix be complicated?
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
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] Groups not desappearing from legend when filtered

[DelazJ]

notice that today is the birthday of the bug report :) : a sign of an
upcoming fix?

2016-06-15 21:22 GMT+02:00 roy roy :

>
> > Hi all,
> > in print layout, if I filter only visible element to be shown in the
> > legend, this works. Apparently however the names of empty groups are
> > shown anyway: am I wrong? Should I open a ticket?
> > Thanks.
> I can confirm this behaviour, i agree that empty groups should be
> filtered as well
> ___
> 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] Groups not desappearing from legend when filtered

[DelazJ]

Hi,
already reported (see http://hub.qgis.org/issues/12969)

Harrissou

2016-06-15 21:11 GMT+02:00 Anita Graser :

>
>
> On Wed, Jun 15, 2016 at 7:35 PM, Paolo Cavallini 
> wrote:
>
>> Hi all,
>> in print layout, if I filter only visible element to be shown in the
>> legend, this works. Apparently however the names of empty groups are
>> shown anyway: am I wrong? Should I open a ticket?
>>
>
> ​Same here, would be nicer if the group would be hidden as well if empty.
>
> 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 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] Groups not desappearing from legend when filtered

[roy roy]

> Hi all,
> in print layout, if I filter only visible element to be shown in the
> legend, this works. Apparently however the names of empty groups are
> shown anyway: am I wrong? Should I open a ticket?
> Thanks.
I can confirm this behaviour, i agree that empty groups should be 
filtered as well
___
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] Groups not desappearing from legend when filtered

[Anita Graser]

On Wed, Jun 15, 2016 at 7:35 PM, Paolo Cavallini 
wrote:

> Hi all,
> in print layout, if I filter only visible element to be shown in the
> legend, this works. Apparently however the names of empty groups are
> shown anyway: am I wrong? Should I open a ticket?
>

​Same here, would be nicer if the group would be hidden as well if empty.

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

Re: [Qgis-developer] Future of OpenLayers plugin - time to deprecate?

[Pirmin Kalberer]

Hi all,

Am Mittwoch, 15. Juni 2016, 08.20:13 schrieb Richard Duivenvoorde:
> Maybe first discuss with Author (in cc)?

Thanks Richard. Today was the 7th annual Swiss QGIS User meeting and therefore 
no time to answer to this second shit storm wave earlier.

First some history for QGIS newbies:
The OpenLayers plugin was presented at the first QGIS User meeting six years 
ago [1]. It was built to integrate Google Maps layers using the Google API via 
OpenLayers. At this time only the illegal (but well known) way using a GDAL 
VRT supported this functionality. In the meantime there have been at least 
three plugins reimplementing this illegal TMS access method, the latest (and 
best) is QuickMapServices. The OpenLayers plugin got the first major breakage 
with the QGIS 2.0 API change. The multithreaded rendering in QGIS 2.4 caused a 
complete rewrite of the plugin. Between and after that other QGIS or Google 
Maps changes have broken the OpenLayers plugin from time to time and it was a 
matter of course that we "fix" it to adapt these (usually paid) changes.

I personally don't think that the name of this or another plugin is the main 
reason for more than 700'000 downloads of the OpenLayers plugin. I know of 
quite a few users staying with old QGIS version (even 1.x) just to be able to 
display and print Google Maps base layers. For some of them the plugin was 
important enough, to pay a few hundred Swiss Francs for another "bug fix". 
Apart of this, OpenLayers was always done in my limited spare time at home or 
at hackfests (travelling sponsored by Sourcepole). Even when I pointed at a 
possible breakages of PluginLayers, like before merging the map rotation 
feature, it seemed never to have any priority to test a change with the OL 
plugin or even preventing to break it. This attitude and the destructive 
Trump-syle tone with the +1 frency in this community mailing list are 
definitely not the motivation I would need for another bug fix. And regarding 
the reputation of QGIS, I find promoting a plugin for doing  illegal things 
worse than not fixing printing problems.

Enough of getting my frustration out - I have also a constructive proposal: 
Please pass a customRenderFlag during composer rendering to give PluginLayers 
a chance to handle this case without adventurous workarounds (and besides make 
it possible to fix WMTS printing with more than 90dpi's). I would then at least 
turn off OL layers and display a message.

Regards
Pirmin

-- 
Pirmin Kalberer - @PirminKalberer
Sourcepole - http://www.sourcepole.com

[1] http://blog.sourcepole.com/2010/04/23/folien-qgis-user-meeting-bern/

> 
> As the maintainers used to put a lot of work into the plugin. In my view
> it is not very polite to retract/depricate a plugin.
> 
> Best I think would be (if Pirmin and Matthias are ok with it), to
> temporarily depricate it, AND show with a message in the description
> that there is a working alternative.
> This would give SP time to fix, without time pressure.
> 
> Unless off course the Plugin is being depricated by the authors too
> Then it could just be removed.
> 
> Maybe we should have a mechanisme in the plugins to do such messages?
> For example: "This plugins is not working properly because (eg
> Webkit/Debian)" or "This plugin is deprecated in favour of ..."?
> 
> Regards,
> 
> Richard Duivenvoorde
> 
> On 14-06-16 23:04, Paolo Cavallini wrote:
> > Makes sense to me. Going to deprecate it tomorrow if nobody objects.
> > Thanks Nyall.
> > 
> > Il 14 giugno 2016 22:25:06 CEST, Anita Graser  ha
> > 
> > scritto:
> > On Tue, Jun 14, 2016 at 9:57 PM, Nyall Dawson
> > 
> > > wrote:
> > On 31 Dec 2015 7:33 AM, "Nyall Dawson"  > 
> > > wrote:
> > > Hi all,
> > > 
> > > The email chain below is just one example of a user who has
> > > issues
> > > with QGIS after installing the OpenLayers plugin. Stackexchange
> > > is
> > > filled with similar examples (See
> > > http://gis.stackexchange.com/questions/tagged/qgis-openlayers-pl
> > > ugin).
> > > 
> > > I'm wondering if it's time we discussed the future of this
> > > plugin. Now
> > > that we have a viable replacement (Quick Map Services) which
> > > doesn't
> > > demonstrate these issues, should we deprecate the OpenLayers
> > > plugin
> > > and remove it from the plugin repo?
> > 
> > Can we revisit this discussion again?
> > 
> > I'm very much in favour of:
> > 1. Removing openlayers plugin from the repo asap. This plugin is
> > broken and unfortunately is harming the reputation of the
> > project, as many users cannot distinguish the difference between
> > the plugin's issues and problems 

[Qgis-developer] Groups not desappearing from legend when filtered

[Paolo Cavallini]

Hi all,
in print layout, if I filter only visible element to be shown in the
legend, this works. Apparently however the names of empty groups are
shown anyway: am I wrong? Should I open a ticket?
Thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
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] What's the recommended way to implement a spatial index in Processing algorithms?

[Anita Graser]

​Hi,

On Tue, Jun 14, 2016 at 3:01 PM, Daan Goedkoop  wrote:

> What I use is:
> features = processing.features( layer )
> index = QgsSpatialIndex( features.__iter__() )


Thanks Daan, that looks good!


On Wed, Jun 15, 2016 at 12:31 PM, Victor Olaya  wrote:

> i guess that the spatial index should be created as usual, but, as you
> say, only including selected features if the Processing settings is
> configured to use only those ones.
> I dont see any specific thing about it being a Processing algorithm,
> other than that. An even if you create it for the whole layer, it
> should be fine (although less efficient)
> ​​
>

​Well, it would be less efficient to build the index and one would have to
check later on if the feature was selected. Otherwise, e.g. the hub
distance algorithm, would return wrong matches to unselected hubs ...


> Any particular problem that you are facing with this
> ​?
>

​No particular problem, just wondering what's the most elegant way and if
there is anything I should be aware of when implementing the index. It
would be good to have this as an example in the PyQGIS Cookbook imho. (Not
just building the index but also accessing the nearest features.)

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] Do QGIS and QGIS plugins fall under the same usage rights for scientific publication?

[Fox Underwood]

QGIS, with citation, can be used for research. Can QGIS plugins
(installable from the plugin list within QGIS Desktop), with citation, also
be used for research? In other words, if someone creates a plugin that's
added to the repository, does the plugin then fall under all the same usage
and copyright rules that QGIS does?

I realise it's splitting hairs and I'm sure it's alright to use the plugin
in research (citing both QGIS and the plugin creator separately), but I was
asked to look into plugin use for copyright reasons before creating more
figures and submitting a paper. I emailed the plugin developer to ask
permission to use the plugin for research purposes. Since I haven't heard
back, I thought I'd ask QGIS developers about usage of plugins found in the
repository.

This page referred me to the QGIS developer mailing list:
http://hub.qgis.org/projects/quantum-gis/wiki/QGIS_Citation_Repository

Clarification would be much appreciated. I'm quite happy to be using QGIS
for research now!

Fox
___
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] Future of OpenLayers plugin - time to deprecate?

[Yves Jacolin]

On Wednesday, June 15, 2016 9:51:39 Paolo Cavallini wrote:
> Il 15/06/2016 09:47, Yves Jacolin ha scritto:
> > Hi,
> > 
> > On Wednesday, June 15, 2016 9:21:51 Paolo Cavallini wrote:
> >> IANAL, but AFAIK the OL
> > 
> > Sometime it is hard to follow you :)
> 
> I was thinking about this while writing :)
> So, let me explain:
> I Am Not A Lawyer, but As Far As I Know the OpenLayers plugin ...
> All the best.
many thanks Paolo!

Y.
___
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] Future of OpenLayers plugin - time to deprecate?

[Yves Jacolin]

Hi,

On Wednesday, June 15, 2016 9:21:51 Paolo Cavallini wrote:
> IANAL, but AFAIK the OL
Sometime it is hard to follow you :)

Y.
___
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] Layer Search and Quick Finder Plugins Integration

[C Hamilton]

I would like to see the Layer Search plugin capability available in QGIS
sometime relative soon and it was proposed to integrate it into Quick
Finder.

It is important to me for Layer Search to display the results of what was
found, the layer it was found in and the column it was found in. I would
also like it to be able to display a fairly large number of results.

This does not fit with the drop down methodology that Quick Finder uses. I
could do a pull request and add Layer Search as a separate search in the
Quick Finder menu. Would that be acceptable or are their any other ideas? I
am not necessarily sure the original request to merge capabilities means
this solution, but I also don't see the direct integration in the Quick
Finder drop down menu results.

Let me know if there is anything more I can do to either help integrate or
whether in the near term layer search should be approved as a plugin.

Thanks,

Calvin
___
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] What's the recommended way to implement a spatial index in Processing algorithms?

[Victor Olaya]

i guess that the spatial index should be created as usual, but, as you
say, only including selected features if the Processing settings is
configured to use only those ones.

I dont see any specific thing about it being a Processing algorithm,
other than that. An even if you create it for the whole layer, it
should be fine (although less efficient)

Any particular problem that you are facing with this?

2016-06-14 12:54 GMT+02:00 Anita Graser :
> Hi,
>
> Some existing Processing algorithms could be faster by making use of a
> spatial index, e.g. http://hub.qgis.org/issues/15012
>
> What's the recommended way to implement a spatial index in a processing
> algorithm to ensure consistent behavior with other tools (e.g. concerning
> using only selected features)?
>
> 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 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] Future of OpenLayers plugin - time to deprecate?

[Paolo Cavallini]

Il 15/06/2016 09:50, Bernd Vogelgesang ha scritto:

> I would propose to rename it to "Basemaps (OpenLayers replacement)".
> QuickMapServices is one of the most unintuitive names for such a basic
> need ... a basemap ;)

Agreed; this is true of many plugins, unfortunately.
I try to convince plugin developers to give informative names, but
changing the name of an existing plugin creates some confusion, and is
not straightforward.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
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] Future of OpenLayers plugin - time to deprecate?

[Tom Chadwin]

Paolo Cavallini wrote
> there is an additional problem: IANAL, but AFAIK the OL plugin does not
> break licence from service providers, wherear QMS plugin does. So, it is
> not a simple drop-in replacement.
> Integrating a native TMS driver in QGIS (generally the best option) may
> make things worse.

Any provider can be abused - WFS,  SHP, whatever. For me, a native tile
server provider would be fabulous. 

Tom



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Future-of-OpenLayers-plugin-time-to-deprecate-tp5243358p5271718.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

Re: [Qgis-developer] Future of OpenLayers plugin - time to deprecate?

[Paolo Cavallini]

Il 15/06/2016 09:47, Yves Jacolin ha scritto:
> Hi,
> 
> On Wednesday, June 15, 2016 9:21:51 Paolo Cavallini wrote:
>> IANAL, but AFAIK the OL
> Sometime it is hard to follow you :)

I was thinking about this while writing :)
So, let me explain:
I Am Not A Lawyer, but As Far As I Know the OpenLayers plugin ...
All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
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] Future of OpenLayers plugin - time to deprecate?

[Bernd Vogelgesang]

Am 14.06.2016, 22:25 Uhr, schrieb Anita Graser :




On Tue, Jun 14, 2016 at 9:57 PM, Nyall Dawson   
wrote:




On 31 Dec 2015 7:33 AM, "Nyall Dawson"  wrote:


Hi all,

The email chain below is just one example of a user who has issues
with QGIS after installing the OpenLayers plugin. Stackexchange is
filled with similar examples (See
http://gis.stackexchange.com/questions/tagged/qgis-openlayers-plugin).

I'm wondering if it's time we discussed the future of this plugin. Now
that we have a viable replacement (Quick Map Services) which doesn't
demonstrate these issues, should we deprecate the OpenLayers plugin
and remove it from the plugin repo?


Can we revisit this discussion again?

I'm very much in favour of:
1. Removing openlayers plugin from the repo asap. This plugin is broken  
and unfortunately is harming the reputation of the >>project, as many  
users cannot distinguish the difference between the plugin's issues and  
problems with QGIS itself (eg see  
>>https://twitter.com/thatkindofplace/status/742543174573260800?s=03 )


2. Rename QuickMapServices as "QuickMapServices (OpenLayers  
replacement)" on the plugin repo, so users looking for openlayers >>are  
nicely directed to the new plugin
I would propose to rename it to "Basemaps (OpenLayers replacement)".  
QuickMapServices is one of the most unintuitive names for such a basic  
need ... a basemap ;)


My 2 cents
Bernd


​+1 for all the reasons above.

Thanks for reviving this Nyall!

Best wishes,
Anita​






--
Bernd Vogelgesang
Siedlerstraße 2
91083 Baiersdorf/Igelsdorf
Tel: 09133-825374___
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] Animated gif support now in changelog

[Tom Chadwin]

A prize for the first GIF of a feature demonstrated by a cat...



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Animated-gif-support-now-in-changelog-tp5271458p5271712.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

Re: [Qgis-developer] Future of OpenLayers plugin - time to deprecate?

[Paolo Cavallini]

Il 15/06/2016 02:43, Mathieu Pellerin ha scritto:
> +1 too, for removing openlayers and looking into putting efforts to come
> up with a native TMS driver.
> 
> Suggestion: instead of just removing openlayers from the plugin
> repository, could we work with the author (if he's reachable and
> willing) for him to publish a new plugin update stating that a/ the
> plugin is discontinued, and b/ users should migrate to quickservicemap?

Hi all,
there is an additional problem: IANAL, but AFAIK the OL plugin does not
break licence from service providers, wherear QMS plugin does. So, it is
not a simple drop-in replacement.
Integrating a native TMS driver in QGIS (generally the best option) may
make things worse.
All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
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] Future of OpenLayers plugin - time to deprecate?

[Richard Duivenvoorde]

Duh.. sorry for this reply, did not load the newer messages apparently :-(

On 15-06-16 08:20, Richard Duivenvoorde wrote:
> 
> Maybe first discuss with Author (in cc)?
> 
> As the maintainers used to put a lot of work into the plugin. In my view
> it is not very polite to retract/depricate a plugin.
> 
> Best I think would be (if Pirmin and Matthias are ok with it), to
> temporarily depricate it, AND show with a message in the description
> that there is a working alternative.
> This would give SP time to fix, without time pressure.
> 
> Unless off course the Plugin is being depricated by the authors too
> Then it could just be removed.
> 
> Maybe we should have a mechanisme in the plugins to do such messages?
> For example: "This plugins is not working properly because (eg
> Webkit/Debian)" or "This plugin is deprecated in favour of ..."?
> 
> Regards,
> 
> Richard Duivenvoorde
> 
> On 14-06-16 23:04, Paolo Cavallini wrote:
>> Makes sense to me. Going to deprecate it tomorrow if nobody objects.
>> Thanks Nyall.
>>
>> Il 14 giugno 2016 22:25:06 CEST, Anita Graser  ha
>> scritto:
>>
>>
>>
>> On Tue, Jun 14, 2016 at 9:57 PM, Nyall Dawson
>> > wrote:
>>
>>
>> On 31 Dec 2015 7:33 AM, "Nyall Dawson" > > wrote:
>> >
>> > Hi all,
>> >
>> > The email chain below is just one example of a user who has issues
>> > with QGIS after installing the OpenLayers plugin. Stackexchange is
>> > filled with similar examples (See
>> > 
>> http://gis.stackexchange.com/questions/tagged/qgis-openlayers-plugin).
>> >
>> > I'm wondering if it's time we discussed the future of this plugin. 
>> Now
>> > that we have a viable replacement (Quick Map Services) which 
>> doesn't
>> > demonstrate these issues, should we deprecate the OpenLayers plugin
>> > and remove it from the plugin repo?
>>
>> Can we revisit this discussion again?
>>
>> I'm very much in favour of:
>> 1. Removing openlayers plugin from the repo asap. This plugin is
>> broken and unfortunately is harming the reputation of the
>> project, as many users cannot distinguish the difference between
>> the plugin's issues and problems with QGIS itself (eg see
>> https://twitter.com/thatkindofplace/status/742543174573260800?s=03 )
>>
>> 2. Rename QuickMapServices as "QuickMapServices (OpenLayers
>> replacement)" on the plugin repo, so users looking for
>> openlayers are nicely directed to the new plugin
>>
>> ​+1 for all the reasons above.
>>
>> Thanks for reviving this Nyall!
>>
>> 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
>>
>>
>> -- 
>> Paolo Cavallini
>> www.faunalia.eu 
>>
>>
>> ___
>> 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] Future of OpenLayers plugin - time to deprecate?

[Richard Duivenvoorde]

Maybe first discuss with Author (in cc)?

As the maintainers used to put a lot of work into the plugin. In my view
it is not very polite to retract/depricate a plugin.

Best I think would be (if Pirmin and Matthias are ok with it), to
temporarily depricate it, AND show with a message in the description
that there is a working alternative.
This would give SP time to fix, without time pressure.

Unless off course the Plugin is being depricated by the authors too
Then it could just be removed.

Maybe we should have a mechanisme in the plugins to do such messages?
For example: "This plugins is not working properly because (eg
Webkit/Debian)" or "This plugin is deprecated in favour of ..."?

Regards,

Richard Duivenvoorde

On 14-06-16 23:04, Paolo Cavallini wrote:
> Makes sense to me. Going to deprecate it tomorrow if nobody objects.
> Thanks Nyall.
> 
> Il 14 giugno 2016 22:25:06 CEST, Anita Graser  ha
> scritto:
> 
> 
> 
> On Tue, Jun 14, 2016 at 9:57 PM, Nyall Dawson
> > wrote:
> 
> 
> On 31 Dec 2015 7:33 AM, "Nyall Dawson"  > wrote:
> >
> > Hi all,
> >
> > The email chain below is just one example of a user who has issues
> > with QGIS after installing the OpenLayers plugin. Stackexchange is
> > filled with similar examples (See
> > 
> http://gis.stackexchange.com/questions/tagged/qgis-openlayers-plugin).
> >
> > I'm wondering if it's time we discussed the future of this plugin. 
> Now
> > that we have a viable replacement (Quick Map Services) which doesn't
> > demonstrate these issues, should we deprecate the OpenLayers plugin
> > and remove it from the plugin repo?
> 
> Can we revisit this discussion again?
> 
> I'm very much in favour of:
> 1. Removing openlayers plugin from the repo asap. This plugin is
> broken and unfortunately is harming the reputation of the
> project, as many users cannot distinguish the difference between
> the plugin's issues and problems with QGIS itself (eg see
> https://twitter.com/thatkindofplace/status/742543174573260800?s=03 )
> 
> 2. Rename QuickMapServices as "QuickMapServices (OpenLayers
> replacement)" on the plugin repo, so users looking for
> openlayers are nicely directed to the new plugin
> 
> ​+1 for all the reasons above.
> 
> Thanks for reviving this Nyall!
> 
> 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
> 
> 
> -- 
> Paolo Cavallini
> www.faunalia.eu 
> 
> 
> ___
> 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