Hi,
I would also prefer a double dev cycle, followed by a double test
period. So just shift the one month from the first dev cycle towards the
end.
In Bonn we discussed this and I think the double dev cycle was an
option, but we said we would decide in December/January when we know
more about
Hi Victor,
Il 06/12/2016 07:33, Victor Olaya ha scritto:
> Let me know what you think
I like the idea of modularity. However, requiring the user to do extra
steps to use GRASS, SAGA, GDAL/OGR, that are already shipped with our
packages, seems a bit of hindrance.
All the best.
--
Paolo Cavallini
Hi all
Before writing a QEP, I would like to discuss quickly here one idea
about Processing, that I think could be interesting and feasible for
3.0
Currently, Processing has some “core” providers (those that are part
of the Processing code itself and are installed with QGIS), ranging
from basic
Plugin dzetsaka : Classification tool approval by pcav.
The plugin version "[995] dzetsaka : Classification tool 2.1" is now approved
Link: http://plugins.qgis.org/plugins/dzetsaka/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List
Hi all,
Il 06/12/2016 00:02, Nyall Dawson ha scritto:
> Hmm I've brought up previously on the list my thoughts that we
> should *extend* the timeline to mid next year, as opposed to speeding
> it up.
>
> See https://lists.osgeo.org/pipermail/qgis-developer/2016-October/045554.html
>
> I'm
Hi Nyall
Wow this is absolutely fantastic! Thanks so much for all your hard work! When
you have all your social media bits ready let me know and I will make a blog
post on http://blog.qgis.org - I think it is a really great demonstration of
how we use the funds donated to QGIS for the good of
On 3 December 2016 at 19:51, Paolo Cavallini wrote:
> Hi all,
> I'm regularly compiling QGIS master, and I'm surprised how usable and
> smooth it is - obviously not suitable for production, but apparently not
> so far from it. It would be great if those more involved with
On 6 December 2016 at 05:46, Matthias Kuhn wrote:
> Thanks for writing this up Nyall,
>
> This is something that I has been on my list of ideas for a long time
> already and that I have never got round to get down to.
>
> I think you have covered the topic quite well already,
I think qgis-dev is now a zombie, as it's v2 master, where there has nor been
any work for a while.
-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
--
View this message in context:
I would really like an option to allow advanced users to manually just SET the
extents of a vector layer when first adding it, so that a full table-scan can
be avoided to derive that result.
This still seems to happen, even though the “use estimated metadata” flag is
checked, when first adding
Thanks for writing this up Nyall,
This is something that I has been on my list of ideas for a long time
already and that I have never got round to get down to.
I think you have covered the topic quite well already, so I don't think
there's a lot I have to add right now.
On 12/05/2016 06:41 PM,
I really like the idea of having basic Processing code in the core library
with Python bindings available.
Regarding iterators approach... It sounds interesting, but we need to think
also about possibility to work with layers, which are not loaded in QGIS.
In this case as I understand we need to
Thanks Victor!
On Mon, Dec 5, 2016 at 1:54 PM, Victor Olaya wrote:
> Anita, Mathieu
>
> I added both of your requests and it should be possible now to use
> tables on both "execute SQL" and "build virtual vector" algorithms
>
> Let me know if you try it (it is on master)
>
Dear all,
The Faculty ITC [1] of the University of Twente, The Netherlands, is starting a
9 month distance course in Geo-Information Science and Earth Observation (15 EC
spread over a 9-month period) that can be taken solo or as a first step to a
full MSc degree..
A decision was made to
Anita, Mathieu
I added both of your requests and it should be possible now to use
tables on both "execute SQL" and "build virtual vector" algorithms
Let me know if you try it (it is on master)
Cheers
2016-12-05 11:07 GMT+01:00 Mathieu Pellerin :
> Victor,
>
> I was
geo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
__ Information from ESET Mail Security, version of virus signature
database 14553 (20161205) __
The message was checked by ESET Mail Se
Hi
I would very much like to see improvements for Processing. A few additional
ideas:
- Display the number of features going through the model. This would help
the user understand the data better.
- Add comments to model components without opening each component. A chance
to explain why a
Klaus,
You can see this post on how to replace them if you want.
http://gis.stackexchange.com/questions/220138/removing-santa-hat-from-qgis-icon/220222#220222
Regards,
Nathan
On Mon, Dec 5, 2016 at 7:32 PM, Mithöfer wrote:
> Dear group,
> not everybody was happy
Victor,
I was looking into this; it'd be nice for the "build vector layer"
algorithm would support/show geometryless layers in the parametermultiinput
panel. AFAIK, geometryless layers aren't (yet? :) ) supported by the
parametermultiinput.
Math
On Mon, Dec 5, 2016 at 2:51 PM, Victor Olaya
Dear group,
not everybody was happy about it. We have cusumer who are a bit
irritated asking where it suddenly came from (and what other
changes were applied...).
Regards,
Klaus
Am Thu, 1 Dec 2016 12:10:12 +0100
schrieb Geo DrinX :
> This morning, I had the surprise of see
Hi all,
I've recently been informally chatting about possible enhancements to
processing with a few QGIS team members, and I thought it'd be worth
starting a public brainstorm about these ideas.
This is really just "thinking aloud" about what the next logical steps
are for processing and how we
Nice!
Definitely, a major step ahead, and will be very important for making
Processing more responsive
thanks for your great work!
2016-12-05 9:04 GMT+01:00 Nyall Dawson :
> Hi all,
>
> Thanks to tons of valuable feedback from the QGIS community and the
> generous
Hi all,
Thanks to tons of valuable feedback from the QGIS community and the
generous funding grant from the QGIS organisation, I've just completed
and merged the task manager framework branch.
I'm very keen on feedback from QGIS devs, plugin authors, and users as
they start the play with this
23 matches
Mail list logo