On 29 June 2017 at 16:27, Paolo Cavallini wrote:
> Hi all,
> I'm testing the new Processing on master. To do this with some order,
> I'm following the training manual:
> http://docs.qgis.org/2.18/en/docs/training_manual/processing/index.html
> and I'll report any issue. Should I just send a messag
On 28 June 2017 at 18:23, G. Allegri wrote:
> The best of two (but there would be a bit of overhead for the algorithm):
> set them to null as soon as two different values are found, keep the first
> encountered value otherwise (all the features with same value).
>
Ok - I've actually had a bit of
Hi all,
I'm testing the new Processing on master. To do this with some order,
I'm following the training manual:
http://docs.qgis.org/2.18/en/docs/training_manual/processing/index.html
and I'll report any issue. Should I just send a message here, or open a
ticket?
as I go, I stumble across commands
This PR (https://github.com/qgis/QGIS/pull/4792) adds variance to
QgsZonalStatistics, and remove the duplicate processing zonal statistics
algorithm on the basis of a general consensus in this mail tread and more
importantly its author, Alexander Bruy, agreeing.
Thanks for the time spent discussin
olivier wrote
> Awesome that will perfectly do until 3.0.
Olivier, could you elaborate just a bit on how to do this in 2.18? I’m a
QGIS beginner, I can bring up the Python Console in QGIS, but then what
function do I invoke that will create an XYZ tile layer where I can specify
zmin/zmax?
Thank y
Il 28 giugno 2017 23:34:04 CEST, Tao Lu ha scritto:
>Hi
>
>I have uploaded a plugin 10 days ago.
>http://plugins.qgis.org/plugins/SuperLabeling/
>I want to know how long will the plugin be approved?
>
>Thanks,
>Tao
Please have a look to the bugtracker.
Thanks.
--
Sent from mobile. Sorry for bein
Hi
I have uploaded a plugin 10 days ago.
http://plugins.qgis.org/plugins/SuperLabeling/
I want to know how long will the plugin be approved?
Thanks,
Tao___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mai
The best of two (but there would be a bit of overhead for the algorithm):
set them to null as soon as two different values are found, keep the first
encountered value otherwise (all the features with same value).
giovanni
2017-06-28 10:16 GMT+02:00 Anita Graser :
>
>
> On Wed, Jun 28, 2017 at
Il 28/06/2017 09:48, Nyall Dawson ha scritto:
> We could just rename the option as "Majority (mode)" - does that work
> for you? (or "Mode (majority)").
fine for me; I just think mode is much more used in stats.
>> Would it be possible to also add variance?
>
> Should be trivial to do - it's ju
On Wed, Jun 28, 2017 at 9:53 AM, Nyall Dawson
wrote:
>
> Incidentally - how should we handle attributes here (and other similar
> algorithms)? Take the first feature's attributes? Drop all attributes?
>
>
I would take the first feature's attributes because I've seen multiple
times that input data
IMHO Spatial join should should provide an option to collect values in a
comma separated list of values in case of categorical (texts) values.
This is something I've been asked many times from users, and I always give
them a script to do it.
PS: This option is also available in a couple of widespr
I would set them to null. In general I wouldn't change the dataset fields
schema along the processing steps, except in case of algorithms dedicated
to this.
The same happens with Dissolve.
giovanni
Il 28 giu 2017 09:53, "Nyall Dawson" ha scritto:
> On 28 June 2017 at 14:42, Paolo Cavallini wro
On 28 June 2017 at 14:42, Paolo Cavallini wrote:
> If we use the boolean as you suggested, I think the default should
> probably be all features.
That's fine by me.
Incidentally - how should we handle attributes here (and other similar
algorithms)? Take the first feature's attributes? Drop all
On 28 June 2017 at 16:23, Paolo Cavallini wrote:
>
>
> Fine. Could we then rename from majority to mode? More understandable IMHO.
We could just rename the option as "Majority (mode)" - does that work
for you? (or "Mode (majority)").
> Would it be possible to also add variance?
Should be trivi
Hi,
> As we go for more sophisticated algs, having a good help system will be
> crucial. BTW, Alex, Matteo, what is the state of your work?
Alex did a great job that has already landed in the code:
https://github.com/qgis/QGIS/pull/4675
However, Processing is in big revolution right now, so bef
15 matches
Mail list logo
