You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In creating the GetStyles response, the code should look at the LAYER's OPACITY as well as the CLASS STYLE's OPACITY to determine whether the fill-opacity CssParameter should be added to the Rule. To be consistent with the getMap and getLegendGraphic requests, the LAYER's OPACITY should override the CLASS STYLE's definition (should they both exist).
On our 6.0.1 version of Mapserver, we have introduced the code below in mapogcsld.c's msSLDGeneratePolygonSLD (in the section where it's dealing with the fill-opacity). I don't know if it's good enough or if there are farther-reaching ramifications to introducing this change than we are aware of. I simply provide it here as a starting point to illustrate what I'm talking about.
Similarly, stroke-opacity should be addressed; for both the PolygonSymbolizer (outlines) and LineSymbolizer (related issues of which are discussed in: #4132)
The text was updated successfully, but these errors were encountered:
In creating the GetStyles response, the code should look at the LAYER's OPACITY as well as the CLASS STYLE's OPACITY to determine whether the fill-opacity CssParameter should be added to the Rule. To be consistent with the getMap and getLegendGraphic requests, the LAYER's OPACITY should override the CLASS STYLE's definition (should they both exist).
On our 6.0.1 version of Mapserver, we have introduced the code below in mapogcsld.c's msSLDGeneratePolygonSLD (in the section where it's dealing with the fill-opacity). I don't know if it's good enough or if there are farther-reaching ramifications to introducing this change than we are aware of. I simply provide it here as a starting point to illustrate what I'm talking about.
Similarly, stroke-opacity should be addressed; for both the PolygonSymbolizer (outlines) and LineSymbolizer (related issues of which are discussed in: #4132)
The text was updated successfully, but these errors were encountered: