[Geoserver-users] Labelling - layer group

GeoServer GeoServer User
1

Hi List,
I’m getting some anomalous behaviour and figured I’d ask if it was as-designed or if it seems like a bug.

I have two layers coming from two different tables. One contains Primary Roads (green), the other A-Roads (red).
Each has a single SLD which draws the features and labels them. The only different between the two SLD’s is the colours.

I’m using the grouping feature:
yes

Any given road section is only geographically represented once between these two layers - there is no overlapping. But from a labelling perspective a road’s name can appear in both layers.

So the A444 could be a mixture of primary road and A-Road as thus:

-------====-------

My issue is that the grouping seems to happen across layers. So I have a Primary road (A444) being labelled with the colour scheme of the A-road because there are three sections of A444 in the A-road layer (there are 63 in the Primary Road layer).

Inline images 1

The A-Road A444 sections are all 60 pixels north under “Nuneaton”. The label should be Primary Road green.

Should this happen? I expected the grouping to only happen within a single layer, not across layers. There’s no mention of which way it’s supposed to work in the help.

Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

2

Yes, the label grouping in GeoServer applies based ONLY on the text of the label, originating layer is not considered. Labels that are positioned earlier in the rendering process get priority over those that are positioned later, so you could put a label-only copy of the primary road layer low in your drawing stack to make it more likely for those labels to appear than the lower-priority features.

image.png

···

On Fri, Jun 28, 2013 at 6:53 AM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:

Hi List,
I’m getting some anomalous behaviour and figured I’d ask if it was as-designed or if it seems like a bug.

I have two layers coming from two different tables. One contains Primary Roads (green), the other A-Roads (red).
Each has a single SLD which draws the features and labels them. The only different between the two SLD’s is the colours.

I’m using the grouping feature:
yes

Any given road section is only geographically represented once between these two layers - there is no overlapping. But from a labelling perspective a road’s name can appear in both layers.

So the A444 could be a mixture of primary road and A-Road as thus:

-------====-------

My issue is that the grouping seems to happen across layers. So I have a Primary road (A444) being labelled with the colour scheme of the A-road because there are three sections of A444 in the A-road layer (there are 63 in the Primary Road layer).

Inline images 1

The A-Road A444 sections are all 60 pixels north under “Nuneaton”. The label should be Primary Road green.

Should this happen? I expected the grouping to only happen within a single layer, not across layers. There’s no mention of which way it’s supposed to work in the help.

Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

3

Hi Jonathan,

Although not a desirable effect, this is the expected behaviour. We’re experiencing the exact same behaviour in one of our maps. The vendorOption “group” actually groups the geometries based on the label attribute only, but does not take into account the other attributes that relate to the geometries and that are used for the visualisation.

For another project we pre-processed the Tele Atlas data first, grouping the geometries not only by name, but also other attributes (e.g. “Form of Way”, “Network Class”, “Direction of Traffic Flow”). In order not to have one geometry containing all the “High Streets” in a country, we then performed an ST_Dump. In short: pre-process the data and don’t rely on the vendorOption “group” for this kind of visualisation.

Another approach could be to refactor to the code in GeoServer so the vendorOption “group” actually takes into account the other attrributes that are declared in the ogc:filter tags of the .

All the best,

Edward

From: jonathanmoules@anonymised.com
Date: Fri, 28 Jun 2013 11:53:20 +0100
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Labelling - layer group

Hi List,
I’m getting some anomalous behaviour and figured I’d ask if it was as-designed or if it seems like a bug.

I have two layers coming from two different tables. One contains Primary Roads (green), the other A-Roads (red).
Each has a single SLD which draws the features and labels them. The only different between the two SLD’s is the colours.

I’m using the grouping feature:
yes

Any given road section is only geographically represented once between these two layers - there is no overlapping. But from a labelling perspective a road’s name can appear in both layers.

So the A444 could be a mixture of primary road and A-Road as thus:

-------====-------

My issue is that the grouping seems to happen across layers. So I have a Primary road (A444) being labelled with the colour scheme of the A-road because there are three sections of A444 in the A-road layer (there are 63 in the Primary Road layer).

Inline images 1

The A-Road A444 sections are all 60 pixels north under “Nuneaton”. The label should be Primary Road green.

Should this happen? I expected the grouping to only happen within a single layer, not across layers. There’s no mention of which way it’s supposed to work in the help.

Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users

4

Hi Jonathan,

Although not a desirable effect, this is the expected behaviour. We’re experiencing the exact same behaviour in one of our maps. The vendorOption “group” actually groups the geometries based on the label attribute only, but does not take into account the other attributes that relate to the geometries and that are used for the visualisation.

For another project we pre-processed the Tele Atlas data first, grouping the geometries not only by name, but also other attributes (e.g. “Form of Way”, “Network Class”, “Direction of Traffic Flow”). In order not to have one geometry containing all the “High Streets” in a country, we then performed an ST_Dump. In short: pre-process the data and don’t rely on the vendorOption “group” for this kind of visualisation.

Another approach could be to refactor to the code in GeoServer so the vendorOption “group” actually takes into account the other attrributes that are declared in the ogc:filter tags of the .

All the best,

Edward

From: jonathanmoules@anonymised.com
Date: Fri, 28 Jun 2013 11:53:20 +0100
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Labelling - layer group

Hi List,
I’m getting some anomalous behaviour and figured I’d ask if it was as-designed or if it seems like a bug.

I have two layers coming from two different tables. One contains Primary Roads (green), the other A-Roads (red).
Each has a single SLD which draws the features and labels them. The only different between the two SLD’s is the colours.

I’m using the grouping feature:
yes

Any given road section is only geographically represented once between these two layers - there is no overlapping. But from a labelling perspective a road’s name can appear in both layers.

So the A444 could be a mixture of primary road and A-Road as thus:

-------====-------

My issue is that the grouping seems to happen across layers. So I have a Primary road (A444) being labelled with the colour scheme of the A-road because there are three sections of A444 in the A-road layer (there are 63 in the Primary Road layer).

Inline images 1

The A-Road A444 sections are all 60 pixels north under “Nuneaton”. The label should be Primary Road green.

Should this happen? I expected the grouping to only happen within a single layer, not across layers. There’s no mention of which way it’s supposed to work in the help.

Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users

5

Thanks for the clarification and information both. I’ll just make do I guess; most users aren’t going to be paying that much attention, lets be honest. :slight_smile:

Cheers,
Jonathan

On 29 June 2013 11:30, Edward Mac Gillavry <emacgillavry@anonymised.com> wrote:

Hi Jonathan,

Although not a desirable effect, this is the expected behaviour. We’re experiencing the exact same behaviour in one of our maps. The vendorOption “group” actually groups the geometries based on the label attribute only, but does not take into account the other attributes that relate to the geometries and that are used for the visualisation.

For another project we pre-processed the Tele Atlas data first, grouping the geometries not only by name, but also other attributes (e.g. “Form of Way”, “Network Class”, “Direction of Traffic Flow”). In order not to have one geometry containing all the “High Streets” in a country, we then performed an ST_Dump. In short: pre-process the data and don’t rely on the vendorOption “group” for this kind of visualisation.

Another approach could be to refactor to the code in GeoServer so the vendorOption “group” actually takes into account the other attrributes that are declared in the ogc:filter tags of the .

All the best,

Edward

From: jonathanmoules@anonymised.com
Date: Fri, 28 Jun 2013 11:53:20 +0100
To: geoserver-users@anonymised.comrge.net
Subject: [Geoserver-users] Labelling - layer group

Hi List,
I’m getting some anomalous behaviour and figured I’d ask if it was as-designed or if it seems like a bug.

I have two layers coming from two different tables. One contains Primary Roads (green), the other A-Roads (red).
Each has a single SLD which draws the features and labels them. The only different between the two SLD’s is the colours.

I’m using the grouping feature:
yes

Any given road section is only geographically represented once between these two layers - there is no overlapping. But from a labelling perspective a road’s name can appear in both layers.

So the A444 could be a mixture of primary road and A-Road as thus:

-------====-------

My issue is that the grouping seems to happen across layers. So I have a Primary road (A444) being labelled with the colour scheme of the A-road because there are three sections of A444 in the A-road layer (there are 63 in the Primary Road layer).

Inline images 1

The A-Road A444 sections are all 60 pixels north under “Nuneaton”. The label should be Primary Road green.

Should this happen? I expected the grouping to only happen within a single layer, not across layers. There’s no mention of which way it’s supposed to work in the help.

Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.