#4131 closed defect (fixed)
Some CssParameter values ignored for PointSymbolizer
Reported by: | myOpenLayersUName | Owned by: | mapserverbugs |
---|---|---|---|
Priority: | normal | Milestone: | 6.2 release |
Component: | WMS Server | Version: | 6.0 |
Severity: | normal | Keywords: | SLD PointSymbolizer fill-opacity stroke-width stroke-opacity CssParameter |
Cc: | sdlime, tbonfort |
Description
The following values are being ignored in an SLD <PointSymbolizer> Mark's Fill and Stroke tags:
fill-opacity
stroke-opacity
stroke-width
Thomas Bonfort has proposed a fix for this which can be found at: http://trac.osgeo.org/mapserver/changeset/12904.
I have tested it with my example Point SLD and Mapserver is now applying the values to the display correctly.
If more info or background is necessary regarding this issue, please see: http://osgeo-org.1803224.n2.nabble.com/Some-PointSymbolizer-values-are-being-ignored-SLD-Syntax-problem-td7028772.html
My PointSymbolizer is defined as follows:
<StyledLayerDescriptor xmlns="http://www.opengis.net/sld" version="1.0.0" xsi:schemaLocation="http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <NamedLayer> <Name>Point</Name> <UserStyle> <FeatureTypeStyle> <Rule> <Name>Point</Name> <Title>Drawing layer</Title> <PointSymbolizer> <Graphic> <Mark> <WellKnownName>circle</WellKnownName> <Fill> <CssParameter name="fill">#FF0000</CssParameter> <CssParameter name="fill-opacity">0.4</CssParameter> </Fill> <Stroke> <CssParameter name="stroke">#000000</CssParameter> <CssParameter name="stroke-opacity">0.6</CssParameter> <CssParameter name="stroke-width">10.0</CssParameter> <CssParameter name="stroke-dasharray">solid</CssParameter> </Stroke> </Mark> <Size>40</Size> </Graphic> </PointSymbolizer> </Rule> </FeatureTypeStyle> </UserStyle> </NamedLayer> </StyledLayerDescriptor>
Change History (6)
comment:1 by , 12 years ago
Cc: | added |
---|---|
Component: | MapServer C Library → WMS Server |
Owner: | changed from | to
comment:2 by , 12 years ago
Cc: | added |
---|
comment:4 by , 12 years ago
Milestone: | → 6.2 release |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Closing. can be re-opened if there's a strong need to backport.
comment:5 by , 12 years ago
The "you" in comment:2 was referring to the original reporter, not you sdlime. Sorry :)
comment:6 by , 12 years ago
I guess that 'you' would be me ... I merely created the ticket as requested by Thomas Bonfort in the thread I started regarding this issue when he provided the changeset link in one of the posts. If the fix is already in the source I'm not looking for anything else. We have already introduced his suggested change into our source.
Sorry if I misunderstood what he was asking me to do or filled this in wrong somehow when I created it. Feel free to give me some indication how I should have done this for my future reference.
My understanding is that Thomas already implemented and committed a fix for this in the development version of the source tree (trunk r12904). This fix will be released in v6.2.
What else needs to be done for this ticket to be closed? Are you expecting this to be backported to the 6.0.x stable branch?