GeoServer 2.12.3 Released

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

This is a maintenance release and a recommend update production systems. This release is made in conjunction with GeoTools 18.3.

Highlights of this release are featured below, for more information please see the release notes (2.12.3,2.12.2, 2.12.12.12.0 | 2.12-RC1 | 2.12-beta).

Improvements

  • Improved bounding box reporting in WMS GetCapabilities allowing more entries to be supported when Output bounding box for every support CRS is selected. Bounding boxes are now returned for layer groups as well.
  • NetCDF/GRIB has been improved with a new setting to copy over global attributes when generating NetCDF output

Bug Fixes

  • WFS 2.0 fix for interaction with startIndex and the total features count
  • CQL filters can now be used with the WMS vector tile output format
  • GeoPackage WPS output corrected to generate y coordinates from bottom left
  • User interface for editing workspace details checks for conflicts with name or namespace URI.
  • GML 3.2 output can now limit the number of decimals used for coordinate output
  • REST management of styles now supports defining a style using POST for CSS, YSLD and MapBox styles (previously this only worked for SLD)
  • WPS output error handling does a better job reporting when Async output format parameters are incorrect.
  • WPS improvements have also been made for the cleanup of temporary folders and output “raw data encoder” (which is often used for image generation).
  • Demo request page does a better job of of reporting authorization failures, and correctly sending credentials for testing service security.
  • GetLegendGraphic fixes to correct line thickness and ensure polygons and points are not cut off.

Community Updates

For developers building from source our community modules remain a great place to collaborate on new functionality and improvements. This month Nuno Oliveira has added a new community module for the GeoTools MongoDB datastore.

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.12 Series

Additional information on the 2.12 series:

GeoServer 2.13.0 released

We are happy to announce the release of GeoServer 2.13.0. Downloads are available (zipwar, 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:

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.

Other assorted improvements

A single bug got fixed since the RC, for more information please see the release notes (2.13.02.13-RC1 | 2.13-beta):

  • CQL filter not working when asking for vector tiles in wms request, GEOS-8065

 

GeoServer 2.13-RC1 Released

We are happy to announce the release of GeoServer 2.13-RC1. Downloads are available (zipwar, 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:

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.

Other assorted improvements

New bug fixes and improvements since the beta are featured below, for more information please see the release notes (2.13-RC1 | 2.13-beta):

  • Async WPS does not report wrong output parameters
  • GetFeatureInfo requires high clicking precision when the WMS “max buffer” setting is zero
  • totalFeatures for WFS 2.0 request returns wrong count
  • CoverageStore HTML REST representation points to a coverage named after the store (instead of its actual name)
  • WPSDownload: per-granule resolution on target resolution
  • GeoWebCache fails to compute sub-gridset bounds for layers whose native CRS is wrong/cannot be recognized
  • Regression: GetLegendGraphics renderer lines thicker than they should
  • Backup/restore reports completion too soon

Test, test, test!

Now that you know about all the goodies, please go, download and test your favourite ones. Let us know how it went!

About GeoServer 2.13

GeoServer 2.13 is scheduled for March 2018 release.

GeoServer 2.13-beta released

We are happy to announce the release of GeoServer 2.13-beta. Downloads are available (zipwar, 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:

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.

Other assorted improvements

There are many bug fixes and improvements to look at in the release notes, cherry picking a few here:

  • Upgrade JDom library
  • REST API CORS support
  • REST improvements to list all layers in a workspace, and include the workspace prefix in layer listings
  • Style POST does not support non-SLD styles
  • Add WMTS RESTful API
  • Installing the XSLT plugin may cause random REST endpoints to report lists with transforms/transform
  • WCS 1.0.0 does not handle FORMAT parameter properly
  • Cache small amount of features in memory to avoid repeated data scans in GetFeature requests
  • Allow requesting both OL3 and OL2 from the client side
  • Simple feature GML 3.2.1 output schema-invalid as geometries lack mandatory gml:id
  • GeoPackage generated via WPS has y coordinates starting from bottom left
  • Numerous WFS 2.0 bugfixes (WFS 2.0 CITE compliance related)
  • WMTS bugfixes, improving CITE compliance
  • Submitting a seed/truncate request for a tile layer results in a “406, not acceptable”
  • GWC Seed Form returns “Chunk [] is not a valid entry” message error when seeding a layer.
  • Demo Page does not send password
  • Importer can now add computed fields (with CQL expressions) during imports
  • NetCDF output format has a new option to copy global attributes from the source NetCDF file

Test, test, test!

Now that you know about all the goodies, please go, download and test your favourite ones. Let us know how it went!

About GeoServer 2.13

GeoServer 2.13 is scheduled for March 2018 release.

GeoServer 2.11.5 released

We are happy to announce the release of GeoServer 2.11.5. Downloads are available (zipwar, 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.22.11.12.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).

GeoServer 2.12.2 Released

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

This is a stable release recommended for production use. This release is made in conjunction with GeoTools 18.2.

Highlights of this release are featured below, for more information please see the release notes (2.12.2, 2.12.12.12.0 | 2.12-RC1 | 2.12-beta).

New Features and Improvements

  • GetLegendGraphic rescale accounts for stroke thickness
  • WPS requests now support the use of CDATA to guard ComplexData
  • CSS expressions with units are now supported

Bug Fixes

  • Importer an now import shape files with spaces in the attribute names to PostGIS
  • An intermittent problem with WFS filter encoding has been resolved.
  • User interface improvements for layer group creation
  • Our community modules remain under active development with fixes to scripting, mbstyle, and backup and restore.

About GeoServer 2.12 Series

Additional information on the 2.12 series:

GeoServer 2.11.4 Released

The GeoServer team are pleased to announce the release of GeoServer 2.11.4. Downloads are available (zipwardmg, and exe) along with documentation and extensions.

GeoServer 2.11.4 is a maintenance release of the GeoServer 2.11.x series recommended for production system. This release is made in conjunction with GeoTools 17.4 and GeoWebCache 1.11.3.

This release contains bug fixes as well as new features. For more information, please see the release notes (2.11.4 | 2.11.3 |  2.11.22.11.12.11.0 | 2.11-RC1 | 2.11-beta).

New Features

  • Support for MongoDB as a source data store for app-schema.
  • Support for GeoJSON output for complex features (app-schema).

About GeoServer 2.11

  • OAuth2 for GeoServer (GeoSolutions).
  • YSLD has graduated and is now available for download as a supported extension.
  • Vector tiles has graduated 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).

GeoServer 2.12.1 Released

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

This is a stable release recommended for production use. This release is made in conjunction with GeoTools 18.1.

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

New Features and Improvements

  • Moved Users/Groups/Roles REST from geofence-server (extension) to restconfig (core)

Bug Fixes

  • Copy style needs to copy content and format
  • REST API CORS support
  • YSLD ColorMap incorrectly recording a String (as shown in SLD conversion)
  • MapPreviewPage search displays wrong results on first try
  • GWC Seed Form returns blank page when seeding a layer.
  • Monitor REST API won’t return xml/json representation for request
  • Failed to resolve workspace for style messages during startup

About GeoServer 2.12 Series

Additional information on the 2.12 series:

GeoServer 2.11.3 released

We are happy to announce the release of GeoServer 2.11.3. Downloads are available (zipwardmg and exe) along with documentation and extensions.

GeoServer 2.11.3 is the first maintenance release of the GeoServer 2.11.x series recommended for production system. This release is made in conjunction with GeoTools 17.3.

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

New Features and Improvements

  • KML has two new options to control polygon placemark placement, to force it within the current view, and to make sure it’s inside polygons regardless of the polygon shape
  • The layer preview allows filtering on raster layers such as mosaics and image pyramids (which can apply the filter on the underlying mosaic index)

Bug Fixes

  • Improvements on pre-build legend treatment in GetLegendGraphic, now works against a layer default style too, and for workspace specific styles
  • GDAL bindings jars restored in the build, making it easier to use the pre-built native support (as opposed to custom built ones, for those remember to remove them)
  • Raster rendering fixes: no more empty output when asking for highly oversampled rasters in WMS, make sure new image mosaic tiles are rendered even if outside the original bounds in image mosaic
  • GWC related improvemenets, seed links now working when running behind a proxy, and more strict checks for non cacheable requests over the WMS service endpoint (especially useful when using direct integration)
  • GeoServer now changes the SLD version number when uploading a SLD 1.1 overwriting a SLD 1.0 file using the REST API (especially useful for QGIS and GeoNode integrations). The UI was not affected by this issue.
  • 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).

GeoServer 2.12.0 Released

We are happy to announce the release of GeoServer 2.12.0. Downloads are available (zipwardmg and exe) along with docs and extensions.

This is a stable release recommended for production use. This release is made in conjunction with GeoTools 18.0.

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 have remain unchanged and we would like to thank everyone who took part.

We should also thank David Vick who migrated the embedded GeoWebCache REST API, and the entire team who helped him reintegrate the results for this 2.12.0 release.

Thanks again to the code sprint sponsors and in-kind contributors:

Gaia3d   atol_logo  Boundless_Logo    How2map_logo     fossgis_logo  iag_logo  

As part of this upgrade, we also have new REST documentation, providing detailed information about each endpoint. The documentation is written in swagger, allowing different presentations to be generated as shown below.

 

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.

GeoServer has long supported this functionality for clients, via an external SLD file. This change allows more people to use the idea of a single file defining their map layers and styling as a configuration option.

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 to “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 labelling features and QGIS compatibility

A number of small new features have been added to labelling 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

../../../_images/charSpacing.png

  • 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 is more good news for those that handle mosaics 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 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 favouring smallest cloud cover, the second one favouring 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.

Other assorted improvements

Highlights of this release featured below, for more information please see the release notes (2.12.0 | 2.12-RC12.12-beta):

  • Users REST uses default role service name as a user/group service name
  • imageio-ext-gdal-bindings-xxx.jar not available in geoserver-2.x.x-gdal-plugin.zip anymore since 2.10
  • REST GET resource metadata – file extension can override format parameter
  • GeoServer macOS picks up system extensions
  • SLD files not deleted when SLD is deleted in web admin
  • Reproject geometries in WMS GetFeatureInfo responses when info_format is GML
  • Include Marlin by default in bin/win/osx downloads, add to war instructions
  • Handle placemark placement when centroid of geometry not contained within
  • Enable usage of viewParams in WPS embedded WFS requests
  • Add GeoJson encoder for complex features
  • Allow image mosaic to refer a GeoServer configured store
  • Duplicate GeoPackage formats in layer preview page
  • ExternalGraphicFactory does not have a general way to reset caches
  • Generating a raster SLD style from template produced a functionally invalid style, now fixed
  • Style Editor Can Create Incorrect External Legend URLs
  • Namespace filtering on capabilities returns all layer groups (including the ones in other workspaces)

 

About GeoServer 2.12 Series

Additional information on the 2.12.0 series:

Download GeoServer