Thanks for your reply Arne.
1) We have the default 4X4 meta-tiling enabled and like you mentioned this is
not a perfect solution.
2) We tried this approach in the past got partial success. Our requirements are
too concerned with labeling than performance and we went to step 3 and
currently running into performance issues as expected.
I will retry the option with direct GWC url and if not I will directly use the
WMS for featureinfo.
Thanks again,
Ravi.
________________________________
From: Arne Kepp <[email protected]>
To: Ravi Pavuluri <[email protected]>
Cc: Geoserver-users <[email protected]>
Sent: Monday, October 8, 2012 1:48 AM
Subject: Re: [Geoserver-users] Geowebcache - Labeling & GetFeatureInfo
On 10/5/12 22:08 , Ravi Pavuluri wrote:
Hi,
>
>I am trying the latest Geoserver(2.2) and integrated
geowebcache. I am not sure if I am supposed to post it here or
in geowebcache forum. Please let me know.
>
geowebcache-users whould be more specific, but either one is valid.
>I had set the styling to label all features within geoserver sld
and also set the singleTile= true using openlayers to have label
shown all the time. It works as expected with just Geoserver and
openlayers. When I start using GWC, I am not really aware of any
way to force the label the way it was. Any tips are greatly
appreciated. Is duplicating the layer with no symbolization for
data, but just for labels a good idea?
>
Labels are duplicated because WMS requests are stateless, so one request
doesn't know what has been rendered in the other. When you view a cached.
You can do three things:
1) Increase metatiling factors so that it is less likely to occur in
places that you care about. This is the easy fix, but it doesn't
give you a perfect solution.
2) You can fix all the labels by calculating a point for each one
and then putting the labels in a separate layer and render only at
these points. Then create a layer group with both the actual data
and the layer group, and cache this combination.
3) Or you can display the layer with two SLDs. One for labels
(untiled, not cached) and one for the actual data. This will require
both the server and client to do more work.
>[This may be openlayers question. Please disregard if
inappropriate]
>Openlayers GetFeatureInfo is not working with multiple layers
when I had GWC enabled "Enable direct WMS integration" option
within Geoserver. Is this a known limitation or am I missing
something here?
>
Not sure, I would have expected it to work and forward requests without caching
them (there are just too many pixels, and the responses can be big). But you
can also do these requests directly against the WMS, OpenLayers doesn't require
you to configure it against a visible layer or anything like that.
-Arne ------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
