The GeoServer team is happy to announce the release of GeoServer 2.10.0. Downloads are available (zipwardmg and exe) along with docs and extensions.

This is the latest stable release of GeoServer intended for production systems. Please note that GeoServer 2.10.0 and GeoServer 2.9.2 include important security updates and we advise all users of GeoServer to upgrade at this time.

This release is made by Ian Turton with the help of the entire GeoServer team. It is built in collaboration with GeoTools 16.0 and GeoWebCache 1.10.0. We would like to thank everyone who provided feedback on the release candidate, ideally we would like more participation.

For more information on this release check the release notes ( 2.10-beta 2.10-M0 ).

Packaging and Installation

  • The macOS DMG is now signed by the Open Source Geospatial Foundation which is required for the latest macOS. If you are having trouble please check System Preferences Security & Privacy and ensure that apps are allowed from “App Store and identified developers”.

geoserver-macos-10-12 macOS 10.12 System Preferences for Security and Privacy

  • The windows installer is now signed by the Open Source Geospatial Foundation. Unfortunately it takes a few days for “Windows SmartScreen” to trust that the application is okay (it is marked as “not commonly downloaded” since we just created it). You will need to click “More Options” to see the option to run the application.

SmartScreen warning on Windows 7 SmartScreen warning on Windows 7

  • For those just starting out the default data directory now includes security restrictions on WFS-T functionality (restricting editing of data to the administrator account by default, it’s up to the administrator to change that if they wish).selezione_118

Thanks to Michael Smith and the OSGeo for purchasing a digital certificate - this helps our open source software reach a wider audience. We would also like to extend our thanks to Larry Shaffer for digging in on the macOS and Windows requirements. The signed windows installer has been “built by hand” and we ask for your feedback so Larry can put together an automated system.

Security Considerations

Aaron Waddell reported an XXE vulnerability in the GeoTools library which has now been fixed.

We ask all our users to treat security vulnerabilities with respect and make plans to upgrade to GeoServer 2.10.0 or GeoServer 2.9.2 at this time.

New Style Editor

This release includes the new Styled Editor featured at the FOSS4G 2016 workshop. The editor mixes in the CSS editor preview and layer association abilities for more productive style development (if you are a CSS user you can go straight to the standard CSS editor now, the specific one got retired).

Here are a few screenshots. The main tab is reminiscent of the existing style editor page:


The publishing tab allows to link the style to layers as primary, or as associated/secondary style:


The preview tab is where we expect most of the work to be done, editing the style, and clicking on “Apply” to view how the changes affect the map:


Finally, the layer attributes tab shows the available attributes, their type, a sample value and allows to compute statistics on them:


We would like to thank those who attended the FOSS4G 2016 styling workshop for trying out an early milestone release. Special thanks to Andrea for extensive testing/feedback and to Torben for all the hard work during the release candidate.

Improved QGIS style compatibility

At the FOSS4G 2016 code sprint some work was done to increase the compatibility between QGIS and GeoServer styling. While most of the work was performed on the QGIS SLD export correctness, some work was also done on the GeoTools/GeoServer side.

First, we taught GeoServer how to handle SE/SLD 1.1 external marks, and implemented support for TTF symbols as external marks (this is how QGIS exports TTF based symbols). Here is an example of the syntax (remember, this is SE, symbology encoding, not SLD 1.0):

   <se:OnlineResource xlink:type="simple" xlink:href="ttf://DNR%20Recreation%20Symbols"/>
     <se:SvgParameter name="fill">#000000</se:SvgParameter>

The result is the extraction of the symbol from the true type font, and its usage in the map as a scalable vector symbol.  Here is a sample from our test suite, with lines overlaying the symbols to easily identify the point locations:


QGIS ships with a set of SVG symbols which are “interesting”, in that they do not contain a fixed fill or stroke color, but parameters that need to be filled by the caller. QGIS then allows the user to specify such values, and fills them in before rendering, thus allowing to treat a SVG in a similar way to a built-in mark (with just a bit less control over the output compared to a mark). Looking at a SVG source we see:

<polygon fill="param(fill)" fill-opacity="param(fill-opacity)"
  stroke="param(outline)" stroke-opacity="param(outline-opacity)"
  points="290.565,67.281 35.067,509.815 33.98,511.7 545.209,512.093 547.389,512.095 "/>

GeoServer just learned to support these parameters, which are supposed to be added in the SVG URL reference, accoding to the SVG Parameters 1.0 spec “URL parameters” approach:

       <OnlineResource xlink:type="simple" xlink:href="firestation.svg?fill=#FF0000" />

Which will result in something like:


There is more work to be done - the team looked at including some of the custom QGIS “well-known” marks in GeoServer, but this work was not completed for the 2.10.0 release. If you are interested in helping out on this or other activities please contact us as a volunteer or professionally.

We would like to thank Andrea for his cross project leadership on this issue, and to the participants of the FOSS4G code sprint for helping out.

CSS Styling Improvements

The CSS Extension now sports nested rules, allowing for even more compact styles, for example:

[@scale < 3000] {
   mark: symbol(circle);
   :mark {
      fill: gray;
      size: 5
   [type = 'important'] {
      mark: symbol(triangle);
      :mark {
        fill: red;
        stroke: yellow

Rendering transformation support has also been added, for example, it’s possible to extract contour lines from a raster using the following style:

<span class="c">/* @title Levels */</span>
<span class="o">*</span> <span class="p">{</span>
  <span class="n">transform</span><span class="o">:</span> <span class="n">ras</span><span class="o">:</span><span class="n">Contour</span><span class="p">(</span><span class="n">levels</span><span class="o">:</span> <span class="m">1100</span> <span class="m">1200</span> <span class="m">1300</span> <span class="m">1400</span> <span class="m">1500</span> <span class="m">1600</span> <span class="m">1700</span><span class="p">);</span>
  <span class="k">z-index</span><span class="o">:</span> <span class="m">0</span><span class="p">;</span>
  <span class="n">stroke</span><span class="o">:</span> <span class="nb">gray</span><span class="p">;</span>
  <span class="n">label</span><span class="o">:</span> <span class="p">[</span><span class="n">numberFormat</span><span class="p">(</span><span class="s1">'#'</span><span class="o">,</span> <span class="n">value</span><span class="p">)];</span>
  <span class="k">font-size</span><span class="o">:</span> <span class="m">12</span><span class="p">;</span>
  <span class="k">font</span><span class="o">-</span><span class="n">fill</span><span class="o">:</span> <span class="nb">black</span><span class="p">;</span>
  <span class="k">font-weight</span><span class="o">:</span> <span class="k">bold</span><span class="p">;</span>
  <span class="n">halo</span><span class="o">-</span><span class="k">color</span><span class="o">:</span> <span class="nb">white</span><span class="p">;</span>
  <span class="n">halo</span><span class="o">-</span><span class="n">radius</span><span class="o">:</span> <span class="m">2</span><span class="p">;</span>
  <span class="o">-</span><span class="n">gt</span><span class="o">-</span><span class="n">label</span><span class="o">-</span><span class="n">follow</span><span class="o">-</span><span class="n">line</span><span class="o">:</span> <span class="n">true</span><span class="p">;</span>
  <span class="o">-</span><span class="n">gt</span><span class="o">-</span><span class="n">label</span><span class="o">-</span><span class="k">repeat</span><span class="o">:</span> <span class="m">200</span><span class="p">;</span>
  <span class="o">-</span><span class="n">gt</span><span class="o">-</span><span class="n">label</span><span class="o">-</span><span class="n">max</span><span class="o">-</span><span class="n">angle</span><span class="o">-</span><span class="n">delta</span><span class="o">:</span> <span class="m">45</span><span class="p">;</span>
  <span class="o">-</span><span class="n">gt</span><span class="o">-</span><span class="n">label</span><span class="o">-</span><span class="n">priority</span><span class="o">:</span> <span class="m">2000</span><span class="p">;</span>
<span class="p">}</span>

WMTS improvements

The WMTS service has now its own service configuration page, and if the INSPIRE extension is installed, proper INSPIRE extensions. The WMTS service is also now usable on per-workspace services (aka virtual services).


“JPEG or PNG” output format for WMS and WMTS

The relase includes support for the “JPEG or PNG” format, which allows the server to dynamically decide if JPEG or PNG is to be returned, based on pixel transparency. This should solve the classic scattered aerial/satellite overlay imagery dilemma, where the imagery is best compressed JPEG, except at the borders of the images, where transparency is needed.


GetFeatureInfo improvements for coverages

GetFeatureInfo against raster layers now ensures valid XML names are given to attributes, for valid GML outputs, and supports continous map wrapping for geographic projections, as well as working properly for rasters whose coordinate span beyond the 180 degrees East:


We would like to thank Ben Caradoc-Davies for working on this.

New projections support

GeoTools is now providing support for the Azimuthal equidistant projection:

Support for the rotated pole projections was also added:


Rotated pole support for GRIB2/NetCDF and GeoServer integration by Ben Caradoc-Davies (Transient), with the GeoTools rotated pole projection implementation by Maciej Filocha (ICM), based on code provided by Jürgen Seib (Deutscher Wetterdienst).

Image mosaic and image pyramid improvements

Both the image mosaic and image pyramid can now be configured to serve multiple coverages no matter what the data source (previously this was possible only if the sources were NetCDF or Grib files).

At the same time the image mosaic now allows more heterogeneous sources, adding to the previous ability of mixing different color models, a newfound ability to support heterogeneous input projections:


Thanks to Devon Tucker for working on the heterogeneous input projections. For more information please check out the documentation examples.

LDAP User Group Service

The LDAP integration was previously limited to “authentication provider” status, e.g. it allowed GeoServer to validate a username/password combo by trying to connect to a LDAP service. GeoServer 2.10 ships with a LDAP based “user group service” instead, meaning, the list of users can be directly fetched from the LDAP, in alternative to the existing XML and JDBC providers.


Community Modules

The GeoServer community has been very active producing a wide range of exciting capabilities. These modules are not part of a release, and are not officially supported, but most of them can be downloaded as part of our nightly builds or built locally. If you are interested in seeing these reviewed and included in future releases of GeoServer please reach out to and ask how you can help.

YSLD community module

A new styling language, YSLD, has been added. YSLD is a YAML based language which closely matches the stucture of SLD using a text only representation: indentation is used to represent document structure rather than XML tags; filters are represented using ECQL, and all GeoServer vendor options are supported (with a “x-“ prefix).

YSLD allows you to cut down your style for the common case where a style has a single rule inside a single feature style - for example:

- polygon:
  stroke-color: 'blue'
  stroke-width: 1
  fill-color: '#7EB5D3'
- text:
  label: ${name}
  fill-color: 'black'
  anchor: [0.5, 0.5]
  x-maxDisplacement: 40
  x-autoWrap: 70

As a “YAML based“ format common blocks of code can be defined up front, and reused multiple times.

define: &stroke
 stroke-color: 'gray'
 stroke-width: 0.5
 - filter: ${region = '1'}
   - polygon:
     <<: *stroke
     fill-color: '#8DD3C7'
 - filter: ${region = '2'}
   - polygon:
     <<: *stroke
     fill-color: '#FFFFB3'

One feature offered that is not included in SLD is integration with GeoWebCache zoom levels - this allows rules to be enabled for specific zoom levels (avoiding the need to calculate the correct scale denominators by hand).

- zoom: [min,5]
  filter: ${type = 'small'}
  - ...
- zoom: [5,max]
  filter: ${type = 'small'}
  - ...
- zoom: [min,5]
  else: true
  - ...
- zoom: [5,max]
  else: true
  - ...

One interesting ability of the YSLD module that can be used to help get you started is the ability to take an existing SLD style and translate it 1-1 to YSLD using the REST API:

  • Access as SLD: http://localhost:8080/geoserver/rest/styles/states.sld?pretty=true

  • Access as YSLD: http://localhost:8080/geoserver/rest/styles/states.yaml

    name: states title: Population in the United States abstract: |- A sample filter that filters the United States into three categories of population, drawn in different colors feature-styles: - name: name rules: - name: Population < 2M title: Population < 2M filter: ${PERSONS < ‘2000000’} scale: [min, max] symbolizers: - polygon: fill-color: ‘#A6CEE3’ fill-opacity: 0.7 …

For more information this release includes an extensive YSLD Reference (complete with diagrams and examples).


WMTS-ND discovery community module

The module adds WMTS operations helping a client to drill into the domain of a dataset with multiple dimensions, helping in particular with scattered datasets, or ones with related dimensions (e.g., forecasts having two related times, execution time and predicted time). The extra operations are:

  • DescribeDomains, providing a compact description of the available dimension values, and allowing to filter on a range of values for a particular dimension (space included), and see how the domain of the related dimensions change

  • GetHistogram, showing how the available data is distributed along a given dimension

  • GetFeature, to get footprint and dimension values of single features/rasters once a particular domain of interest has been established

The full specification is available online.

ncWMS community module

The ncWMS community module adds some extra operations and style support specially geared towards multidimensional raster data (including, but not limited to, NetCDF). The operations are a subset of the WMS extension provided by ncWMS, a NetCDF-CF specific WMS server. First, a palette oriented styling language is added that only requires to provide a list of color values, which will be applied to the declared data min/max range automatically:


The palette is then going to be applied to the range of values declared in the layer bands configuration, along with a number of vendor parameter in the request to control the actual range of values to be displayed, color for out of range values, linear vs logarithic palette:


The request can also include a “animate” parameter that, coupled with the GIF output format and a dimension range, e.g., a time range, will generate an animation in output:


Finally, a GetTimeSeries request parallels GetFeatureInfo and charts/extract the evolution of the phenomenon at a given point against time (also available as a CSV dump):


More details and information about the module are available in the official documentation.

Backup and restore community module

The backup/restore community module provides a UI and a set of REST service to backup and restore the GeoServer configuration without forcing a full application restart. Each operation is asynchronous, and restores can be subject to dry run, to verify if the restore will complete without errors before actually applying it.


More information about the module can be found in the user documentation.

About GeoServer 2.10

Articles, docs, blog posts and presentations:

Community modules

  • A new community module to backup/restore and restore GeoServer configuration

  • A resource browser is available allowing remote management of styles, icons and fonts (needs building from sources).

  • A new WMTS multidimensional domain discovery community module for discovering patches of data in scattered data sets

  • The YSLD community module has been updated with extensive documentation