i have a layer group containing 6 other layer groups that don’t overlap.
Now i start a getFeatureInfo request on my base layer group with a point that lies in one of my sub-layer groups and i can see in the log that all layers in all layer groups are queried.
Is this expected behavior? Or is there a way to configure geoserver that only the layers of the affected layer group are queried?
On Thu, Mar 6, 2014 at 9:51 AM, Wilhelm, Dirk <wilhelm@anonymised.com> wrote:
Hello,
i have a layer group containing 6 other layer groups that don't overlap.
Now i start a getFeatureInfo request on my base layer group with a point
that lies in one of my sub-layer groups and i can see in the log that all
layers in all layer groups are queried.
Is this expected behavior? Or is there a way to configure geoserver that
only the layers of the affected layer group are queried?
From your description, this is expected, in WMS a group is just a shortcut
way to get all the layers
that are contained in it, regardless of the nesting levels (basically the
sub-tree is flattened in
a long list)
That said you are welcome to look at the GetFeatureInfo implementation and check the query against the bounds of each layer … and ignore queries that have no chance of hitting content.
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
i have a layer group containing 6 other layer groups that don’t overlap.
Now i start a getFeatureInfo request on my base layer group with a point that lies in one of my sub-layer groups and i can see in the log that all layers in all layer groups are queried.
Is this expected behavior? Or is there a way to configure geoserver that only the layers of the affected layer group are queried?
From your description, this is expected, in WMS a group is just a shortcut way to get all the layers
that are contained in it, regardless of the nesting levels (basically the sub-tree is flattened in
a long list)