Re: [Qgis-user] How to display WMS legend (getLegendGraphic-request) in QGIS

[Jürgen E . Fischer]

Hi Astrid,

On Fri, 07. Dec 2012 at 09:51:57 +0100, Astrid Emde wrote:
> I am using WMS in QGIS and would like to diplay the legend from the
> getLegendGraphic-request in my application.
>
> Is there a possibility to do this?

I think there's no client support for that yet.   The server has support for
that and the webclient uses it, but the legend for the WMS.

We could probably replace the "standard" raster legend item with the
getlegendgraphcis response.

Jürgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de
committ(ed|ing) to Quantum GIS IRC: jef on FreeNode 


-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] How to open external links, interpret css or JavaScript from a WMS getFeatureInfo result

[Jürgen E . Fischer]

Hi Astrid,

On Fri, 07. Dec 2012 at 09:50:19 +0100, Astrid Emde wrote:
> I am using WMS in QGIS and get Information about my data through the
> getFeatureInfo-request. In the html-result of the request I have links to
> other websides or scripts and I refer to an external css-file.
> Unfortunately QGIS does not open the links and does not use the css.

Which version are you referring to?  In master you should be able to follow
links.  You can also print HTML responses.

> Looks like QGIS ignores the JavaScript Code too?
> Is there a possibility to enable QGIS to open the links,use the css and
> interpret JavaScript?

Not sure.  QGIS uses Qt's internal webkit to render the page.  Do you have a
public sample server to try that with?


Jürgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de
committ(ed|ing) to Quantum GIS IRC: jef on FreeNode 


-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] How to display WMS legend (getLegendGraphic-request) in QGIS

[Astrid Emde]

Am 07.12.2012 09:12, schrieb Jürgen E. Fischer:
> Hi Astrid,
>
> On Fri, 07. Dec 2012 at 09:51:57 +0100, Astrid Emde wrote:
>> I am using WMS in QGIS and would like to diplay the legend from the
>> getLegendGraphic-request in my application.
>>
>> Is there a possibility to do this?
> I think there's no client support for that yet.   The server has support for
> that and the webclient uses it, but the legend for the WMS.
>
> We could probably replace the "standard" raster legend item with the
> getlegendgraphcis response.
>
> Jürgen
>
Hello Jürgen,

thanks for your reply.

The Solution to use the getlegendgraphcis response if it exists sounds
good to me. Maybe it could be displayed in a separate frame in QGIS.

I am using QGIS 1.8-0

-- 

Mit freundlichen Grüßen

Astrid Emde


Where2B Konferenz 2012
13. Dezember 2012 in Bonn
www.where2b-conference.com


 Astrid Emde
 WhereGroup GmbH & Co.KG
 Eifelstraße 7
 53119 Bonn
 Germany

 Fon: +49(0)228 90 90 38 - 19
 Fax: +49(0)228 90 90 38 - 11

 astrid.e...@wheregroup.com
 www.wheregroup.com

 Folgen Sie der WhereGroup auf twitter: http://twitter.com/WhereGroup_com

Amtsgericht Bonn, HRA 6788
---
Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Olaf Knopp, Peter Stamm
---
 pgp-public key:
 http://pgp.mit.edu:11371/pks/lookup?search=0x06DA52D72D515284
  Signierte und/oder verschlüsselte Nachrichten sind sehr willkommen
  Signed and/or encrypted mail is highly appreciated

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] Let's discuss on a Mask feature

[haubourg]

Hi All, 
users often ask me how they can mask parts of their map that are not inside
their area of interest. 
As a quick an fast answer, we developped Mask plugin available on
repository.  It take selected objects of a polygon layer, and creates a new
memory layer, populated with a great rectangle with holes in place of
selected objects. We have that way a layer that can  be drawn on top of
others, masking features. 

*We miss two main features:
   - draw labels only for objects parts inside mask*
   - *have the ability to generate a mask on the fly when using Atlas tool
in Master.* That means, each time Map in composer in Atlas is zoomed on, we
would like to generate a map of coverage object. We would also like to be
able to generate a mask with buffer options to allow to show beiond strict
boundary of mask. 

*Do others need this?*

*Dear dev's, does that sound possible, and not too a CPU killer task? *I
guess intersecting all objects on screen with some complex polygons could be
hard. What about invalid polygons? Should we suggest simplifying mask
polygons on the fly?  

Please tell me about this, I would be happy to fund this If everybody agrees
with that need and implementation. 



--
View this message in context: 
http://osgeo-org.1560.n6.nabble.com/Let-s-discuss-on-a-Mask-feature-tp5021391.html
Sent from the Quantum GIS - User mailing list archive at Nabble.com.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] Add new selection to previous selected items

[Xan Vieiro]

Hi !!!
Is there a way to add a new selection to a previous selected items, instead
of create a new selection?
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Let's discuss on a Mask feature

[Vincent Picavet]

Hi,

> users often ask me how they can mask parts of their map that are not inside
> their area of interest.
> As a quick an fast answer, we developped Mask plugin available on
> repository.  It take selected objects of a polygon layer, and creates a new
> memory layer, populated with a great rectangle with holes in place of
> selected objects. We have that way a layer that can  be drawn on top of
> others, masking features.
> 
> *We miss two main features:
>- draw labels only for objects parts inside mask*
>- *have the ability to generate a mask on the fly when using Atlas tool
> in Master.* That means, each time Map in composer in Atlas is zoomed on, we
> would like to generate a map of coverage object. We would also like to be
> able to generate a mask with buffer options to allow to show beiond strict
> boundary of mask.

As to solve this, I though of a solution being redrawing a geometrical object 
in the composer on top of the map, based on the objects to mask. This needs 
implementation of a polygon object in the composer, which is not yet present. 
But it would probably be simpler than doing a full mask feature 
implementation.

We could also have a button in the composer to «create a mask for this map 
based on the currently selected features in the map window».

The only drawback to this approach is that the labels will be covered by the 
mask, and will appear truncated if part of it lies under the mask. I do not 
know if this would be a blocker.

Therefore the question is : do we need this in the main map window, or this 
solution for composer would be enough ?

We'd be glad to implement that in composer and Atlas if this is a good 
solution for you.

Vincent

> *Do others need this?*
> 
> *Dear dev's, does that sound possible, and not too a CPU killer task? *I
> guess intersecting all objects on screen with some complex polygons could
> be hard. What about invalid polygons? Should we suggest simplifying mask
> polygons on the fly?
> 
> Please tell me about this, I would be happy to fund this If everybody
> agrees with that need and implementation.
> 
> 
> 
> --
> View this message in context:
> http://osgeo-org.1560.n6.nabble.com/Let-s-discuss-on-a-Mask-feature-tp5021
> 391.html Sent from the Quantum GIS - User mailing list archive at
> Nabble.com. ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Let's discuss on a Mask feature

[HAUBOURG]

Hi Vincent,
 
> As to solve this, I though of a solution being redrawing a geometrical object 
> in
> the composer on top of the map, based on the objects to mask. This needs
> implementation of a polygon object in the composer, which is not yet
> present.
> But it would probably be simpler than doing a full mask feature
> implementation.

The mask feature is also needed in the main Map Canvas.  It would be better to 
implement a full Mask feature .

> 
> We could also have a button in the composer to  based on the currently selected features in the map window>.

No, because when exporting in batch mode with Atlas can't deal with a manual 
selection.
 - When Atlas is not activated, then composer Maps should only show current map 
state (with Mask ON or OFF). 
IMHO when several maps are in the composer, users wish to use mask only on some 
maps. If we want to keep actual workflow, that implies using the "Lock layer 
for this map" to show some layers or not on each map.   Then I see no other 
choice than materializing Mask as a layer. That layer  would have a special 
behavior:  it should be able to mask all labels of layers that lies under it, 
but not those lying on top of it. Options could be using a buffer and its size, 
simplify feature on the fly or not + threshold. 

That would allow a user to switch differents masks on and off, and to use them 
or not in different Composer maps. 
A memory layer would be fine for it.. BUT we need a way to save them along with 
the project. THAT implies we need to commit in CORE "Memory Layer Saver" 
features. (previously discussed here [0], but left opened)

 - When Atlas is activated, the idea is to let Atlas code generate a temporary 
mask layer fo each object of Coverage Layer, and suppress the mask layer each 
time a export iteration is done. Buffer and simplify options could be retyped 
in Atlas Panel and then passed as arguments to Mask classes.


> 
> The only drawback to this approach is that the labels will be covered by the
> mask, and will appear truncated if part of it lies under the mask. I do not
> know if this would be a blocker.
This is a BLOCKER, since this is what Mapinfo does, and this is not satisfying 
at all. People do workarounds like cookie cutter to destroy objects outside the 
mask. We loose the dynamic link with data and batch Atlas possibilities. 
 This is why I was asking devs on risks of it, and submitting the idea of 
simplifying the masks polygon. Warnings would be welcome if polygons have to 
much vertices and parts , along with  suggestions to mask less layers, and 
simplifies polygons.. 


> 
> Therefore the question is : do we need this in the main map window, or this
> solution for composer would be enough ?
> 
> We'd be glad to implement that in composer and Atlas if this is a good
> solution for you.


Sure ;-) but we need to find a global agreement on it, and we previously need 
to act what method is choosen to implement Memory Layer persistency in core. 
I'll be glad to fund this too.

 



[0] - 
http://osgeo-org.1560.n6.nabble.com/Memory-data-provider-persistence-td4108012.html
 
 

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Let's discuss on a Mask feature

[Vincent Picavet]

Hello,

> > As to solve this, I though of a solution being redrawing a geometrical
> > object in the composer on top of the map, based on the objects to mask.
> > This needs implementation of a polygon object in the composer, which is
> > not yet present.
> > But it would probably be simpler than doing a full mask feature
> > implementation.
> 
> The mask feature is also needed in the main Map Canvas.  It would be better
> to implement a full Mask feature .

Before going into details, I just want to point to the fact that generally 
speaking, I really do not like having a mask as a classic layer. Layers are 
data, and a mask is a graphical artefact that is only intended for 
visualization in a particular map output. Therefore, it should be something 
more like an overlay, if not a composer only feature.
This remark could be relativized if it has some complex implementation 
consequences.

This mask layer feature request is maybe time for a more general question : do 
we want something like «modifier layers» ? 
That would enable to do compositing for example, like in the gimp ? You could 
attach a «modifier» to a specific layer, which would add effects to the layer, 
but would not be a layer by itself, just added rendering options with 
parameters (a mask could be one of those modifiers).
Modifiers would not affect the way the features themselves are drawn, but the 
way the global resulting image is printed on screen for that layer.

> > We could also have a button in the composer to  > map based on the currently selected features in the map window>.
> 
> No, because when exporting in batch mode with Atlas can't deal with a
> manual selection. 

When exporting in batch mode for atlas then you have this mask generated 
automatically in the composer, based on the current coverage. That's exactly 
the same than for a mask layer, except that it's a composer geometry object, 
attached to a specific map.

> - When Atlas is not activated, then composer Maps should
> only show current map state (with Mask ON or OFF). IMHO when several maps
> are in the composer, users wish to use mask only on some maps. If we want
> to keep actual workflow, that implies using the "Lock layer for this map"
> to show some layers or not on each map.   Then I see no other choice than
> materializing Mask as a layer. That layer  would have a special behavior: 
> it should be able to mask all labels of layers that lies under it, but not
> those lying on top of it. Options could be using a buffer and its size,
> simplify feature on the fly or not + threshold.

I think the labelling point would be the most tricky to handle, as labels are 
normally drawn for the whole map afterwards. I do not know enough of the 
labelling part to discuss it in depth though, inputs welcome.

> That would allow a user to switch differents masks on and off, and to use
> them or not in different Composer maps. A memory layer would be fine for
> it.. BUT we need a way to save them along with the project. THAT implies
> we need to commit in CORE "Memory Layer Saver" features. (previously
> discussed here [0], but left opened)
> 
>  - When Atlas is activated, the idea is to let Atlas code generate a
> temporary mask layer fo each object of Coverage Layer, and suppress the
> mask layer each time a export iteration is done. Buffer and simplify
> options could be retyped in Atlas Panel and then passed as arguments to
> Mask classes.

Looks complicated to me, generating a data layer each time to have a display 
feature sounds a complex way of handling things. But maybe it is the most 
reasonable one.

> > The only drawback to this approach is that the labels will be covered by
> > the mask, and will appear truncated if part of it lies under the mask. I
> > do not know if this would be a blocker.
> 
> This is a BLOCKER, since this is what Mapinfo does, and this is not
> satisfying at all. People do workarounds like cookie cutter to destroy
> objects outside the mask. We loose the dynamic link with data and batch
> Atlas possibilities. This is why I was asking devs on risks of it, and
> submitting the idea of simplifying the masks polygon. Warnings would be
> welcome if polygons have to much vertices and parts , along with 
> suggestions to mask less layers, and simplifies polygons..

The label issue is again probably the most complicated one. If this is a 
blocker, we should go deeper into the way labelling works, as it's gonna be 
complex.

Before speaking about performance and technical aspect, we should agree on 
where in QGIS this kind of display-oriented «layer» should go : composer, some 
kind of modifier layer, overlay layer, or classic data layer, or another better 
solution ? 
We should generalize the problem, find a global concept, and verify that 
masking is covered by it.
Or is masking the only forseen feature of this kind ?

What do other think of it ?

Vincent

> 
> > Therefore the question is : do we need this in the main map window, or
> > this solution

Re: [Qgis-user] How to display WMS legend (getLegendGraphic-request) in QGIS

[Diego Mo]

Recently we build a little QGIS plugin to display WMS legends.
It work with QGIS 1.8, not yet with the nightly build.
We are going to release this plugin on the official repo.
At the moment, if you want test it, you can download it from this repo:
http://osgis.csi.it/qgis_plugin/csi_plugin_test.htm
 (remember to set "Show all
plugin, even those marked as experimental" in the python plugin option panel)
Thanks in advance for every feed back
Best regards

Diego Mo
CSI-Piemonte
Direzione Territorio e Ambiente


 >  _
 > 
 >  Il 7 dicembre 2012 alle 9.28 Astrid Emde  ha
 > scritto:
 >  > Am 07.12.2012 09:12, schrieb Jürgen E. Fischer:
 >  > > Hi Astrid,
 >  > >
 >  > > On Fri, 07. Dec 2012 at 09:51:57 +0100, Astrid Emde wrote:
 >  > >> I am using WMS in QGIS and would like to diplay the legend from the
 >  > >> getLegendGraphic-request in my application.
 >  > >>
 >  > >> Is there a possibility to do this?
 >  > > I think there's no client support for that yet. The server has support
 >  > > for
 >  > > that and the webclient uses it, but the legend for the WMS.
 >  > >
 >  > > We could probably replace the "standard" raster legend item with the
 >  > > getlegendgraphcis response.
 >  > >
 >  > > Jürgen
 >  > >
 >  > Hello Jürgen,
 >  >
 >  > thanks for your reply.
 >  >
 >  > The Solution to use the getlegendgraphcis response if it exists sounds
 >  > good to me. Maybe it could be displayed in a separate frame in QGIS.
 >  >
 >  > I am using QGIS 1.8-0
 >  >
 >  > --
 >  >
 >  > Mit freundlichen Grüßen
 >  >
 >  > Astrid Emde
 >  >
 >  > 
 >  > Where2B Konferenz 2012
 >  > 13. Dezember 2012 in Bonn
 >  > www.where2b-conference.com
 >  > 
 >  >
 >  > Astrid Emde
 >  > WhereGroup GmbH & Co.KG
 >  > Eifelstraße 7
 >  > 53119 Bonn
 >  > Germany
 >  >
 >  > Fon: +49(0)228 90 90 38 - 19
 >  > Fax: +49(0)228 90 90 38 - 11
 >  >
 >  > astrid.e...@wheregroup.com
 >  > www.wheregroup.com
 >  >
 >  > Folgen Sie der WhereGroup auf twitter: http://twitter.com/WhereGroup_com
 >  >
 >  > Amtsgericht Bonn, HRA 6788
 >  > ---
 >  > Komplementärin:
 >  > WhereGroup Verwaltungs GmbH
 >  > vertreten durch:
 >  > Olaf Knopp, Peter Stamm
 >  > ---
 >  > pgp-public key:
 >  > http://pgp.mit.edu:11371/pks/lookup?search=0x06DA52D72D515284
 >  > Signierte und/oder verschlüsselte Nachrichten sind sehr willkommen
 >  > Signed and/or encrypted mail is highly appreciated
 >  >
 >  > ___
 >  > Qgis-user mailing list
 >  > Qgis-user@lists.osgeo.org
 >  > http://lists.osgeo.org/mailman/listinfo/qgis-user
 >___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] How to display WMS legend (getLegendGraphic-request) in QGIS

[Astrid Emde]

Hello Diego,

thanks for the information. I tried the plugin and it is what I am
looking for.

It shows the legend of the layer that has the focus in the layertree. Nice.

Thanks for your help.

Astrid



Am 07.12.2012 13:16, schrieb Diego Mo:
> Recently we build a little QGIS plugin to display WMS legends.
> It work with QGIS 1.8, not yet with the nightly build.
> We are going to release this plugin on the official repo.
> At the moment, if you want test it, you can download it from this
> repo: http://osgis.csi.it/qgis_plugin/csi_plugin_test.htm (remember to
> set "Show all plugin, even those marked as experimental" in the python
> plugin option panel)
> Thanks in advance for every feed back
> Best regards
>  
> Diego Mo
> CSI-Piemonte
> Direzione Territorio e Ambiente
>  
>
>  
>
>  >  _
>
>  >  
>
>  >  Il 7 dicembre 2012 alle 9.28 Astrid Emde
>  ha scritto:
>
>  >  > Am 07.12.2012 09:12, schrieb Jürgen E. Fischer:
>
>  >  > > Hi Astrid,
>
>  >  > >
>
>  >  > > On Fri, 07. Dec 2012 at 09:51:57 +0100, Astrid Emde wrote:
>
>  >  > >> I am using WMS in QGIS and would like to diplay the legend
> from the
>
>  >  > >> getLegendGraphic-request in my application.
>
>  >  > >>
>
>  >  > >> Is there a possibility to do this?
>
>  >  > > I think there's no client support for that yet. The server has
> support for
>
>  >  > > that and the webclient uses it, but the legend for the WMS.
>
>  >  > >
>
>  >  > > We could probably replace the "standard" raster legend item
> with the
>
>  >  > > getlegendgraphcis response.
>
>  >  > >
>
>  >  > > Jürgen
>
>  >  > >
>
>  >  > Hello Jürgen,
>
>  >  >
>
>  >  > thanks for your reply.
>
>  >  >
>
>  >  > The Solution to use the getlegendgraphcis response if it exists
> sounds
>
>  >  > good to me. Maybe it could be displayed in a separate frame in QGIS.
>
>  >  >
>
>  >  > I am using QGIS 1.8-0
>
>  >  >
>
>  >  > --
>
>  >  >
>
>  >  > Mit freundlichen Grüßen
>
>  >  >
>
>  >  > Astrid Emde
>
>  >  >
>
>  >  > 
>
>  >  > Where2B Konferenz 2012
>
>  >  > 13. Dezember 2012 in Bonn
>
>  >  > www.where2b-conference.com
>
>  >  > 
>
>  >  >
>
>  >  > Astrid Emde
>
>  >  > WhereGroup GmbH & Co.KG
>
>  >  > Eifelstraße 7
>
>  >  > 53119 Bonn
>
>  >  > Germany
>
>  >  >
>
>  >  > Fon: +49(0)228 90 90 38 - 19
>
>  >  > Fax: +49(0)228 90 90 38 - 11
>
>  >  >
>
>  >  > astrid.e...@wheregroup.com
>
>  >  > www.wheregroup.com
>
>  >  >
>
>  >  > Folgen Sie der WhereGroup auf twitter:
> http://twitter.com/WhereGroup_com
>
>  >  >
>
>  >  > Amtsgericht Bonn, HRA 6788
>
>  >  > ---
>
>  >  > Komplementärin:
>
>  >  > WhereGroup Verwaltungs GmbH
>
>  >  > vertreten durch:
>
>  >  > Olaf Knopp, Peter Stamm
>
>  >  > ---
>
>  >  > pgp-public key:
>
>  >  > http://pgp.mit.edu:11371/pks/lookup?search=0x06DA52D72D515284
>
>  >  > Signierte und/oder verschlüsselte Nachrichten sind sehr willkommen
>
>  >  > Signed and/or encrypted mail is highly appreciated
>
>  >  >
>
>  >  > ___
>
>  >  > Qgis-user mailing list
>
>  >  > Qgis-user@lists.osgeo.org
>
>  >  > http://lists.osgeo.org/mailman/listinfo/qgis-user
>
>  >  
>
>
>
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user


-- 

Mit freundlichen Grüßen

Astrid Emde


Where2B Konferenz 2012
13. Dezember 2012 in Bonn
www.where2b-conference.com


 Astrid Emde
 WhereGroup GmbH & Co.KG
 Eifelstraße 7
 53119 Bonn
 Germany

 Fon: +49(0)228 90 90 38 - 19
 Fax: +49(0)228 90 90 38 - 11

 astrid.e...@wheregroup.com
 www.wheregroup.com

 Folgen Sie der WhereGroup auf twitter: http://twitter.com/WhereGroup_com

Amtsgericht Bonn, HRA 6788
---
Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Olaf Knopp, Peter Stamm
---
 pgp-public key:
 http://pgp.mit.edu:11371/pks/lookup?search=0x06DA52D72D515284
  Signierte und/oder verschlüsselte Nachrichten sind sehr willkommen
  Signed and/or encrypted mail is highly appreciated

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Let's discuss on a Mask feature

[HAUBOURG]

> 
> Before going into details, I just want to point to the fact that generally
> speaking, I really do not like having a mask as a classic layer. Layers are 
> data,
> and a mask is a graphical artefact that is only intended for visualization in 
> a
> particular map output. Therefore, it should be something more like an
> overlay, if not a composer only feature.
> This remark could be relativized if it has some complex implementation
> consequences.
Agreed, I maybe was thinking like a plugin developper, that have few capacities 
to change underlying implementations. 


> This mask layer feature request is maybe time for a more general question :
> do we want something like  ?

It is an option, but we should then apply modifiers to all layers concerned ? 
Another one is to jump a step beyond and go for a Arcgis - like and add 
something similar to what they call 'data blocks'. It is a way to handle multi 
map inside Mapcanvas. 
We could then apply modifiers (including masks) to that Data Block level. I 
must say it would really be more usable for multi maps composers. In current 
state, modifying multimaps is a pain, playing with data groups, composer and 
'lock layer options', with many window switches to tune Composer correctly. I 
would then appreciate to be able to switch to "Paper units" projection and be 
able to tune labeling exactly as it will be rendered on paper. 
IMHO, we are discussing here of a major evolution, touching API.. QGIS 3.0?  




> That would enable to do compositing for example, like in the gimp ? You
> could attach a  to a specific layer, which would add effects to the
> layer, but would not be a layer by itself, just added rendering options with
> parameters (a mask could be one of those modifiers).
> Modifiers would not affect the way the features themselves are drawn, but
> the way the global resulting image is printed on screen for that layer.

I'm not familiar with those tools. Isn't it too far away from the goal of 
keeping QGIS simple and very usable for common users? 

> > > We could also have a button in the composer to  > > this map based on the currently selected features in the map window>.
> >
> > No, because when exporting in batch mode with Atlas can't deal with a
> > manual selection.
> 
> When exporting in batch mode for atlas then you have this mask generated
> automatically in the composer, based on the current coverage. That's exactly
> the same than for a mask layer, except that it's a composer geometry object,
> attached to a specific map.

Sorry, I think I misunderstood previously. OK with you.


> 
> > - When Atlas is not activated, then composer Maps should only show
> > current map state (with Mask ON or OFF). IMHO when several maps are in
> > the composer, users wish to use mask only on some maps. If we want to
> > keep actual workflow, that implies using the "Lock layer for this map"
> > to show some layers or not on each map.   Then I see no other choice than
> > materializing Mask as a layer. That layer  would have a special behavior:
> > it should be able to mask all labels of layers that lies under it, but
> > not those lying on top of it. Options could be using a buffer and its
> > size, simplify feature on the fly or not + threshold.
> 
> I think the labelling point would be the most tricky to handle, as labels are
> normally drawn for the whole map afterwards. I do not know enough of the
> labelling part to discuss it in depth though, inputs welcome.

Well, Objects are already modified on the fly before labeling for some options :
See "labels only objects in extent" and "Label using perimeter" options. 
Geometries are clippes with BBOX of current mapcanvas, and then are used for 
labeling?
This induce new bugs I just reported yesterday : http://hub.qgis.org/issues/6835



> 
> > That would allow a user to switch differents masks on and off, and to
> > use them or not in different Composer maps. A memory layer would be
> > fine for it.. BUT we need a way to save them along with the project.
> > THAT implies we need to commit in CORE "Memory Layer Saver" features.
> > (previously discussed here [0], but left opened)
> >
> >  - When Atlas is activated, the idea is to let Atlas code generate a
> > temporary mask layer fo each object of Coverage Layer, and suppress
> > the mask layer each time a export iteration is done. Buffer and
> > simplify options could be retyped in Atlas Panel and then passed as
> > arguments to Mask classes.
> 
> Looks complicated to me, generating a data layer each time to have a display
> feature sounds a complex way of handling things. But maybe it is the most
> reasonable one.
Of course, any better implementation idea is welcome!

> 
> > > The only drawback to this approach is that the labels will be
> > > covered by the mask, and will appear truncated if part of it lies
> > > under the mask. I do not know if this would be a blocker.
> >
> > This is a BLOCKER, since this is what Mapinfo does, and this is not
> > satisfyi

[Qgis-user] Right-click does not work any more....

[Johan Nilsson]

I have QGIS 1.8 from
http://ppa.launchpad.net/ubuntugis/ubuntugis-unstable/ubuntu on Lucid
(Ubuntu 10.04LTS), and right-click on a layer does not work any more.  It
still work on my Ubuntu 12.04..
I can reach the function from the Menu--> Layer, but I don't know which
layer I really change property for
Nothing happen when I right-click in QGIS.

/Cheers
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Let's discuss on a Mask feature

[Alister Hood]

Hi,

> Date: Fri, 7 Dec 2012 13:10:40 +0100
> From: Vincent Picavet 
> To: HAUBOURG 
> Cc: "'qgis-user@lists.osgeo.org'" 
> Subject: Re: [Qgis-user] Let's discuss on a Mask feature
> Message-ID: <201212071310.41007.vincent...@oslandia.com>
> Content-Type: Text/Plain;  charset="iso-8859-1"
> 
> 
> Before speaking about performance and technical aspect, we should agree on
> where in QGIS this kind of display-oriented ?layer? should go : composer, some
> kind of modifier layer, overlay layer, or classic data layer, or another 
> better
> solution ?
> We should generalize the problem, find a global concept, and verify that
> masking is covered by it.
> Or is masking the only forseen feature of this kind ?
> 
> What do other think of it ?
> 
> Vincent

There may be some parallel with the discussion earlier in the year about 
graticules as map/composer decorations versus layers:
http://lists.osgeo.org/pipermail/qgis-developer/2012-May/020040.html
http://lists.osgeo.org/pipermail/qgis-developer/2012-May/020047.html
http://lists.osgeo.org/pipermail/qgis-developer/2012-July/020854.html

For ease of use on a basic level it seems to me that instead of being a 
separate layer it should be some sort of symbology option tied to the original 
map layer, similar to how it works in Mapinfo.

If you need a different feature in the layer to act as the mask for each page 
in an Atlas, I don't know the best way of controlling that, but I think the 
same problem would need to be solved for other things like map titles.

Alister
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user