Versions Compared

Old Version 25

changes.mady.by.user Kim Stimpson

Saved on

compared with

New Version Current

changes.mady.by.user Kim Stimpson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

If you want to manually edit the SLD for the selected Layer then click on the Advanced tab. 

Info

From iShare 6.0 which uses MapServer 7.6.3 the handling of Multiple Rules in an SLD that match a given style have changed from matching just the first, to applying all that match, in order of the rules. See Using Multiple Rules below for details.


Note

If you manually edit the SLD via the Advanced tab and you add entries that cannot be handled by the SLD Style Editor then the Advanced tab will be your only option.

...

Here you can manually configure the style of your OGC Layer. Astun supply some default SLD files in the folder specified in the iShare Settings General tab SldSnippetDefinitionPath. For more information on SLD please refer to the GeoServer documentation which has plenty of examples httphttps://docs.geoserver.org/stable/en/user/styling/sld-/cookbook/index.html.

Toolbar

There is a Toolbar at the top of the Editing pane for common functions:

...

  • Use a WHERE clause in the SQL statement for your Layer to limit the features being displayed rather than using FILTER statements in the SLD styling. Only use FILTER statements to style the display of the visible features.

Anchor
multiplerules
multiplerules
Using Multiple Rules

Status
colourYellow
title5.6.0+

If you wish to apply different styles to a Layer then you can do this using Multiple Rules.

Note
titleiShare 6.0

From iShare 6.0, due to the change in the way that Multiple Rules are handled i.e. Rules now apply to all that match not just the first match it finds, the solution is to use the <ElseFilter/> in the Rule which is used to match all not-otherwise-matched features. This goes in the Rule in the place that a Filter would normally occupy, e.g. in this simplified SLD, there’s a Rule with a Filter to match features with a crime_type value of Vehicle crime and a second Rule that uses ElseFilter to apply to all other features. Without the ElseFilter, every feature would have a fill colour of #FF8000.

Code Block
languagexml
titleExample ElseFilter
collapsetrue
<Rule>
  <Name>Vehicle crime</Name>
  <Description>
    <Title>Vehicle crime</Title>
  </Description>
  <Filter>
    <PropertyIsEqualTo>
      <PropertyName>crime_type</PropertyName>
      <Literal>Vehicle crime</Literal>
    </PropertyIsEqualTo>
  </Filter>
  <PointSymbolizer>
    <Graphic>
      <Mark>
        <WellKnownName>circle</WellKnownName>
        <Fill>
          <SvgParameter name="fill">#000080</SvgParameter>
        </Fill>
        <Stroke>
          <SvgParameter name="stroke">#000000</SvgParameter>
        </Stroke>
      </Mark>
      <Size>7</Size>
    </Graphic>
  </PointSymbolizer>
</Rule>
<Rule>
  <Name>Other crime</Name>
  <Description>
    <Title>Other crime</Title>
  </Description>
  <ElseFilter />
  <PointSymbolizer>
    <Graphic>
      <Mark>
        <WellKnownName>circle</WellKnownName>
        <Fill>
          <SvgParameter name="fill">#FF8000</SvgParameter>
        </Fill>
        <Stroke>
          <SvgParameter name="stroke">#000000</SvgParameter>
        </Stroke>
      </Mark>
      <Size>7</Size>
    </Graphic>
  </PointSymbolizer>
</Rule>


For a list of available filter functions that can be used with in a Rule/Filter see: https://mapserver.org/ogc/filter_encoding.html

...