Hi Andrew, FeatureTypeStyle is each drawn into its own buffer which is then merged during composing the final image.
- FeaureTypeStyles are used in the order defined - If this default order is not desired there are some vendor options for greater control of z-order - You can adjust the alpha and blending effects when buffers are merged as a special effect - You can also control z-order by introducing filtering (to control what order features are drawn in within a z-order). Best documented in the GeoServer manual on "sld extensions". - https://docs.geoserver.org/latest/en/user/styling/sld/extensions/z-order/index.html And with pictures here: - https://docs.geoserver.org/latest/en/user/styling/ysld/reference/featurestyles.html#drawing-order -- Jody Garnett On May 27, 2024 at 6:20:22 PM, Andrew Hughes <ahhug...@gmail.com> wrote: > Hi All, > > Im looking to know if it is possible to control the rendering/z order in > the following: > > Geoserver: > + Group Layer (mapbox vector tile, pbf) > + Layer A > + Layer B > > Given both Layer A and Layer B have a common field called > "access_code".... and values that I would like rendered (top first)... > 1. access_code = Restricted > 2. access_code = Approved with Conditions > 3. access_code = Approved > > And, the client is OpenLayers. > > We would like access_code = Restricted always on top (regardless of being > in A or B) and so forth.. > > Is there an SLD/CSS option that will control the sorting/ordering of the > data so that it streams out the pbf and rendered in such an order? or > perhaps we need to split Layer A and B into a total of 6 layers within the > group layer... > > Layer A - Restricted > Layer B - Restricted > Layer A - Approved with Conditions > Layer B - Approved with Conditions > Layer A - Approved > Layer B - Approved > > Or.... something else? or nothing else will work? > > Any help would be greatly appreciated. > > Cheers, > Andrew > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
