Over the course of the past few months, I have been working on improving GeoServer style editor page based on the “CSS Styles” page. These changes are now available in the newly released GeoServer 2.10.0.

The original GeoServer Improvement Proposal for these changes (GSIP-149) can be found on the github page for the GeoServer project.

From a development perspective, working on these improvements was quite the experience, and turned out to not be as simple a port as I had expected. By the end of it, I wound up learning a lot about wicket (The UI Framework used by GeoServer), and the various ways in which we have gotten it to do things it was never designed to do.

Thanks to Andrea Aime for help with some of the technical aspects of Wicket and the previous Style Page, and to Jody Garnett for guiding me through the creation of my first GSIP. This work greatly benefited from review and feedback during the 2.10 release candidate and from the those attending the FOSS4G Styling workshop.

Intro to the New Style Editor

The new style editor is far more functional, in addition to managing the style you can now directly update which layers use the style, interactively preview your map at different zoom levels, and review layer attributes.

The new “apply” button works very well with the map preview, allowing you to save your work and review the change visually without leaving the style editor.

Refer to the User Guide for more details about each tab.

Data Tab

All the functionality of the old style editor is available on the first tab. This consists of modifying style data (name, workspace, format), style content (style generation and upload functions), and the legend graphic.

For example to generate a new point style:

1. Under Generate a default style select Point.
2. Click Generate, a random color will be used when generating the new style.
   
3. The Style editor is filled in with the generated style.
4. Press Apply to save this style while remaining on the style editor page.
5. Click Preview Legend to view a preview of the style iconography.
   

Publishing Tab

The “Publishing” tab visualizes which layers the current style is associated with, and lets you modify these associations for all layers.

For instance, we can set our new style to be the default style for the “buildings” layer:

To use our new point style we can configure several layers:

1. Make our style the default for buildings, click the checkbox under the Default column.
   
2. To allow our style to be used as an alternative style for firestations and hospitals click the checkbox under the Associated column.
   
3. These changes are made immediately.

Layer Preview Tab

One of the most valuable elements of the earlier CSS Style page was the ability to preview the current style on an existing layer. This ability to edit current layer, while showing a layer preview, is the key workflow improvement of the improved Style Editor.

The preview tab allows you to view the current style on any layer while editing:

1. The layer used for the preview can be changed by clicking the layer name at the top of the page.
   
   
2. The style editor remains at the bottom of the page when switching tabs, so we can go ahead and modify our style:
   
   
3. After modifying the style, we can click the new “Apply” button to save the style and remain on the page. The Layer Preview will be updated with the new styling:
   
   

Layer Attributes Tab

Similar to the Layer Preview, the Layer Attributes tab allows you to preview the attributes associated with the preview layer.

This can be useful for determining what attribute to use for labeling, or how best to configure scale-dependant rules.

1. The layer used for the preview can be changed by clicking the layer name at the top of the page.
   
2. The Min/Max statistics can be calculated using the “Compute” link. Let’s take a look at the range of elevations:
3. We can use this information to set the colour of the points based on their elevation, using the Interpolate function:
   
4. Clicking the “Apply” button and returning to the preview tab, we can see the results of these changes in the in the layer preview:
   

And there you have it! The new style page presents a much more streamlined workflow for writing new styles for your layers.

If you are using the new style editor and encounter an error, please file a bug report.

The GeoServer team is pleased to announce the release of GeoServer 2.10.1. Download bundles are provided (bin, war, dmg and exe) along with documentation and extensions.

GeoServer 2.10.1 is the latest stable release of GeoServer and is recommended for production deployment. This release is made in conjunction with GeoTools 16.1 and GeoWebCache 1.10.1. Thanks to all contributors.

New Features and Improvements:

• Allow windows installer to use port 80
• Allow underlined labels in SLD
• Add documentation for the WMTS multidimensional module
• Add an example of GS Download process with request of output reference

Bug Fixes:

• Slow startup of GeoServer with many layers
• Cannot upload style files in the style editor
• Generating a raster SLD style from template produces a formally invalid style
• WPS fails if geometry column is named “location”
• REST API services settings.html throws errors for null values
• REST PUT property update on ServiceInfo does not work properly for primitive properties
• ClassCastException when posting WFS Transaction request on a URL containing a valid GetFeature request
• High oversampling on raster cells with reproject can put a significant amount of load on GeoServer
• JMS Clustering does not propagate virtual services configurations

And more! For more information on this release check the release notes (2.10.1 | 2.10.0 | 2.10-RC1 | 2.10-beta | 2.10-M0 )

Security Considerations

This release addresses three security vulnerabilities:

• Additional restrictions have been placed on the demo request page
• Addressed an XML injection vulnerability identified in an automatic scan.
• GeoServer now changes sessions during login, this addresses a class of vulnerablities known as “session fixation”.

Thanks again to Nick Muerdter for reporting these in a responsible manner (and Andrea and Jody for addressing these during the November bug stomp.)

If you wish to report a security vulnerability, please visit our website for instructions on responsible reporting.

About GeoServer 2.10

Articles, docs, blog posts and presentations:

• State of GeoServer 2016 (slideshare)
• The style editor has been refreshed with the best ideas from the css extension
• The styling workshop has been updated for foss4g 2016 and now includes both CSS and YSLD examples.
• Smart transparency in GeoServer with image/vnd.jpeg-png format (GeoSolutions)
• QGIS SLD export improvements (GeoSolutions)

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

We are happy to announce the release of GeoServer 2.11.1. Downloads are available (zip, war, dmg and exe) along with documentation and extensions.

GeoServer 2.11.1 is the latest stable release of GeoSever recommended for production system. This release is made in conjunction with GeoTools 17.1.

Highlights of this release are featured below, for more information please see the release notes (2.11.1 | 2.11.0 | 2.11-RC1 | 2.11-beta ).

Security Considerations

This release addresses three security vulnerabilities:

• Added a configurable delay during login, to mitigate a brute force attack.
• Added a configurable parameter to control clickjacking attacks against the GeoServer UI.
• Added an additional parameter for locking down password autocomplete in the GeoServer UI

Thanks to Andrea Aime and Devon Tucker for providing fixes to these issues.

These fixes are also included in the 2.10.3 release.

If you wish to report a security vulnerability, please visit our website for instructions on responsible reporting.

New Features and Improvements

• There is a new Mapbox Style community module available, which adds support for an interoperable json styling language. For more details, refer to the documentation.
• GSIP 158 – NetCDF output support for variable attributes and extra variables. This improvement adds the ability to set attributes on output NetCDF variables, copy attributes from source NetCDF/GRIB variables, and copy scalar variables from NetCDF/GRIB sources including ImageMosaics. See the documentation for details.
• Allow disabling usage of SLD and SLD_BODY in WMS requests (also for virtual services).

Bug Fixes

• Various improvements to virtual services, including lookup and GML 3 encoding handling
• Namespace filtering on capabilities returns all layer groups (including the ones in other workspaces)
• Not possible to PUT workspace using REST
• GeoServer Home Page missing information messages
• Style Editor Preview Legend Fails on non-SLD Styles
• Integrated GWC does not work with layer and layer group specific services
• Generating a raster SLD style from template produces a functionally invalid style
• GeoServer generates invalid GeoPackage raster mosaics
• Metatiling may throw a ClassCastException: Raster cannot be cast to WritableRaster

About GeoServer 2.11

Articles, docs, blog posts and presentations:

• OAuth2 for GeoServer (GeoSolutions)
• YSLD has graduated and is now available for download as a supported extension
• Vector tiles has graduate and is now available for download as an extension
• The rendering engine continues to improve with underlying labels now available as a vendor option
• A new “opaque container” layer group mode can be used to publish a basemap while completely restricting access to the individual layers.
• Layer group security restrictions are now available
• Latest in performance optimizations in GeoServer (GeoSolutions)
• Improved lookup of EPSG codes allows GeoServer to automatically match EPSG codes making shapefiles easier to import into a database (or publish individually).

We are pleased to announce the release of GeoServer 2.10.4. Downloads are available (zip, war, dmg and exe) along with documentation and extensions.

This is a maintenance release of GeoServer suitable for production systems. Maintenance releases are focused on bug fixes and stability, rather than new features. This release is made in conjunction with GeoTools 16.4 and GeoWebCache 1.10.3.

This release is made by Torben Barsballe and Kevin Smith from the Boundless team. Special thanks to Nick Stires from Boundless and the Frank Warmerdam from OSGeo for their help setting up the new build.geoserver.org server used for this release. We would like to thank these volunteers and everyone who contributed features, fixes and time during the release process.

Security Considerations

The 2.10.3 release addressed three security vulnerabilities. Details of these vulnerabilities were not included in the 2.10.3 blog post to provide time for the fixes to be included in 2.11.1, and have been replicated here:

• Added a configurable delay during login, to mitigate a brute force attack.
• Added a configurable parameter to control clickjacking attacks against the GeoServer UI.
• Added an additional parameter for locking down password autocomplete in the GeoServer UI

Thanks to Andrea Aime and Devon Tucker for providing fixes to these issues.

If you wish to report a security vulnerability, please visit our website for instructions on responsible reporting.

New Features and Improvements

• Add rest endpoint for geofence admin rules
• Add REST endpoint for a user to change their password
• Allow disabling usage of SLD and SLD_BODY in WMS requests (also for virtual services)

Bug Fixes

• Native JAI installation instructions report incorrect information about the installers
• Downloading zip file using /rest/workspaces/<ws>/datastores/<ds>/file.shp doesn’t work after GeoServer reload
• Virtual services do not play nice with GML 3 encoding
• Namespace filtering on capabilties returns all layer groups (including the ones in other workspaces)
• Cascaded WMS does not encrypt configuration password
• Reloading GeoServer re-enables all disabled WMTS services
• Slow WFS GetFeature when using a 3D bbox POST request
• WMS cascading fails with NPE when advanced projection handling gets disabled
• Style Editor Preview Legend Fails on non-SLD Styles
• Exception when saving a layer group in GeoServer UI
• JMS fails to handle styles workspaces changes
• WFS-T Insert FeatureIds being returned in incorrect order
• CSW get capabilities ingore virtual services settings and always use the global service ones
• Integrated GWC does not work with layer and layer group specific services

And more! For more information on this release check the release notes ( 2.10.4 | 2.10.3 | 2.10.2 | 2.10.1 | 2.10.0 | 2.10-RC1 | 2.10-beta | 2.10-M0 )

About GeoServer 2.10

Articles, docs, blog posts and presentations:

• The YSLD extension added, with extensive documentation (user guide)
• State of GeoServer 2016 (slideshare)
• The style editor has been refreshed with the best ideas from the css extension (user guide)
• The styling workshop has been updated for foss4g 2016 and now includes both CSS and YSLD examples (user guide)
• Smart transparency in GeoServer with image/vnd.jpeg-png format (GeoSolutions)
• QGIS SLD export improvements (GeoSolutions)

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

We are happy to announce the release of GeoServer 2.11.2. Downloads are available (zip, war, dmg and exe) along with documentation and extensions.

GeoServer 2.11.1 is the latest stable release of GeoSever recommended for production system. This release is made in conjunction with GeoTools 17.1.

Highlights of this release are featured below, for more information please see the release notes (2.11.2 | 2.11.1 | 2.11.0 | 2.11-RC1 | 2.11-beta ).

New Features and Improvements

• There is a new GetLegendGraphic option that will return feature counts in the legend label, counting them in the current bounding box
• Geometries in GetFeatureInfo GML output are now reprojected following the base GetMap output projection
• The LayerGroup edit page allows configuring keywords and identifiers (as already available for normal layers)

Bug Fixes

• Various raster improvements, including better handling of heterogeneous CRS mosaics, lower pixelation at high latitudes in EPSG:3857,
• GetLegendGraphic against multiple layers did not work if any layer was out of scale range, fixed
• GetFeatureInfo now works against a mix of queriable and non queriable layers
• Cascading WMS now supports very long credentials
• Several fixes and tweaks in the configuration UI for an improved experience
• And several more, check the release notes for full details

About GeoServer 2.11

Articles, docs, blog posts and presentations:

• OAuth2 for GeoServer (GeoSolutions)
• YSLD has graduated and is now available for download as a supported extension
• Vector tiles has graduate and is now available for download as an extension
• The rendering engine continues to improve with underlying labels now available as a vendor option
• A new “opaque container” layer group mode can be used to publish a basemap while completely restricting access to the individual layers.
• Layer group security restrictions are now available
• Latest in performance optimizations in GeoServer (GeoSolutions)
• Improved lookup of EPSG codes allows GeoServer to automatically match EPSG codes making shapefiles easier to import into a database (or publish individually).

Rest API now using Spring MVC

In March, we upgraded the framework used by the GeoServer REST API from Restlet to Spring MVC. All the endpoints should remain unchanged, but they do need testing to ensure there weren’t any unintended side effects.

As part of this upgrade, we also have new REST documentation, providing detailed information about each endpoint.

Thanks again to the code sprint sponsors:

• Boundless
• GeoSolutions
• Astun Technology
• Gaia3D
• Insurance Australia Group (IAG)
• How 2 Map
• FOSSGIS
• Atol Conseils et Développements
• Geodan

WMTS Cascading

Adds the ability to create WMS layers backed by remote WMTS layers, similar to the pre-existing WMS cascading functionality.

See GSIP-162 for more details.

Style Based Layer Groups

Adds the ability to define a listing of layers and styles using a single SLD file, in accordance with the original vision of the SLD specification. This includes a new entry type in the Layer Group layers list, and a new preview mode for the style editor.

See GSIP-161 for more details.

Options for KML Placemark placement

New options for KML encoding have been added, to control the placement of placemark icons, mostly for polygons. The syntax of the new options introduces three new top level format options keys:

&format_options=kmcentroid_contain:true;kmcentroid_samples:10;kmcentroid_clip:true

See GSIP-160 for more details.

GeoWebCache data security API

Add an extension point to GeoWebCache allowing for a security check based on the layer and extent of the tile. Adds an implementation of this extension point to GeoServer’s GWC integration.

This change mostly only affects developers, but will lead to improved security for users in the future.

See GSIP 159 for more details.

NetCDF output support for variable attributes and extra variables

Adds the following to the NetCDF output extension:

1. An option to allow all attributes to be copied from the source NetCDF/GRIB variable to the target variable.
2. Support for manual configuration of variable attributes, much like the current support for setting global attributes.
3. Support for configuration of extra variables which are copied from the NetCDF/GRIB source to the output; initially only scalar variables will be supported. Extra variables can be expanded over “higher” dimensions, that is, values copied from one scalar per ImageMosaic granule are assembled into a multidimensional variable over, for example, time and elevation.

See GSIP 158 for more details.

New labeling features and QGIS compatibility

A number of small new features have been added to labeling to match some of QGIS features, in particular:

• Kerning is on by default
• New vendor option to strikethrough text
• New vendor options to control char and word spacing

• Perpendicular offset now works also for curved labels (previously only supported for straight labels):
• Labeling the border of polygons as opposed to their centroid when using a LinePlacement (here with repetition and offset):

Along with this work some SLD 1.1 text symbolizer fixes were added in order to better support the new QGIS 3.0 label export, here is an example of a map labeling with background image, as shown in QGIS, and then again in GeoServer using the same data and the exported SLD 1.1 style (click to enlarge):

CSS improvements

The CSS styling language and editing UI have seen various improvements. The editor now supports some primitive code completion:

At the language level:

• Scale dependencies can now also be expressed using the “@sd” variable (scale denominator) and the values can use common suffixes such as k and M to get more readable values, compare for example “[@scale < 1000000]” with “[@sd < 1M]”
• Color functions have been introduced to match LessCSS functionality, like “Darken”, “Lighten, “Saturate” and so on. The same functions have been made available in all other styling languages.
• Calling a “env” variable has been made easier, from “env(‘varName’)” to “@varName” (or “@varName(defaultValue)” if you want to provide a default value).

As you probably already know, internally CSS is translated to an equivalent SLD for map rendering purposes. This translation process became 50 times faster over large stylesheets (such as OSM roads, a particularly long and complicated style).

Image mosaic improvements and protocol control

Image mosaic saw several improvements in 2.12.

First, the support for mosaicking images in different coordinate reference systems improved greatly, with several tweaks and correctness fixes. As a noteworthy change, the code can now handle source data crossing the dateline. The following images show the footprints of images before and after the dateline (expressed in two different UTM zones, 60 and 1 respectively) and the result of mosaicking them as rasters (click to get a larger picture of each):

There are more good news for those that handle mosaicks with a lot of super-imposing images taken at different times. If you added interesting information into the mosaic index, such as cloud cover, off-nadir, snow cover and the like, you can now filter and sort over them, in both WMS (viewing) and WCS (downloading) by adding the cql_filter and sortBy KVP parameters.

Here is an example of the same mosaic, the first composite favoring smallest cloud cover, the second one favoring recency instead (click to enlarge):

GeoPackage graduation

The GeoPackage store jumped straight from community to core package, in light of its increasing importance.

The WMS/WFS/WPS output formats are still part of community. Currently GeoPackage vector does not support spatial indexes, but stay tuned, it’s cooking!

New community modules

The 2.12 series comes with a few new community modules, in particular:

• Looking into styling vector tiles and server side using a single language? Look no further than the MBStyle module
• For those into Earth Observation, there is a new OpenSearch for EO module in the community section
• Need to store full GeoTiff in Amazon S3? The “S3 support for GeoTiff” module might just be what you’re looking for
• A new “status-monitoring” community module is about to be merged, providing basic statistics system resource usage. Check out this pull request to follow its progress and merge.

Mind, community modules are not part of the release, but you can find them in the nightly builds instead.

Rest API now using Spring MVC

In March, we upgraded the framework used by the GeoServer REST API from Restlet to Spring MVC. All the endpoints should remain unchanged, but they do need testing to ensure there weren’t any unintended side effects.

As part of this upgrade, we also have new REST documentation, providing detailed information about each endpoint.

Thanks again to the code sprint sponsors:

• Boundless
• GeoSolutions
• Astun Technology
• Gaia3D
• Insurance Australia Group (IAG)
• How 2 Map
• FOSSGIS
• Atol Conseils et Développements
• Geodan

WMTS Cascading

Adds the ability to create WMS layers backed by remote WMTS layers, similar to the pre-existing WMS cascading functionality.

See GSIP-162 for more details.

Style Based Layer Groups

Adds the ability to define a listing of layers and styles using a single SLD file, in accordance with the original vision of the SLD specification. This includes a new entry type in the Layer Group layers list, and a new preview mode for the style editor.

See GSIP-161 for more details.

Options for KML Placemark placement

New options for KML encoding have been added, to control the placement of placemark icons, mostly for polygons. The syntax of the new options introduces three new top level format options keys:

&format_options=kmcentroid_contain:true;kmcentroid_samples:10;kmcentroid_clip:true

See GSIP-160 for more details.

GeoWebCache data security API

Add an extension point to GeoWebCache allowing for a security check based on the layer and extent of the tile. Adds an implementation of this extension point to GeoServer’s GWC integration.

This change mostly only affects developers, but will lead to improved security for users in the future.

See GSIP 159 for more details.

NetCDF output support for variable attributes and extra variables

Adds the following to the NetCDF output extension:

1. An option to allow all attributes to be copied from the source NetCDF/GRIB variable to the target variable.
2. Support for manual configuration of variable attributes, much like the current support for setting global attributes.
3. Support for configuration of extra variables which are copied from the NetCDF/GRIB source to the output; initially only scalar variables will be supported. Extra variables can be expanded over “higher” dimensions, that is, values copied from one scalar per ImageMosaic granule are assembled into a multidimensional variable over, for example, time and elevation.

See GSIP 158 for more details.

New labeling features and QGIS compatibility

A number of small new features have been added to labeling to match some of QGIS features, in particular:

• Kerning is on by default
• New vendor option to strikethrough text
• New vendor options to control char and word spacing

• Perpendicular offset now works also for curved labels (previously only supported for straight labels):
• Labeling the border of polygons as opposed to their centroid when using a LinePlacement (here with repetition and offset):

Along with this work some SLD 1.1 text symbolizer fixes were added in order to better support the new QGIS 3.0 label export, here is an example of a map labeling with background image, as shown in QGIS, and then again in GeoServer using the same data and the exported SLD 1.1 style (click to enlarge):

CSS improvements

The CSS styling language and editing UI have seen various improvements. The editor now supports some primitive code completion:

At the language level:

• Scale dependencies can now also be expressed using the “@sd” variable (scale denominator) and the values can use common suffixes such as k and M to get more readable values, compare for example “[@scale < 1000000]” with “[@sd < 1M]”
• Color functions have been introduced to match LessCSS functionality, like “Darken”, “Lighten, “Saturate” and so on. The same functions have been made available in all other styling languages.
• Calling a “env” variable has been made easier, from “env(‘varName’)” to “@varName” (or “@varName(defaultValue)” if you want to provide a default value).

As you probably already know, internally CSS is translated to an equivalent SLD for map rendering purposes. This translation process became 50 times faster over large stylesheets (such as OSM roads, a particularly long and complicated style).

Image mosaic improvements and protocol control

Image mosaic saw several improvements in 2.12.

First, the support for mosaicking images in different coordinate reference systems improved greatly, with several tweaks and correctness fixes. As a noteworthy change, the code can now handle source data crossing the dateline. The following images show the footprints of images before and after the dateline (expressed in two different UTM zones, 60 and 1 respectively) and the result of mosaicking them as rasters (click to get a larger picture of each):

There are more good news for those that handle mosaicks with a lot of super-imposing images taken at different times. If you added interesting information into the mosaic index, such as cloud cover, off-nadir, snow cover and the like, you can now filter and sort over them, in both WMS (viewing) and WCS (downloading) by adding the cql_filter and sortBy KVP parameters.

Here is an example of the same mosaic, the first composite favoring smallest cloud cover, the second one favoring recency instead (click to enlarge):

GeoPackage graduation

The GeoPackage store jumped straight from community to core package, in light of its increasing importance.

The WMS/WFS/WPS output formats are still part of community. Currently GeoPackage vector does not support spatial indexes, but stay tuned, it’s cooking!

New community modules

The 2.12 series comes with a few new community modules, in particular:

• Looking into styling vector tiles and server side using a single language? Look no further than the MBStyle module
• For those into Earth Observation, there is a new OpenSearch for EO module in the community section
• Need to store full GeoTiff in Amazon S3? The “S3 support for GeoTiff” module might just be what you’re looking for
• A new “status-monitoring” community module has been added, providing basic statistics system resource usage. Check out this pull request to follow its progress and merge.

Mind, community modules are not part of the release, but you can find them in the nightly builds instead.

We are happy to announce the release of GeoServer 2.12.1. Downloads are available (zip, war, dmg and exe) along with docs and extensions.

We are happy to announce the release of GeoServer 2.11.5. Downloads are available (zip, war, and exe) along with documentation and extensions (OSX installer is currently missing as we’re unable to generate a signed installed version due to security/infrastructure issues being discussed on geoserver-devel).

GeoServer 2.11.5 is the last maintenance release of the GeoServer 2.11.x series, so we recommend users to plan an upgrade to 2.12.x or to the upcoming 2.13.x series. This release is made in conjunction with GeoTools 17.5.

Highlights of this release are featured below, for more information please see the release notes (2.11.5 | 2.11.4 | 2.11.3 |  2.11.2 | 2.11.1 | 2.11.0 | 2.11-RC1 | 2.11-beta ).

Bug Fixes

• Fixed GetFeatureInfo on rasters setup with “reproject to declared” SRS policy
• Assorted fixes on demo request page (password was not being sent
• Allow importer to handle multi-coverage files on import (NetCDF)
• GetLegendGraphic fixes for cut symbols on rescale (happened with large symbols and odd sized legends)
• WMS fixes on rendering rasters whose native CRS is a polar stereographic
• And several more, check the release notes for full details

About GeoServer 2.11

Articles, docs, blog posts and presentations:

• OAuth2 for GeoServer (GeoSolutions)
• YSLD has graduated and is now available for download as a supported extension
• Vector tiles has graduate and is now available for download as an extension
• The rendering engine continues to improve with underlying labels now available as a vendor option
• A new “opaque container” layer group mode can be used to publish a basemap while completely restricting access to the individual layers.
• Layer group security restrictions are now available
• Latest in performance optimizations in GeoServer (GeoSolutions)
• Improved lookup of EPSG codes allows GeoServer to automatically match EPSG codes making shapefiles easier to import into a database (or publish individually).

We are happy to announce the release of GeoServer 2.13-beta. Downloads are available (zip, war, and exe) along with docs and extensions.

This is a beta release of GeoServer made in conjunction with GeoTools 19-beta.

We want to encourage people to test the release thoroughly and report back any issue found. With no further delay, let’s see what’s new, that is, what is there to test!

Isolated Workspaces

The concept of an “Isolated Workspaces” has been added to GeoServer, to allow for reusing a namespace among multiple workspaces. In particular, an isolated workspace allows reuse of a namespace already used by another workspace, but its resources (layers, styles, etc …) can only be retrieved when using that workspace’s virtual services and will only show up in those virtual service capabilities documents.

When reusing a namespace among workspaces, exactly one of those must be non-isolated, and the rest must be isolated; i.e. isolated workspaces have no restrictions in namespaces usage but the existing restrictions still apply for non isolated workspaces.

This is particularly useful for those publishing complex schemas for INSPIRE compliance. For more details, refer to the original proposal.

GeoWebCache REST API

Two new endpoints have been added to the GeoWebCache REST API:

• /gwc/rest/blobstores:
  • GET /gwc/rest/blobstores for a list of the blobstores
  • GET /gwc/rest/blobstores/{blobStoreName} for details about a single blobstore
  • PUT /gwc/rest/blobstores/{blobStoreName} to create or update a blobstore
  • DELETE /gwc/rest/blobstores/{blobStoreName} to remove a blobstore
• /gwc/rest/gridsets:
  • GET /gwc/rest/gridsets for a list of the gridsets
  • GET /gwc/rest/gridsets/{gridSetName} for details about a single gridset
  • PUT /gwc/rest/gridsets/{gridSetName} to create or update a gridset
  • DELETE /gwc/rest/gridsets/{gridSetName} to remove a gridset

API docs for these endpoints will be added to the GeoServer documentation shortly. Until then, the request body syntax for PUT requests closely matched the equivalent structures in geowebcache.xml: BlobStores and GridSets.

The ArcGISCache backed layers are now also configurable via the REST API.

This release sees a major reworking of the configuration system in GeoWebCache that will allow for plugging in alternate configuration persistence mechanisms in future. While these changes should be largely invisible to users, it is a huge update that impacts all of GeoWebCache. However, due to these changes, we ask that you please test the embedded GeoWebCache.

UI Improvements

Entering in URLs for data files has been improved with autocomplete – now GeoServer will scan the path that has already been typed, and suggest existing files within that path.

In addition, autocomplete support has been added to a number of dropdowns which contain a long list of values, such as stores or layers. You can now start typing the name of an option, and the visible options will be filtered to match.

Editing raster layer parameters made easier, from a wall a text input fields, to appropriate controls being used depending on the parameter type. Here is a “before and after” comparison:

Finally, error messages are now displayed both at top (as usual) and bottom (new!) in all configuration pages. This should make it easier to locate error messages, especially while editing styles:

GeoPackage performance improvements

GeoPackage reading and rendering performance improved significantly, up to two times faster on large datasets full extractions and 50% faster on small bounding box searches, bringing GeoPackage on par with PostGIS. We also have a Google spreadsheet with more details.

Shapefile remains king of full dataset extractions and the fastest data source for pure spatial driven queries.

WFS 2.0 and WMTS 1.0 OGC compliance work

During the past few months we have been involved in OGC Testbed 14 and significantly improved GeoServer compliance with WFS 2.0 and WMTS 1.0. The work involved numerous fixes in GeoServer/GeoWebCache, along with variuos fixes in the CITE tests themselves. The changes were too numerous to backport to the 2.12.x series, so if compliance with these protocols is important it’s time to consider an upgrade to the 2.13.x series. For details see these lists:

• Full list of WFS 2.0 OGC compliances related changes
• List of changes for WMTS 1.0 are split among GeoWebCache and GeoServer ones

Work is still ongoing and a small number of issues are yet to be fixed, we’ll keep you updated.

Support for more PostGIS data types

The PostGIS data store now has simple support for HStore and JSON columns. HStore is returned as a Map and will render as a JSON formatted string field in common WFS output formats, while JSON is read as a string and rendered as-is. In both cases no special query support has been added for those types (but we’d be very happy if someone would work, or sponsor, that functionality too).

Better label position control in map rendering

When setting maxDisplacement on point/polygons the renderer used to search in a circular area around the designated label point.
The new displacementMode vendor option allows to control the positioning by specifying the preferred cardinal positions, as a comma separated list.

Coverage views from heterogeneous bands

Satellite data often comes as a set of heterogeenous resolution bands, due to multiple sensors having different native resolutions. It is yet useful to have all bands packaged on the same coverage, for ease of display (false color setups) and information (GetFeatureInfo). Coverage views now allow to mix those bands, coming from separate files and organized in a image mosaic, in a single multiband coverage view, resampling on the fly with configurable target resolution policies.

Removed OS X installers

Due to lack of resources and interest, the OS X dmg installers are no longer being built. OS X users can still use the system-independent binary.

New community modules and improvements

The 2.13 series comes with a few new community modules, in particular:

• Do you want to generate GHRSST compliant outputs from GHRSST inputs? Try out the new GHRSST NetCDF output community module.
• There is also a new community module introducing NSG profiles for the WFS and WMTS services.

Existing community modules also got some love, in particular:

• The WPS download module now allows to download large maps, and also build animations, generating MP4 courtesy of jcodec library. Both processes can (and should!) be invoked asynchronously to better handle long generation times. Here is an example of animation output:

• The WPS download process now also allows control of GeoTiff output structure (tiling, compression) in raw raster downloads
• Various JDBCConfig and JDBCStore performance improvements, reducing the number of configuration database queries performed for each OGC request. Configuration queries are also consistently logged for further analysis

Note that community modules are not part of the release; instead you can find them in the nightly builds.

We are happy to announce the release of GeoServer 2.13-RC1. Downloads are available (zip, war, and exe) along with docs and extensions.

This is a release candidate of GeoServer made in conjunction with GeoTools 19-RC1.

We want to encourage people to test the release thoroughly and report back any issue found. With no further delay, let’s see what’s new, that is, what is there to test!

Isolated Workspaces

The concept of an “Isolated Workspaces” has been added to GeoServer, to allow for reusing a namespace among multiple workspaces. In particular, an isolated workspace allows reuse of a namespace already used by another workspace, but its resources (layers, styles, etc …) can only be retrieved when using that workspace’s virtual services and will only show up in those virtual service capabilities documents.

When reusing a namespace among workspaces, exactly one of those must be non-isolated, and the rest must be isolated; i.e. isolated workspaces have no restrictions in namespaces usage but the existing restrictions still apply for non isolated workspaces.

This is particularly useful for those publishing complex schemas for INSPIRE compliance. For more details, refer to the original proposal.

GeoWebCache REST API

Two new endpoints have been added to the GeoWebCache REST API:

• /gwc/rest/blobstores:
  • GET /gwc/rest/blobstores for a list of the blobstores
  • GET /gwc/rest/blobstores/{blobStoreName} for details about a single blobstore
  • PUT /gwc/rest/blobstores/{blobStoreName} to create or update a blobstore
  • DELETE /gwc/rest/blobstores/{blobStoreName} to remove a blobstore
• /gwc/rest/gridsets:
  • GET /gwc/rest/gridsets for a list of the gridsets
  • GET /gwc/rest/gridsets/{gridSetName} for details about a single gridset
  • PUT /gwc/rest/gridsets/{gridSetName} to create or update a gridset
  • DELETE /gwc/rest/gridsets/{gridSetName} to remove a gridset

API docs for these endpoints will be added to the GeoServer documentation shortly. Until then, the request body syntax for PUT requests closely matched the equivalent structures in geowebcache.xml: BlobStores and GridSets.

The ArcGISCache backed layers are now also configurable via the REST API.

This release sees a major reworking of the configuration system in GeoWebCache that will allow for plugging in alternate configuration persistence mechanisms in future. While these changes should be largely invisible to users, it is a huge update that impacts all of GeoWebCache. However, due to these changes, we ask that you please test the embedded GeoWebCache.

UI Improvements

Entering in URLs for data files has been improved with autocomplete – now GeoServer will scan the path that has already been typed, and suggest existing files within that path.

In addition, autocomplete support has been added to a number of dropdowns which contain a long list of values, such as stores or layers. You can now start typing the name of an option, and the visible options will be filtered to match.

Editing raster layer parameters made easier, from a wall a text input fields, to appropriate controls being used depending on the parameter type. Here is a “before and after” comparison:

Finally, error messages are now displayed both at top (as usual) and bottom (new!) in all configuration pages. This should make it easier to locate error messages, especially while editing styles:

GeoPackage performance improvements

GeoPackage reading and rendering performance improved significantly, up to two times faster on large datasets full extractions and 50% faster on small bounding box searches, bringing GeoPackage on par with PostGIS. We also have a Google spreadsheet with more details.

Shapefile remains king of full dataset extractions and the fastest data source for pure spatial driven queries.

WFS 2.0 and WMTS 1.0 OGC compliance work

During the past few months we have been involved in OGC Testbed 14 and significantly improved GeoServer compliance with WFS 2.0 and WMTS 1.0. The work involved numerous fixes in GeoServer/GeoWebCache, along with variuos fixes in the CITE tests themselves. The changes were too numerous to backport to the 2.12.x series, so if compliance with these protocols is important it’s time to consider an upgrade to the 2.13.x series. For details see these lists:

• Full list of WFS 2.0 OGC compliances related changes
• List of changes for WMTS 1.0 are split among GeoWebCache and GeoServer ones

Work is still ongoing and a small number of issues are yet to be fixed, we’ll keep you updated.

Support for more PostGIS data types

The PostGIS data store now has simple support for HStore and JSON columns. HStore is returned as a Map and will render as a JSON formatted string field in common WFS output formats, while JSON is read as a string and rendered as-is. In both cases no special query support has been added for those types (but we’d be very happy if someone would work, or sponsor, that functionality too).

Better label position control in map rendering

When setting maxDisplacement on point/polygons the renderer used to search in a circular area around the designated label point.
The new displacementMode vendor option allows to control the positioning by specifying the preferred cardinal positions, as a comma separated list.

Coverage views from heterogeneous bands

Satellite data often comes as a set of heterogeenous resolution bands, due to multiple sensors having different native resolutions. It is yet useful to have all bands packaged on the same coverage, for ease of display (false color setups) and information (GetFeatureInfo). Coverage views now allow to mix those bands, coming from separate files and organized in a image mosaic, in a single multiband coverage view, resampling on the fly with configurable target resolution policies.

Removed OS X installers

Due to lack of resources and interest, the OS X dmg installers are no longer being built. OS X users can still use the system-independent binary.

New community modules and improvements

The 2.13 series comes with a few new community modules, in particular:

• Do you want to generate GHRSST compliant outputs from GHRSST inputs? Try out the new GHRSST NetCDF output community module.
• The mongodb community module provides an easy-to-use wrapper around the Ge0Tools mongodb data store, allowing you to publish geospatial data stored in mongodb.
• There is also a new community module introducing NSG profiles for the WFS and WMTS services.

Existing community modules also got some love, in particular:

• The WPS download module now allows to download large maps, and also build animations, generating MP4 courtesy of jcodec library. Both processes can (and should!) be invoked asynchronously to better handle long generation times. Here is an example of animation output:

• The WPS download process now also allows control of GeoTiff output structure (tiling, compression) in raw raster downloads, as well as downloading granules part of a heterogeneous mosaic in their native CRS and native resolution
• Various JDBCConfig and JDBCStore performance improvements, reducing the number of configuration database queries performed for each OGC request. Configuration queries are also consistently logged for further analysis

Note that community modules are not part of the release; instead you can find them in the nightly builds.

We are happy to announce the release of GeoServer 2.13.0. Downloads are available (zip, war, and exe) along with docs and extensions.

This is a release candidate of GeoServer made in conjunction with GeoTools 19.0.

Isolated Workspaces

The concept of an “Isolated Workspaces” has been added to GeoServer, to allow for reusing a namespace among multiple workspaces. In particular, an isolated workspace allows reuse of a namespace already used by another workspace, but its resources (layers, styles, etc …) can only be retrieved when using that workspace’s virtual services and will only show up in those virtual service capabilities documents.

When reusing a namespace among workspaces, exactly one of those must be non-isolated, and the rest must be isolated; i.e. isolated workspaces have no restrictions in namespaces usage but the existing restrictions still apply for non isolated workspaces.

This is particularly useful for those publishing complex schemas for INSPIRE compliance. For more details, refer to the original proposal.

GeoWebCache REST API

Two new endpoints have been added to the GeoWebCache REST API:

• /gwc/rest/blobstores:
  • GET /gwc/rest/blobstores for a list of the blobstores
  • GET /gwc/rest/blobstores/{blobStoreName} for details about a single blobstore
  • PUT /gwc/rest/blobstores/{blobStoreName} to create or update a blobstore
  • DELETE /gwc/rest/blobstores/{blobStoreName} to remove a blobstore
• /gwc/rest/gridsets:
  • GET /gwc/rest/gridsets for a list of the gridsets
  • GET /gwc/rest/gridsets/{gridSetName} for details about a single gridset
  • PUT /gwc/rest/gridsets/{gridSetName} to create or update a gridset
  • DELETE /gwc/rest/gridsets/{gridSetName} to remove a gridset

API docs for these endpoints will be added to the GeoServer documentation shortly. Until then, the request body syntax for PUT requests closely matched the equivalent structures in geowebcache.xml: BlobStores and GridSets.

The ArcGISCache backed layers are now also configurable via the REST API.

This release sees a major reworking of the configuration system in GeoWebCache that will allow for plugging in alternate configuration persistence mechanisms in future. While these changes should be largely invisible to users, it is a huge update that impacts all of GeoWebCache. However, due to these changes, we ask that you please test the embedded GeoWebCache.

UI Improvements

Entering in URLs for data files has been improved with autocomplete – now GeoServer will scan the path that has already been typed, and suggest existing files within that path.

In addition, autocomplete support has been added to a number of dropdowns which contain a long list of values, such as stores or layers. You can now start typing the name of an option, and the visible options will be filtered to match.

Editing raster layer parameters made easier, from a wall a text input fields, to appropriate controls being used depending on the parameter type. Here is a “before and after” comparison:

Finally, error messages are now displayed both at top (as usual) and bottom (new!) in all configuration pages. This should make it easier to locate error messages, especially while editing styles:

GeoPackage performance improvements

GeoPackage reading and rendering performance improved significantly, up to two times faster on large datasets full extractions and 50% faster on small bounding box searches, bringing GeoPackage on par with PostGIS. We also have a Google spreadsheet with more details.

Shapefile remains king of full dataset extractions and the fastest data source for pure spatial driven queries.

WFS 2.0 and WMTS 1.0 OGC compliance work

During the past few months we have been involved in OGC Testbed 14 and significantly improved GeoServer compliance with WFS 2.0 and WMTS 1.0. The work involved numerous fixes in GeoServer/GeoWebCache, along with variuos fixes in the CITE tests themselves. The changes were too numerous to backport to the 2.12.x series, so if compliance with these protocols is important it’s time to consider an upgrade to the 2.13.x series. For details see these lists:

• Full list of WFS 2.0 OGC compliances related changes
• List of changes for WMTS 1.0 are split among GeoWebCache and GeoServer ones

Work is still ongoing and a small number of issues are yet to be fixed, we’ll keep you updated.

Support for more PostGIS data types

The PostGIS data store now has simple support for HStore and JSON columns. HStore is returned as a Map and will render as a JSON formatted string field in common WFS output formats, while JSON is read as a string and rendered as-is. In both cases no special query support has been added for those types (but we’d be very happy if someone would work, or sponsor, that functionality too).

Better label position control in map rendering

When setting maxDisplacement on point/polygons the renderer used to search in a circular area around the designated label point.
The new displacementMode vendor option allows to control the positioning by specifying the preferred cardinal positions, as a comma separated list.

Coverage views from heterogeneous bands

Satellite data often comes as a set of heterogeenous resolution bands, due to multiple sensors having different native resolutions. It is yet useful to have all bands packaged on the same coverage, for ease of display (false color setups) and information (GetFeatureInfo). Coverage views now allow to mix those bands, coming from separate files and organized in a image mosaic, in a single multiband coverage view, resampling on the fly with configurable target resolution policies.

Removed OS X installers

Due to lack of resources and interest, the OS X dmg installers are no longer being built. OS X users can still use the system-independent binary.

New community modules and improvements

The 2.13 series comes with a few new community modules, in particular:

• Do you want to generate GHRSST compliant outputs from GHRSST inputs? Try out the new GHRSST NetCDF output community module.
• The mongodb community module provides an easy-to-use wrapper around the Ge0Tools mongodb data store, allowing you to publish geospatial data stored in mongodb.
• There is also a new community module introducing NSG profiles for the WFS and WMTS services.

Existing community modules also got some love, in particular:

• The WPS download module now allows to download large maps, and also build animations, generating MP4 courtesy of jcodec library. Both processes can (and should!) be invoked asynchronously to better handle long generation times. Here is an example of animation output:

• The WPS download process now also allows control of GeoTiff output structure (tiling, compression) in raw raster downloads, as well as downloading granules part of a heterogeneous mosaic in their native CRS and native resolution
• Various JDBCConfig and JDBCStore performance improvements, reducing the number of configuration database queries performed for each OGC request. Configuration queries are also consistently logged for further analysis

Note that community modules are not part of the release; instead you can find them in the nightly builds.

Highlights of this release are featured below, for more information please see the release notes (2.13.1 | 2.13.0 | 2.13-RC1 | 2.13-beta):

New Features and Improvements

• MongoDB community module moved to extension
• Support PNG/JPEG WPS Downloads
• Allow self joining GetFeature without aliases
• Add support for priority in control-flow bounded queues
• Hibernate Monitoring extension moved to a community module

Bug Fixes

• WCS 1.0.0 generates wrong links in GetCapabilities
• WFS 2.0 capabilities report transaction support even if the service level is not configured as such
• WPSResourceManager cleanup is not deleting temporary subfolders (only files)
• GeoServer in CITE compliance mode fails to validate an empty LockFeature request
• WMS 1.3 GetMap request significantly slower than WMS 1.1.0 since GeoServer 2.11.4
• Import objects cannot be deleted when in COMPLETE state
• Style with Interpolate function causes NullPointerException on GetLegendGraphic
• Windows Installation issue – upgrading GeoServer results in corrupt data_dir
• Windows Installer: Remove ‘work’ folder when uninstalling

Highlights of this release are featured below, for more information please see the release notes (2.13.2 | 2.13.1 | 2.13.0 | 2.13-RC1 | 2.13-beta).

Improvements and Fixes

• style editor map legend always includes legend
• performance improvement for multi-band coverage time series
• WMS 1.3.0 performance improvement for north/east axis order
• Fix support of external graphics over http

Security updates

Please update your production instances of GeoServer to receive the latest security updates and fixes.

If you encounter a security vulnerability in GeoServer, or any other open source software, please take care to report the issue in a responsible fashion.

About GeoServer 2.13 Series

Additional information on the 2.13 series:

• Isolated workspaces (User Guide)
• Coverage views from heterogeneous bands (User Guide)
• State of GeoServer 2.13 (slideshare)
• See the GeoServer 2.13.0 released announcement for visual guide to new features

We are happy to announce the release of GeoServer 2.12.5. Downloads are available (zip, war, and exe) along with docs and extensions.

This release addresses several security vulnerabilities:

• Prevent arbitrary code execution via Freemarker Template injection
• XXE vulnerability in GeoTools XML Parser
• XXE vulnerability in WPS Request builder
• Various library upgrades (see above) from versions with known CVEs

Thanks to Steve Ikeoka, Kevin Smith, Brad Hards and Nuno Oliveira for providing fixes to these issues.

These fixes are also included in the 2.13.2 release.

WMS “nearest match” support for time dimension

WMS time dimension can now be configured for “nearest match”, that is, to return the nearest time to the one requested (either explicitly, or implicitly via the default time value).

In case of mismatch the actual time used will be returned along with the response as a HTTP header. It is also possible to configure a maximum tolerance, beyond that the server will throw a service exception.

Channel selection name allow expressions

<RasterSymbolizer>
  <ChannelSelection>
    <RedChannel>
      <SourceChannelName>
          <ogc:Function name="env">
             <ogc:Literal>B1</ogc:Literal>
             <ogc:Literal>2</ogc:Literal>
          </ogc:Function>
      </SourceChannelName>
    </RedChannel>
    <GreenChannel>
      <SourceChannelName>
          <ogc:Function name="env">
             <ogc:Literal>B2</ogc:Literal>
             <ogc:Literal>5</ogc:Literal>
          </ogc:Function>
      </SourceChannelName>
    </GreenChannel>
    <BlueChannel>
      <SourceChannelName>
          <ogc:Function name="env">
             <ogc:Literal>B3</ogc:Literal>
             <ogc:Literal>7</ogc:Literal>
          </ogc:Function>
      </SourceChannelName>
    </BlueChannel>
  </ChannelSelection>
<RasterSymbolizer>

<?xml version="1.0" encoding="UTF-8"?>
<StyledLayerDescriptor 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" xsi:schemaLocation="http://www.opengis.net/sld
http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd" version="1.0.0">
  <NamedLayer>
    <Name>Sentinel2 NDVI</Name>
    <UserStyle>
      <Title>NDVI</Title>
      <FeatureTypeStyle>
        <Transformation>
          <ogc:Function name="ras:Jiffle">
            <ogc:Function name="parameter">
              <ogc:Literal>coverage</ogc:Literal>
            </ogc:Function>
            <ogc:Function name="parameter">
              <ogc:Literal>script</ogc:Literal>
              <ogc:Literal>
                nir = src[7];
                vir = src[3];
                dest = (nir - vir) / (nir + vir);
              </ogc:Literal>
            </ogc:Function>
          </ogc:Function>
        </Transformation>
        <Rule>
          <RasterSymbolizer>
            <Opacity>1.0</Opacity>
            <ColorMap>
              <ColorMapEntry color="#000000" quantity="-1"/>
              <ColorMapEntry color="#0000ff" quantity="-0.75"/>
              <ColorMapEntry color="#ff00ff" quantity="-0.25"/>
              <ColorMapEntry color="#ff0000" quantity="0"/>
              <ColorMapEntry color="#ffff00" quantity="0.5"/>
              <ColorMapEntry color="#00ff00" quantity="1"/>
            </ColorMap>
          </RasterSymbolizer>
        </Rule>
      </FeatureTypeStyle>
    </UserStyle>
  </NamedLayer>
</StyledLayerDescriptor>

The performance is good enough for interactive display, and the result looks as follows (click to enlarge):

PostGIS store improvements and measured geometries support

The PostGIS datastore has been for years the only one that could encode a few filter functions used in filters down into native SQL, but it required a datastore creation flag to be enabled.
Starting with this release it will do so by default.

The functions supported for SQL encoding by the store are:

• String functions: strConcat, strEndsWith, strStartsWith, strEqualsIgnoreCase, strIndexOf, strLength, strToLowerCase, strToUpperCase, strReplace, strSubstring, strSubstringStart, strTrim, strTrim2
• Math functions: abs, abs_2, abs_3, abs_4, ceil, floor
• Date functions: dateDifference

This release adds support for “array” data type in the store, with full reading and writing support, as well as native filtering (with index support, where feasible).

Finally, it’s now possible to read geometries with measures from PostGIS and encode the results in GML. GML does not natively support measures, so the encoding is off by default and you’ll have to enable it explicitly, as well as ensure that the clients involved in WFS usage recognize this extra ordinate. The work will continue in the next few month in order to cover more formats.

Style editor improvements

The GeoServer style editor now includes a fullscreen side-by-side editing mode, to make it easier to preview your styles while editing them. Click the fullscreen button at the top-right of the screen to toggle fullscreen mode.

The toolbar also has two new additions, a color picker helping to find the right color and turn it into a HEX specification, and a file chooser that allows to pick an external graphic and build the relevant ExternalGraphic element:

The 2.12 series comes with a few new community modules, in particular:

• OAuth2 OpenID connect module (still very much a work in progress)
• A WFS3 implementation has been added that matches the current WFS3 specification draft, and it’s being updated to become an official compliant one.

Mind, community modules are not part of the release, but you can find them in the nightly builds instead.

We are happy to announce the release of GeoServer 2.14.0. Downloads are available (zip, war, and exe) along with docs and extensions.

This release includes a number of new features and improvements:

<RasterSymbolizer>
  <ChannelSelection>
    <RedChannel>
      <SourceChannelName>
          <ogc:Function name="env">
             <ogc:Literal>B1</ogc:Literal>
             <ogc:Literal>2</ogc:Literal>
          </ogc:Function>
      </SourceChannelName>
    </RedChannel>
    <GreenChannel>
      <SourceChannelName>
          <ogc:Function name="env">
             <ogc:Literal>B2</ogc:Literal>
             <ogc:Literal>5</ogc:Literal>
          </ogc:Function>
      </SourceChannelName>
    </GreenChannel>
    <BlueChannel>
      <SourceChannelName>
          <ogc:Function name="env">
             <ogc:Literal>B3</ogc:Literal>
             <ogc:Literal>7</ogc:Literal>
          </ogc:Function>
      </SourceChannelName>
    </BlueChannel>
  </ChannelSelection>
<RasterSymbolizer>

<?xml version="1.0" encoding="UTF-8"?>
<StyledLayerDescriptor 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" xsi:schemaLocation="http://www.opengis.net/sld
http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd" version="1.0.0">
  <NamedLayer>
    <Name>Sentinel2 NDVI</Name>
    <UserStyle>
      <Title>NDVI</Title>
      <FeatureTypeStyle>
        <Transformation>
          <ogc:Function name="ras:Jiffle">
            <ogc:Function name="parameter">
              <ogc:Literal>coverage</ogc:Literal>
            </ogc:Function>
            <ogc:Function name="parameter">
              <ogc:Literal>script</ogc:Literal>
              <ogc:Literal>
                nir = src[7];
                vir = src[3];
                dest = (nir - vir) / (nir + vir);
              </ogc:Literal>
            </ogc:Function>
          </ogc:Function>
        </Transformation>
        <Rule>
          <RasterSymbolizer>
            <Opacity>1.0</Opacity>
            <ColorMap>
              <ColorMapEntry color="#000000" quantity="-1"/>
              <ColorMapEntry color="#0000ff" quantity="-0.75"/>
              <ColorMapEntry color="#ff00ff" quantity="-0.25"/>
              <ColorMapEntry color="#ff0000" quantity="0"/>
              <ColorMapEntry color="#ffff00" quantity="0.5"/>
              <ColorMapEntry color="#00ff00" quantity="1"/>
            </ColorMap>
          </RasterSymbolizer>
        </Rule>
      </FeatureTypeStyle>
    </UserStyle>
  </NamedLayer>
</StyledLayerDescriptor>

JTS Upgrade

Java Topology Suite (JTS) has been upgraded to version 1.16. This marks a significant change in package naming, the library has switched from “com.vividsolutions” to “org.locationtech”  packages and all GeoServer code has been updated to follow suit.

This has some side-effects on output produced by REST featuretype and structured coverage requests, specifically the package names used for geometry types in the binding parameter of any geometry attributes.

Any REST clients which rely on this binding information should be updated to support the new names. GeoServer will still support reading the old “com.vividsolutions” names, but will only output the new”org.locationtech” names.

For more details, refer to the upgrade guide in the GeoServer documentation.

Java 11 is released tomorrow! GeoServer has a window until January 2019 before Java 8 is no longer officially supported!

To make the transition the GeoServer team is setting up a Java 2018 Code Sprint – and we need your support to help enough participants attend!

• October 22-26th
• Groups gathering in North America, Europe and Oceania

With recent policy changes setting the Java platform on a six-month release cycle. We also have significant work ensuring the libraries we use either work with the “jigsaw” module system or are replaced.

Already we have identified changes needed for GeoServer to run at all:

• Upgrade Spring: The application framework uses the reflection feature of Java to wire GeoServer together – and needs to be updated to work with the additional Java 11 restrictions.
• Upgrade Log4J: A Java 11 compatible version of Log4J is available and provides tools for visualization and exploring log messages.
• Repackage the application adding automatic module names

Our goal is to ensure that the next release of GeoServer can run with Java 8 or Java 11.

How to participate

Please visit the osgeo wiki page and add yourself to the list of participants. We are trying to bring as contributors together as possible and would love it if you could join us!

In addition to GeoServer representatives from GeoTools and GeoNetwork will be taking part.

How to sponsor

We have three sponsorship levels available, with contributions devoted to helping participants attend:

• Gold: $7500 USD
• Silver: $1500 USD
• Bronze: $750 USD

Sponsor logos are included on the event page and blog posts in addition to being featured in the associated project release announcements. More importantly your financial support goes towards making sure GeoServer remains available on a supported Java platform.

Please see the wiki page for details on how to sponsor.