Lines¶

Stroke¶

The only mandatory property for representation of linework is stroke. This is a key property; its presence triggers the generation of an appropriate LineSymbolizer.

Basic Stroke Properties

The use of stroke as a key property prevents CSS from having the idea of a default line color (as the stroke information must be supplied each time).

1. Navigate to the CSS Styles page.

2. Click Choose a different layer and select ne:roads from the list.

3. Click Create a new style and choose the following:

   Workspace for new layer:	No workspace
   New style name:	line_example

4. Replace the generated CSS definition with the following stroke example:

   /* @title Line
    * @abstract Example line symbolization
    */
    * {
      stroke: blue;
    }
   

5. Click Submit and then the Map tab for an initial preview.

   You can use this tab to follow along as the style is edited, it will refresh each time Submit is pressed.

   

6. You can look at the SLD tab at any time to see the generated SLD. Currently it is showing a straight forward LineSymbolizer generated from the CSS stroke property:

   <sld:UserStyle>
      <sld:Name>Default Styler</sld:Name>
      <sld:FeatureTypeStyle>
         <sld:Name>name</sld:Name>
         <sld:Rule>
            <sld:Title>Line</sld:Title>
            <sld:Abstract>Example line symbolization</sld:Abstract>
            <sld:LineSymbolizer>
               <sld:Stroke>
                  <sld:CssParameter name="stroke">#0000ff</sld:CssParameter>
               </sld:Stroke>
            </sld:LineSymbolizer>
         </sld:Rule>
      </sld:FeatureTypeStyle>
   </sld:UserStyle>
   

7. Additional properties can be used to fine-tune appearance. Use stroke-width to specify the width of the line.

   /* @title Line
    * @abstract Example line symbolization
    */
    * {
      stroke: blue;
      stroke-width: 2px;
    }
   

8. The stroke-dasharray is used to define breaks rendering the line as a dot dash pattern.

   /* @title Line
    * @abstract Example line symbolization
    */
    * {
      stroke: blue;
      stroke-width: 2px;
      stroke-dasharray: 5 2;
    }
   

9. Check the Map tab to preview the result.

   

Z-Index¶

The next exercise shows how to work around a limitation when using multiple strokes to render a line.

Use of Z-Index

1. Providing two strokes is often used to provide a contrasting edge (called casing) to thick line work.

   Update line_example with the following:

   * {
     stroke: black, #8080E6;
     stroke-width: 5px, 3px;
   }
   

2. If you look carefully you can see a problem with our initial attempt. The junctions of each line show that the casing outlines each line individually, making the lines appear randomly overlapped. Ideally we would like to control this process, only making use of this effect for overpasses.

   

3. The z-index parameter allows a draw order to be supplied. This time all the thick black lines are dawn first (at z-index 0) followed by the thinner blue lines (at z-index 1).

   * {
     stroke: black, #8080E6;
     stroke-width: 5px, 3px;
     z-index: 0, 1;
   }
   

4. If you look carefully you can see the difference.

   

5. By using z-index we have been able to simulate line casing.

   

Label¶

Our next example is significant as it introduces the how text labels are generated.

Use of Label Property

This is also our first example making use of a dynamic style (where the value of a property is defined by an attribute from your data).

1. To enable LineString labeling we will need to use the key properties for both stroke and label.

   Update line_example with the following:

   * {
     stroke: blue;
     label: [name];
   }
   

2. The SLD standard documents the default label position for each kind of Geometry. For LineStrings the initial label is positioned on the midway point of the line.

   

3. We have used an expression to calculate a property value for label. The label property is generated dynamically from the name attribute. Expressions are supplied within square brackets, making use of Constraint Query Language (CQL) syntax.

   * {
     stroke: blue;
     label: [name];
   }
   

4. Additional properties can be supplied to fine-tune label presentation:

   * {
     stroke: blue;
     label: [name];
     font-fill: black;
     label-offset: 7px;
   }
   

5. The font-fill property set to black provides the label color.

   * {
     stroke: blue;
     label: [name];
     font-fill: black;
     label-offset: 7px;
   }
   

6. The label-offset property is used to adjust the starting position used for labeling.

   Normally the displacement offset is supplied using two numbers (allowing an x and y offset from the the midway point used for LineString labeling).

   When labeling a LineString there is a special twist: by specifying a single number for label-offset we can ask the rendering engine to position our label a set distance away from the LineString.

   * {
     stroke: blue;
     label: [name];
     font-fill: black;
     label-offset: 7px;
   }
   

7. When used in this manner the rotation of the label will be adjusted automatically to match the LineString.

   

How Labeling Works¶

The rendering engine collects all the generated labels during the rendering of each layer. Then, during labeling, the engine sorts through the labels performing collision avoidance (to prevent labels overlapping). Finally the rendering engine draws the labels on top of the map. Even with collision avoidance you can spot areas where labels are so closely spaced that the result is hard to read.

The parameters provided by the SLD specification, from which our CSS implementation is derived, are general purpose and should be compatible with any rendering engine.

To take greater control over the GeoServer rendering engine we can use “vendor specific” parameters. These hints are used specifically for the GeoServer rendering engine and will be ignored by other systems. The GeoServer rendering engine marks each vendor specific parameter with the prefix -gt-.

1. The ability to take control of the labeling process is exactly the kind of hint a vendor specific parameter is intended for.

   Update line_example with the following:

   * {
     stroke: blue;
     label: [name];
     font-fill: black;
     label-offset: 7px;
     -gt-label-padding: 10;
   }
   

2. The parameter -gt-label-padding provides additional space around our label for use in collision avoidance.

   * {
     stroke: blue;
     label: [name];
     font-fill: black;
     label-offset: 7px;
     -gt-label-padding: 10;
   }
   

3. Each label is now separated from its neighbor, improving legibility.

   

Scale¶

This section explores the use of attribute selectors and the @scale selector together to simplify the road dataset for display.

1. Replace the line_example CSS definition with:

   [scalerank < 4] {
     stroke: black;
   }
   

2. And use the Map tab to preview the result.

   

3. The scalerank attribute is provided by the Natural Earth dataset to allow control of the level of detail based on scale. Our selector short-listed all content with scalerank 4 or lower, providing a nice quick preview when we are zoomed out.

4. In addition to testing feature attributes, selectors can also be used to check the state of the rendering engine.

   Replace your CSS with the following:

   [@scale > 35000000] {
      stroke: black;
   }
   [@scale < 35000000] {
      stroke: blue;
   }
   

5. As you adjust the scale in the Map preview (using the mouse scroll wheel) the color will change between black and blue. You can read the current scale in the bottom right corner, and the legend will change to reflect the current style.

   

6. Putting these two ideas together allows control of level detail based on scale:

   [@scale < 9000000] {
     stroke: #888888;
     stroke-width: 2;
   }
   [@scale >= 9000000] [@scale < 17000000] [scalerank < 7] {
     stroke: #777777;
   }
   [@scale >= 1700000] [@scale < 35000000] [scalerank < 6] {
     stroke: #444444;
   }
   [@scale >= 3500000] [@scale < 70000000] [scalerank < 5] {
     stroke: #000055;
   }
   [@scale >= 70000000] [scalerank < 4] {
     stroke: black;
   }
   

7. As shown above selectors can be combined in the same rule:

   • Selectors separated by whitespace are combined CQL Filter AND
   • Selectors separated by a comma are combined using CQL Filter OR

   Our first rule [@scale < 9000000] checks that the scale is less than 9M. The next rule [@scale >= 9000000] [@scale < 17000000] [scalerank < 7] checks that the scale is greater than or equal to 9M AND less than 17M AND that the scalerank is less than 7.

   

Additional Considerations¶