Page Comparison

...

Originally in Weave the drawing of the current selection was always done as part of the rendering the map image, this was because originally there was only a single map layer on the client. In this situation each update of the map image included a step, on the server, where the current selection was drawn on top of the map image generated by the underlying map engine before passing the image back to the browser for display.Image Removed

...

Once support for more than one map engine was available on the client this process was supplemented by configuring the client as such that the original map image was untouched and the current selection was drawn as a completely separate image, where both images were sent to the browser which displayed the selection image on top of the original map image.Image Removed

...

This provided improved performance for the client since it no longer required and entire map redraw if just the selection was changed, and was all done through configuration. The configuration basically involved creating a dummy map engine, based on the original map engine, that never ended up drawing any of it's layers but instead went through the process outlined above of having the selection drawn on the (empty) image it generated.

But this was only ever a hack since it relied upon the use of a dummy map engine configured through guesswork.
Now however this dummy map engine can be replaced by a map engine specifically designed to draw a separate selection layer on top of other layer in the client browser, it's this map engine, the Selection Map Engine that is described here.Image Removed

...

Configuration of the server map engine

...

Creating a selection map engine follows the same process as other map engines and just has a new namespace of its own when it comes to configuration, obviously the content of the configuration for the selection map engine is different since it serves a different purpose, but we explain that configuration here.

...

...

Basic configuration to setup a selection map engine on the server

<?xml version="1.0" encoding="UTF-8"?>

<config xmlns="urn:com.cohga.server.config#1.0" xmlns:selection="urn:com.cohga.server.map.selection#1.0">

  <selection:mapengine id="selection">
    <!-- Selection specific configuration if required -->
  </selection:mapengine>

</config>

...

The maximum scale beyond which selections won't be drawn can be set with the maxscale value.

...

Setting maximum scale for selections to be drawn at

  <selection:mapengine id="selection">
    <maxscale>50000</maxscale>
  </selection:mapengine>

...

By setting a limit value you can specify that the plugin should draw a maximum of that many features. There is no default value.

...

...

Setting time and selection size limits

  <selection:mapengine id="selection">
    <limit>5000</limit>
    <timeout>5</timeout>
  </selection:mapengine>

...

Additionally, if you really want to tweak the performance of the selection rendering you can disable the smoothing of the drawing by turning off anti-aliasing, which may gain a few milliseconds. The default is to anti-alias the selection drawing.

...

...

Turning off antialiasing

  <selection:mapengine id="selection">
    <antialiasing>false</antialiasing>
  </selection:mapengine>

Also, since the selected features are drawn in batches you can alter the number of features that are drawn in each batch. The default batch size is 1000.
Increasing this value will will reduce the overhead that's required for each batch but sometimes there are limits on the underlying infrastructure (database or spatial engine) that limit the number of features that can be retrieved at once. You can try increasing this value and selecting more than that many features and see if the selection is still drawing, if it is then it's safe to use the new limit value, otherwise it should be reduced until a safe value is determined. There's little point in setting this value to more than the limit value, if set.

...

Changing number of features rendered in each batch

  <selection:mapengine id="selection">
    <batchsize>2500</batchsize>
  </selection:mapengine>

...

You can specify the default format for the images generated by the selection map engine with the format property.

...

Changing the format of the generated image

  <selection:mapengine id="selection">
      <format>image/png32</format>
  </selection:mapengine>

...

CSS style rendering properties

...

• Colours can be specified as either an RGB value, as decimal or hex (e.g., #ff0000), or as one of black, blue, cyan, darkgray, darkgrey, gray, grey, green, lightgray, lightgrey, magenta, orange, pink, red, white, yellow.

• The word 'colour' or 'color' and hyphens can be used in the property names, for example the following are all equivalent, 'strokecolour', 'strokecolor', 'stroke-colour' and 'stroke-color'.

• When setting line properties only the stroke settings are read.

• When setting polygon properties only stroke and fill settings are read.

• When setting point properties stroke, fill and marker settings are read.

• You don't need to include point, line and polygon unless you want to change all renderers, you only need to include the one(s) you want to change, and you only need to include the properties that you want to change from the defaults

...

...

Changing the basic rendering styles of point, lines and polygons

<selection:mapengine id="selection">
  <override>
    <point>
      <active>
        <strokecolour>white</strokecolour>
        <strokewidth>1</strokewidth>
        <strokeopacity>0</strokeopacity>
        <fillcolour>cyan</fillcolour>
        <fillopacity>1</fillopacity>
        <mark>circle</mark>
        <marksize>12</marksize>
      </active>
      <inactive>
        <strokecolour>cyan</strokecolour>
        <strokewidth>2</strokewidth>
        <strokeopacity>1</strokeopacity>
        <fillcolour>white</fillcolour>
        <fillopacity>0</fillopacity>
        <mark>circle</mark>
        <marksize>12</marksize>
      </inactive>
    </point>
    <line>
      <active>
        <strokecolour>cyan</strokecolour>
        <strokewidth>3</strokewidth>
        <strokeopacity>0.75</strokeopacity>
      </active>
      <inactive>
        <strokecolour>#00ffff</strokecolour>
        <strokewidth>2</strokewidth>
        <strokeopacity>0.25</strokeopacity>
      </inactive>
    </line>
    <polygon>
      <active>
        <strokecolour>#00ffff</strokecolour>
        <strokewidth>3</strokewidth>
        <strokeopacity>0.75</strokeopacity>
        <fillcolour>#00ffff</fillcolour>
        <fillopacity>0.125</fillopacity>
      </active>
      <inactive>
        <strokecolour>#00ffff</strokecolour>
        <strokewidth>2</strokewidth>
        <strokeopacity>0.25</strokeopacity>
        <fillcolour>#00ffff</fillcolour>
        <fillopacity>0.025</fillopacity>
      </inactive>
    </polygon>
  </override>
</selection:mapengine>

...

This can be done by setting the geometry type for an entity as follows:

...

Overriding the rendering type for an entity

<selection:mapengine id="selection">
  <override>
    <entity id="property">polygon</entity>
    <entity id="road">line</entity>
    <entity id="trafficlight">point</entity>
  </override>
</selection:mapengine>

...

It's also possible to specify the rendering directly for a specific entity by using the entity id instead of point, line or polygon, for example:

...

Overriding an entities rendering using CSS properties

<selection:mapengine id="selection">
  <override>
    <entity id="property">
      <active>
        <strokecolour>green</strokecolour>
        <strokewidth>3</strokewidth>
        <strokeopacity>0.75</strokeopacity>
        <fillcolour>green</fillcolour>
        <fillopacity>0.125</fillopacity>
      </active>
      <inactive>
        <strokecolour>green</strokecolour>
        <strokewidth>2</strokewidth>
        <strokeopacity>0.25</strokeopacity>
        <fillcolour>green</fillcolour>
        <fillopacity>0.025</fillopacity>
      </inactive>
    </entity>
  </override>
</selection:mapengine>

...

Additionally it's possible to specify the selection rendering using SLD (Styled Layer Descriptor).
This can be done either by specifying the SLD directly in the config file or by referencing a file containing the SLD from the config file.

...

Referencing a SLD file

<selection:mapengine id="selection">
  <override>
    <entity id="property">property.sld</entity>
  </override>
</selection:mapengine>

...

Alternatively the SLD can be embedded directly in the configuration file (but is not recommended)

...

...

Embedding a SLD file

<selection:mapengine id="selection">
  <override>
    <entity id="property"><![CDATA[
      <StyledLayerDescriptor version="1.0.0" xsi:schemaLocation="http://www.opengis.net/sld StyledLayerDescriptor.xsd" xmlns="http://www.opengis.net/sld" xmlns:ogc="http://www.opengis.net/ogc" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <NamedLayer>
          <Name>property</Name>
          <UserStyle>
          <!-- Rest of SLD content here -->
          </UserStyle>
        </NamedLayer>
      </StyledLayerDescriptor>
    ]]></entity>
  </override>
</selection:mapengine>

There's an open source tool that can be used to create SLD files available at AtlasStyler SLD editor.

Optional 'override' tag in definition

...

The following two examples are equivalent:

...

Referencing a SLD file with override tag

<selection:mapengine id="selection">
  <override>
    <entity id="property">property.sld</entity>
  </override>
</selection:mapengine>

Referencing a SLD file without override tag

<selection:mapengine id="selection">
  <entity id="property">property.sld</entity>
</selection:mapengine>

...

Using the selection map engine requires that we add the selection map engine to the client configuration so that it is drawn on top of the existing layers.

...

...

New 'selection' map engine added to client

    <client:config id="...">
        ...
        <view id="com.cohga.html.client.map.mapView">
            ...
            <mapEngine id="raster">
               <options>
                 <selection>false</selection>
                 <alpha>false</alpha>
               </options>
            </mapEngine>

            <mapEngine id="vector">
               <options>
                 <selection>false</selection>
                 <alpha>true</alpha>
               </options>
            </mapEngine>

            </mapEngine id="selection">
                <options>
                    <!-- tell the client map engine that this layer is for handing selections -->
                    <selection>true</selection>
                    <!-- ensure the the client knows that this map engine supports transparency -->
                    <alpha>true</alpha>
                </options>
            </mapEngine>
        </view>
    </client:config>

The final step is to switch the toc model to use the new selection map engine for the selection related entries by adding a mapengine tag to the Selection entry.

    <toc:model id="toc.main">
        <!-- set the default map engine for entries that don't have one set -->
        <mapengine>vector</mapengine>

        <entry label="Selection" exclusive="true">
            <!-- change the map engine for every entry in this group to use the selection map engine-->
            <mapengine>selection</mapengine>
            <entry layer="_selection.active" label="Active" checked="true"/>
            <entry layer="_selection.all" label="All" checked="false"/>
            <entry label="Selected" checked="false">
                <!-- individual selection layer here -->
                ...
            </entry>
        </entry>

        <!-- regular layer entries here -->
        ...

        <entry label="Raster" exclusive="true">
            <!-- use the raster map engine for every entry in here -->
            <mapengine>raster</mapengine>
            ...
        </entry>
    </toc:model>

...