On 23 February 2017 at 17:06, Andrea Peri wrote:
> Hi,
> we at Tuscany Region in 2013 fundedthe adding of the support of scale
> legend in the wms provider.
> That (if I remenber was added to the 2.2 or 2.4 version of qgis).
>
> These are the commit for that adding:
>
> https://github.com/qgis/QGI
Hi Nathan I find only this commit.
https://github.com/qgis/QGIS/commit/836e1a86368f9eace236d24ba40b7af77a6bc63d
But it speak of
don't refresh legend symbology everytime the extent changes
I'm not so skill on qgis code to understand what it do.
Our feture was for a retrieving of the new legend w
Unfortunatelly no.
:(
A.
2017-02-23 8:10 GMT+01:00 Nathan Woodrow :
> Do you have the commit where it was removed? That would normally have the
> message on why.
>
> Nathan
>
>
> On Thu, 23 Feb 2017 5:06 pm Andrea Peri wrote:
>>
>> Hi,
>> we at Tuscany Region in 2013 fundedthe adding of the su
Do you have the commit where it was removed? That would normally have the
message on why.
Nathan
On Thu, 23 Feb 2017 5:06 pm Andrea Peri wrote:
> Hi,
> we at Tuscany Region in 2013 fundedthe adding of the support of scale
> legend in the wms provider.
> That (if I remenber was added to the 2.2
Hi,
we at Tuscany Region in 2013 fundedthe adding of the support of scale
legend in the wms provider.
That (if I remenber was added to the 2.2 or 2.4 version of qgis).
These are the commit for that adding:
https://github.com/qgis/QGIS/commit/8fb20f038d9d6c67bafc932ccea1d688ef2d5363
https://githu
Sure
A qua, 22/02/2017, 20:14, Nyall Dawson escreveu:
> On 21 February 2017 at 21:04, Alexandre Neto
> wrote:
> > Maybe I'm missing something here, but seems that the Map Settings
> variables
> > of map items in the print composer are not being updated when the map
> item
> > changes.
> >
> > I
On 7 February 2017 at 18:52, Nyall Dawson wrote:
> Hi all,
>
> Following up on one of the points raised by John Hawkison (author of
> the famous "my first weekend with QGIS" email), I'd like to raise
> discussion about renaming all use of outline/border throughout QGIS to
> "stroke".
Done in
htt
On 21 February 2017 at 21:04, Alexandre Neto wrote:
> Maybe I'm missing something here, but seems that the Map Settings variables
> of map items in the print composer are not being updated when the map item
> changes.
>
> It seems to be just a display problem. using one of the variables somewhere
On 22 February 2017 at 21:06, Daan Goedkoop wrote:
> Yes, apparently the dissolve tool merges adjacent geometries into a
> single "part" when operating on polygons, but not when operating on
> lines.
>
Perhaps you're looking for the "merge lines" tool? That will join the
parts of a multilinestrin
Matthias Kuhn wrote:
> I think having 2.18.x and 3.2.x available in parallel for an extended
> period is a good thing (...) but with a clear deadline for 2.18 so we are
> not stuck in the 2 release series forever.
and Jürgen E. Fischer wrote:
> When a new LTR is released we have a period where the
Plugin Hotspot Analysis approval by pcav.
The plugin version "[1181] Hotspot Analysis 0.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/HotspotAnalysis/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https
Oh, I didn't get that you want to actually change the geometry itself not
its style.
I usually don't play with geometry for representation purpose, or sometimes
I store alternate geometries but I keep the original one.
Are you aware of the geometry generator renderer ? You could apply a
translation
Hi all,
in QGIS 2.18.3, apparently concentration maps are not displayed if
rendering effects are enabled: does someone please confirm?
All the best, and thanks.
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?d
Plugin QGIS GML Application Schema Toolbox approval by pcav.
The plugin version "[1046] QGIS GML Application Schema Toolbox 1.0.2" is now
approved
Link: http://plugins.qgis.org/plugins/gml_application_schema_toolbox/
___
Qgis-developer mailing list
Qgis
Hi,
working with Field menu range in QGIS 2.18 I notice that the problem
is still there despite the introduction of costraint:
say that i want to set a range for an integer field
called "numfield" with
min value 1
max value 5
step 1
at this point i would expect that QGIS only accepts "1 2 3
Hi Harrissou,
On Wed, 22. Feb 2017 at 15:22:11 +0100, DelazJ wrote:
> I think there usually (ok! it happens only once) is an overlap between two
> LT releases: 2.8 was maintained few months after 2.14 (I think it was
> stopped when 2.16 was released).
Yes.
We build for two package repositories.
Personally I would like to see a 3.x release become LTR as soon as
possible. 3.0 should be skipped because despite it's incredibly high
stability there could potentially still be problems. So the next in line
is 3.2.
I think having 2.18.x and 3.2.x available in parallel for an extended
period is a
It's an option, too. The question is which one is supposed to be more mature,
stable and polished: 3.2.5 or 3.4.0. Anyway, in both cases the lifetime of
2.18 LTR seems to be clear now.
Dnia środa, 22 lutego 2017 15:22:11 DelazJ pisze:
> Hi,
>
> I think there usually (ok! it happens only once) i
Hi Regis,
I would assume that in this use case the user would not be modifying the
source polygons, but would make a copy of them which could be a memory
layer and then resize them. I mentioned resizing small features so that
they visibly would be better shown on the map, but the other use case wo
Hi,
I think there usually (ok! it happens only once) is an overlap between two
LT releases: 2.8 was maintained few months after 2.14 (I think it was
stopped when 2.16 was released) -
http://qgis.org/en/site/getinvolved/development/roadmap.html
So following that logic, 3.2 would be released in janu
Dnia środa, 22 lutego 2017 14:45:07 Borys Jurgiel pisze:
> Other options would be: retire 2.18 LTR in January 2018 or postpone 3.2
> until June 2018. Both look unacceptable for me.
I mean to* me of course - they look to me, not 'unacceptable for me'. I'm
sorry :)
Regards,
Borys
_
Thanks Jürgen, for maintaining this
Arnaud
Le 22/02/2017 à 13:58, Jürgen E. Fischer a écrit :
Hi Arnaud,
On Wed, 22. Feb 2017 at 13:39:11 +0100, Jürgen E. Fischer wrote:
On Wed, 22. Feb 2017 at 11:15:46 +0100, Arnaud Morvan wrote:
Where can I found this daily osgeo4w installer ?
osgeo4w.
Tim Sutton said:
> Personally I was hoping for 2.18 LTR to last from June 2017 to June 2018
> and then releasing 3.2 In June 2018.
>
> * retire 2.14 in June 2017
> * 2.18 becomes LTR from June 2017 to ***June*** 2018
> * 3.0 feature freeze in July 2017
> * release 3.0 in Sept 2017
> * release
Hi Luca,
On Wed, 22. Feb 2017 at 13:54:07 +0100, Luca Mandolesi wrote:
> Is there a possibility to have a QGIS3 "Master" Standalone installer to
> download it and begin to porting my own plugins from Python27 to Python3?
>
> My Osgeo4W is my work enviroment and I'm afraid to destroy anything. I'm
Hi Arnaud,
On Wed, 22. Feb 2017 at 13:39:11 +0100, Jürgen E. Fischer wrote:
> On Wed, 22. Feb 2017 at 11:15:46 +0100, Arnaud Morvan wrote:
> > Where can I found this daily osgeo4w installer ?
> osgeo4w.osgeo.org.
For the dailies/nightlies. It has:
qgis-ltr (2.14 release)
qgis-ltr-dev (nightl
Luca I have 2.14, 2.18 and master from osgeo4w. No issues at all ;)
giovanni
Il 22 feb 2017 13:54, "Luca Mandolesi" ha scritto:
> Is there a possibility to have a QGIS3 "Master" Standalone installer to
> download it and begin to porting my own plugins from Python27 to Python3?
>
> My Osgeo4W is
Is there a possibility to have a QGIS3 "Master" Standalone installer to
download it and begin to porting my own plugins from Python27 to Python3?
My Osgeo4W is my work enviroment and I'm afraid to destroy anything. I'm so
scared of P3!!! Best regards. Luca
_
I can try. Although I don't have your eye for details. :-)
A qua, 22/02/2017, 12:01, DelazJ escreveu:
> Hi,
>
> 2017-02-22 0:38 GMT+01:00 Alexandre Neto :
>
> According to the latest news, it seems that there will make sense to have
> a 2.18 Documentation release...
>
> Sorry for trying to "rush
Hi Arnaud,
On Wed, 22. Feb 2017 at 11:15:46 +0100, Arnaud Morvan wrote:
> Where can I found this daily osgeo4w installer ?
osgeo4w.osgeo.org.
I thought there would be NSIS installers too at the url you pointed at.
Probably a space issue. I'll investigate.
Jürgen
--
Jürgen E. Fischer
Hi,
2017-02-22 0:38 GMT+01:00 Alexandre Neto :
> According to the latest news, it seems that there will make sense to have
> a 2.18 Documentation release...
>
> Sorry for trying to "rush" it to 3.0. Or will it be 3.2?
>
> Anyway, I am going to put some effort in fixing 2.x issues in the user's
>
Yes, apparently the dissolve tool merges adjacent geometries into a
single "part" when operating on polygons, but not when operating on
lines.
2017-02-22 11:46 GMT+01:00 Marco Grisolia :
> Hmm maybe I'm wrong, but I think it will only return singleparts without
> taking care of an adjacency criter
Hmm maybe I'm wrong, but I think it will only return singleparts without
taking care of an adjacency criterion (even if ran after the dissolving
operation).
Marco
2017-02-22 11:37 GMT+01:00 Anita Graser :
> You can run multiplart to singlepart afterwards.
>
>
> On Wed, Feb 22, 2017 at 11:18 AM, r
You can run multiplart to singlepart afterwards.
On Wed, Feb 22, 2017 at 11:18 AM, roy roy wrote:
> Hi Anita, that does not do what Marco is asking for, because you get a
> multipart geometry;
>
> he needs a linestring geometry I think...
>
> Il 22/02/2017 11:10, Anita Graser ha scritto:
>
> Hi
Thanks to all for the answers! I really appreciate.
@Daan, actually it should work for all the features for a specific field (I
set it inside the code, but it may easily become an input parameter). So,
after the setting of a specific field, the code will dissolve all the
features which have the sa
Hi Anita, that does not do what Marco is asking for, because you get a
multipart geometry;
he needs a linestring geometry I think...
Il 22/02/2017 11:10, Anita Graser ha scritto:
Hi Marco,
The Dissolve tool already has a "unique fields" option. It sounds like you are
reinventing that.
Best wi
Hi,
Arnaud, you might find it at http://qgis.org/en/site/forusers/download.html
Harrissou
2017-02-22 11:15 GMT+01:00 Arnaud Morvan :
> Hi all,
>
> Where can I found this daily osgeo4w installer ?
>
> Is it here : http://qgis.org/downloads/weekly/?C=M;O=D
>
> Last build seems dated from : 14-Nov-
Hi all,
Where can I found this daily osgeo4w installer ?
Is it here : http://qgis.org/downloads/weekly/?C=M;O=D
Last build seems dated from : 14-Nov-2016
Is there a place where we can get more recent build for windows ?
Regards
Arnaud Morvan
Ingénieur logiciel
Tél: +33 (0)4 58 48 20 32
Camp
Hi Marco,
there is an OGR geoalgorithm that seems to do what you are describing
in QGIS Processing (Dissolve polygons) maybe its easy to adapt it
to also work with lines ...
Il 22/02/2017 10:32, Marco Grisolia ha scritto:
Hi,
I recently answered to a question on GIS StackExchange [0]. In this q
Hi Marco,
The Dissolve tool already has a "unique fields" option. It sounds like you
are reinventing that.
Best wishes,
Anita
On Wed, Feb 22, 2017 at 10:32 AM, Marco Grisolia
wrote:
> Hi,
> I recently answered to a question on GIS StackExchange [0]. In this
> question, the asker was looking
Hello,
the example on StackExchange seems to do this for the currently
selected features.
It might also be desirable to do this for an entire layer, e.g. join
at all places where exactly two line features are adjacent. (I think
v.build.polylines does this, but apparently it is not available from
Hi,
I recently answered to a question on GIS StackExchange [0]. In this
question, the asker was looking for a way for dissolving features using an
adjacency criterion instead of using common attribute field (please, follow
the link below for a better understanding). This feature is already
availabl
41 matches
Mail list logo