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

This is a maintenance release recommended for production use (for newer projects please use the 2.14.x series, as this is last community sponsored 2.13.x release). This release is made in conjunction with GeoTools 19.4 and GeoWebCache 1.13.4.

Improvements and Fixes

• Significant speedup in WMTS capabilities document generation when source data is not in WGS84

• GeoPackage improvements, speed up raster reading and reprojection, make sure global coverage GeoPackage can be displayed

• Removed gml:id attribute from GML 3.1 encoding (was added in previous releases by mistake)

• NetCDF output format improvement, fixing projection coefficients in some cases, make sure data packing takes into account all data slices when calculating linear transformation coefficients

• WCS 2.0 compliance improvements, DescribeCoverage output schema compliance fixes when using GeoServer extensions, returning correct exception type when subsetting request is out of range on time/elevation/custom dimension axis

• KML request handling fixes, support for sortBy and CQL filtering on layer groups

• GWC related fixes, could not modify blobstore configuration without changing its name too, wrong axis order in configuration when saving EPSG:4326 gridset configurations

• Styling related improvements, cannot read dynamic SLD served by an apache server, SLD 1.1 posted to the REST API resulted in garbled content

• And various others, please see the release notes for details

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

This is a stable release of the GeoServer 2.14 series and is recommended for all production systems. Users of prior releases of GeoServer are encouraged to upgrade.

This release is made in conjunction with GeoTools 20.1 and GeoWebCache 1.14.1. Thanks to all who contributed to this release.

Improvements and Fixes

This release includes a number of new features and improvements:

• New coordinate formatting options for WFS layers

• REST API granule management remove of metadata or all

• Coverage view support for indexed color model

• Check handling of WCS 2.0 time/elevation/range subsetting

• WFS 1.1.0 handling of gml:id

• WFS Shapefile and GeoJSON output now support geometry with measures

• Fixes to the start.bat and shutdown.bat scripts on windows

About GeoServer 2.14 Series

Additional information on the GeoServer 2.14 series:

• New MongoDB extension added

• Style editor improvements including side by side editing

• Nearest match support for WMS dimension handling

• Upgrade notes documenting REST API feature type definition change

• State of GeoServer 2.14 (SlideShare)

• GeoServer Ecosystem (SlideShare)

• GeoServer Developers Workshop (SlideShare)

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

This is a maintenance release recommended for production use (for newer projects please use the 2.14.x series, as 2.13.x will cease to be supported in a few months). This release is made in conjunction with GeoTools 19.3 and GeoWebCache 1.13.3.

Improvements and Fixes

• Allow selection of geometry attribute in app-schema, support mapping files over HTTP connection, push spatial filters over nested geometries down into SQL when possible

• Performance improvement when reporting dimension values in WMS capabilities, for dimensions out of raster data and presented as “interval and resolution”

• WCS thread safety fixes when using requests with reprojection and rescaling under high load. Also, when requesting an area inside the bounds of a sparse mosaic, the result might have had less pixels than requested.

• CSS translator fixed to support mark offset/anchors based on expressions

• File chooser autocomplete had duplicate entries on Linux

• REST config, it was not possible to set the default style using a layer PUT

• GetLegendGraphic ignores the OnlineResource configured in the style for raster layers

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

Last week the Brazilian government released a list of government agencies that have already implemented their spatial data infrastructure (SDI). This list has 21 agencies, and the interesting thing is that 18 out of 21 use GeoServer in their SDI.

Portal of Brazil’s spatial data infrastructure

Brazil has a 2008 decree, which establishes the creation of spatial data infrastructure by government agencies, and since then, this process of spatial data availability has been growing in the country.

Below, the GeoServer address of some of these agencies:

• National Telecommunications Agency (Anatel)

• National Bank for Economic and Social Development (BNDES)

• Brazilian Agricultural Research Corporation (Embrapa)

• Brazilian Institute of Geography and Statistics (IBGE)

• Brazilian Institute of Environment and Renewable Natural (IBAMA)

A spatial data infrastructure (SDI) is a data infrastructure implementing a framework of geographic data, metadata, users and tools that are interactively connected in order to use spatial data in an efficient and flexible way (Wikipedia, 2018).

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.