On Thu, 25 Feb 2021 at 14:16, Andrea Aime <[email protected]> wrote:
> I was thinking the same. In WMS GeoServer treats bounding boxes are purely > informative, a way for the client to > get in the right viewing area for the layer, but would respond to any > request outside of them. > They are not enforced, you can check by restricting the bbox and using the > map preview... it should completely ignore it. > > But each individual layer is correctly defined with a bounding box and doesn't display anything outside it's bounds. But when I put them in a layer group I get back data that is not in either of the layers' bounds. Should the two layers not be handled separately? rather than being added together with an expanded bounding box? > GWC defines the grid subsets based on those boxes for sure, and might > refuse to serve outside of those. > Looking at your pictures, it would even seem it intersects with tile > boxes, and returns only part of the data? > But once it's a group, the restriction is the box of the group, the one of > the layers is likely ignored (GWC does not even know the "thing" is a > layer). > > GWC isn't involved here and the tiling in the background is also unrelated (other than being what makes up the image pyramid store the two layers are published from). If you wanted separate bboxes, wouldn’t you have to serve separate layers? >> >> >> > I really want to only add one layer for the two areas that are defined as different layers. Ian
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
