Hi all,

I have been tinkering around with a SLD style for relatively simple data served 
from PostGIS database. Basicly It is collection of multilinestring-type 
geometries, and style should changes color and width of lines according to 
value in certain column. There are six possible values. For some unknown reason 
five of these rules work, but one of them just doesn't. All other lines are 
drawn correctly, but no style is applied to line segments containing this 
value. Rule itself is completely identical to other six, only difference being 
in color of the line. Example below.

<!-This one doesn't draw -->
<FeatureTypeStyle>
        <Rule>
          <Name>Kovat asfalttibetonit (AB)</Name>
          <Title>Kovat asfalttibetonit (AB)</Title>
          <ogc:Filter>
            <ogc:PropertyIsEqualTo>
              <ogc:PropertyName>paalluok</ogc:PropertyName>
              <ogc:Literal>10</ogc:Literal>
            </ogc:PropertyIsEqualTo>
          </ogc:Filter>
          <LineSymbolizer>
            <Stroke>
              <CssParameter name="stroke">#FF0000</CssParameter>
              <CssParameter name="stroke-width">3</CssParameter>
              <CssParameter name="stroke-opacity">1</CssParameter>
            </Stroke>
          </LineSymbolizer>
        </Rule>
</FeatureTypeStyle>

<!-This one works correctly -->
<FeatureTypeStyle>
          <Rule>
          <Name>Pehme&#228;t asfalttibetonit (PAB)</Name>
          <Title>Pehme&#228;t asfalttibetonit (PAB)</Title>
          <ogc:Filter>
            <ogc:PropertyIsEqualTo>
              <ogc:PropertyName>paalluok</ogc:PropertyName>
              <ogc:Literal>20</ogc:Literal>
            </ogc:PropertyIsEqualTo>
          </ogc:Filter>
          <LineSymbolizer>
            <Stroke>
              <CssParameter name="stroke">#0070FF</CssParameter>
              <CssParameter name="stroke-width">3</CssParameter>
              <CssParameter name="stroke-opacity">1</CssParameter>
            </Stroke>
          </LineSymbolizer>
        </Rule>
</FeatureTypeStyle>

I have been unable to get any error logging out of Geoserver about this issue, 
it is as if that single rule is just skipped. Data in database does seem to be 
ok, there are segments with correct value and they contain correct type of 
geometry (and values are similar to other possible values).

Any ideas how to deal with this issue would be appreciated. I'm running 
Geoserver 2.1.4 on top of RHEL5 and Tomcat 6.

-Tuomas Koivusalo


Think green - keep it on the screen.

This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to