[Geoserver-users] wmsGetFeatureInfo Request in 2.5 doesnt work on TextSymbolizers

GeoServer GeoServer User
1

Hi,
So we recently upgraded Geoserver to version 2.5, and I noticed the change
in WMSGetFeatureInfo requests. Does anyone know if there is a way to get the
request to work when a user clicks on a text symbolizer?( it use to before
this update)

We currently use custom fonts for symbols, and I am aware of TTF Marks in
point symbolizers, but can not use them because then I lose the vendor
options available to Text symbolizers.

So basically I lose click for text, or I lose the "priority" and
"spaceAround" options I use to de-clutter data.

Any ideas?

(Also just in case someone asks why we upgrade to version 2.5, apparently
it's needed for a specific plugin)

Thanks,
-Will

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wmsGetFeatureInfo-Request-in-2-5-doesnt-work-on-TextSymbolizers-tp5136800.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

On Wed, Apr 23, 2014 at 10:35 PM, willucf <willpettyucf@anonymised.com> wrote:

Hi,
So we recently upgraded Geoserver to version 2.5, and I noticed the change
in WMSGetFeatureInfo requests. Does anyone know if there is a way to get
the
request to work when a user clicks on a text symbolizer?( it use to before
this update)

Actually we never supported the "click" on text symbolizers (or any
symbolizers,
really), we just had a search area around the point/line/polygon used for
labelling,
we were just doing a bbox query in the underlying data source.

But you're right, if now a layer only has a text symbolizer (one that does
not
paint the underlying geometry), we won't catch anything
at all, to get results back we need to modify the code and force the
rendering
subsystem to paint the point/line/polygon from which the label originates.

Could you open a ticket on jira.codehaus.org/browse/GEOS (if you don't have
an account,
get one at xircles.codehaus.org)?

We currently use custom fonts for symbols, and I am aware of TTF Marks in
point symbolizers, but can not use them because then I lose the vendor
options available to Text symbolizers.

So basically I lose click for text, or I lose the "priority" and
"spaceAround" options I use to de-clutter data.

Any ideas?

You can force GeoServer to use the old GetFeatureInfo subsystem by adding
the -Dorg.geoserver.wms.featureinfo.render.enabled=false parameter to the
JVM used by GeoServer (how you do that, depends on what kind of install
you have).

(Also just in case someone asks why we upgrade to version 2.5, apparently
it's needed for a specific plugin)

Hmm.. uh? Not sure which plugin requires 2.5, I'd be curious to know :slight_smile:

Cheers
Andrea

--

Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

3

Hopefully I'll get some time tomorrow to create an account and open that jira
ticket.
In the mean time I found a workable solution.
I added a point symbolizer on top of the text symbolizers that is
essentially an invisible circle.
It does not work if the stroke width or opacity of the circle is set to 0,
but does with a value of .1, and the circle can not be seen.

Thanks,
-Will

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wmsGetFeatureInfo-Request-in-2-5-doesnt-work-on-TextSymbolizers-tp5136800p5136807.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

4

That is a tough one, consider rendering a mark that is completely transparent? Not sure if that would trick the new get feature info implementation. I understand the old implementation is still available as an option so you should not fear upgrading.

Andrea I could not find your him about using -Dorg.geoserver.wms.featureinfo.render.enabled=false in the user manual, was I just looking in the wrong spot?

···

Jody Garnett

On Thu, Apr 24, 2014 at 6:35 AM, willucf <willpettyucf@anonymised.com> wrote:

Hi,
So we recently upgraded Geoserver to version 2.5, and I noticed the change
in WMSGetFeatureInfo requests. Does anyone know if there is a way to get the
request to work when a user clicks on a text symbolizer?( it use to before
this update)

We currently use custom fonts for symbols, and I am aware of TTF Marks in
point symbolizers, but can not use them because then I lose the vendor
options available to Text symbolizers.

So basically I lose click for text, or I lose the “priority” and
“spaceAround” options I use to de-clutter data.

Any ideas?

(Also just in case someone asks why we upgrade to version 2.5, apparently
it’s needed for a specific plugin)

Thanks,
-Will

–
View this message in context: http://osgeo-org.1560.x6.nabble.com/wmsGetFeatureInfo-Request-in-2-5-doesnt-work-on-TextSymbolizers-tp5136800.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform

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

5

On Thu, Apr 24, 2014 at 3:28 AM, Jody Garnett <jody.garnett@anonymised.com>wrote:

That is a tough one, consider rendering a mark that is completely
transparent? Not sure if that would trick the new get feature info
implementation. I understand the old implementation is still available as
an option so you should not fear upgrading.

Andrea I could not find your him about using -Dorg.geoserver.wms.
featureinfo.render.enabled=false in the user manual, was I just looking
in the wrong spot?

No, it's not documented because I want people to use it only as a last
resort, and the old implementation will be removed once we stop
getting issues reports on the new one. Please keep it that way.

Cheers
Andrea

--

Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------