GeoServer Blog

GeoServer 2.19.1 Released

We are happy to announce GeoServer 2.19.1 release is available for download (zip and war) along with docs and extensions.

This GeoServer 2.19.1 release was produced in conjunction with GeoTools 25.1 and GeoWebCache 1.19.1. this is a stable release recommended for production systems.

Thanks to everyone who contributed, and to Jody Garnett (GeoCat) for making this release.

Improvements and Fixes

Several new features are included in this release:

  • GetFeatureInfo can now includes ColorMap labels for the location clicked, check out the tutorial.
  • A new styling vendor option inclusion to control control legend generation for WMS GetLegendGraphic using values of legendOnly, mapOnly, or normal to define how a style element is used.

Notable improvements:

  • Improve parameter extractor logging
  • Customization of complex GeoJSON WFS output is now available for other data stores, previously this was restricted attributes marked @dataType by the AppSchema plugin.
  • SLD Service now places a limit, configured by system variable ``-Dorg.geoserver.sldService.maxUniqueRange=1024`, of the number of unique intervals.

Fixes included in this release:

  • Fix elevation key-value-pair parser (used in WMS GetMap) handling of edge cases such as zero intervals
  • Fix importer application of gridset bounds, (ot was not working correctly when GWC DiskQuote in use)
  • Inspire schemas URL updated to their new HTTPS location
  • WCS 2.0 slicing on lat/long fix, was sometimes returning adjacent pixel
  • WMS Layers with dimensions were missing from GetCapabilities when using catalog security challenge mode.
  • App Schema download was missing a required jar.
  • Improvements helping coverage format compatibility with file references
  • Address GeoFence interaction with non global named tree container
  • Address WPS Download animation out of memory issues
  • Address rendering process regression with use of vendor option sortByGroup resulting in “internal error rendering process failed”

Internal:

  • Upgrade to commons-io 2.8.0
  • Autoformat maven pom.xml files

For details check the 2.9.1 release notes.

About GeoServer 2.19

Additional information on GeoServer 2.19 series:

Release notes ( 2.19.1 | 2.19.0 | 2.19-RC )

Read More

GeoServer 2.18.3 Released

We are pleased to announce the release of GeoServer 2.18.3 with downloads ( war | bin ), documentation and extensions.

This release is made in conjunction with GeoTools 24.3 and GeoWebCache 1.18.3. This is a maintenance release recommended for production systems.

Thanks to everyone who contributed, and Ian Turton (Astun) and Jody Garnet (GeoCat) for making this release.

Improvements and Fixes

This release includes a number of enhancements and fixes in core and extensions:

  • Add LayerGroup support to Geofence,
  • ColorMap labels in raster layer GetFeatureInfo response
  • New web-service-auth community module
  • Add GeoServer environment parametrization support to Base Proxy configuration
  • Include layer name(s) in WMS ServiceException for GetMap

For more information check the 2.18.3 release notes.

About GeoServer 2.18

Additional information on GeoServer 2.18 series:

Read More

GeoServer 2.19.0 Released

We are happy to announce GeoServer 2.19.0 release is available for download (zip and war) along with docs and extensions.

This GeoServer 2.19.0 release was produced in conjunction with GeoTools 25.0 and GeoWebCache 1.19.0.

Thanks to everyone who contributed and helped test this release. Developer adding new features are credited in the sections below. Release candidate testing was performed by Andrea Aime, Bart Verbeeck, Christoforos Vradis, Georg Weickelt, Graham Humphries, Ian Turton, Jody Garnett, Peter Rushforth, Richard Duivenvoorde, Russell Grew, and Simone Giannecchini. With all the new extensions being added we appreciated those testing the release candidate packaging.

Thanks to Alessandro Parma (GeoSolutions) and Andrea Aime (GeoSolutions) for making this release.

MapML extension

In this release, MapML has graduated from community module to extension status. Map Markup Language (MapML) is a proposed extension to HTML, for maps. The objective of the project is to standardize accessible, performant Web maps with native support from Web browsers (maps in HTML). The GeoServer MapML extension will closely track the MapML specification as it evolves. Find out more at https://maps4html.org/, and if you like our goals, join the community group!

The MapML extension works with GeoServer layers and layer groups, and uses WMS, WMTS and WFS facilities built into GeoServer to provide simple map previews layers. The layer previews can be “dragged” from one browser tab onto another map preview to visualize a mashup of the layers of layer groups using the built in MapML viewer.

MapML Layer properties panel
Editing a layer’s MapML properties in the Layers panel

MapML gridsets in the Layers Tile Caching tab
Editing a layer’s MapML gridsets in the Layers panel Tile Caching tab

MapML Preview link is added to the Layer Preview page
Preview a layer in the MapML viewer by following the MapML link

MapML previews can be mashed up by dragging the URL of one preview onto another
Mash up MapML previews by drag and drop

The Maps for HTML community would like to thank Andrea Aime, Jody Garnett and the GeoServer PSC for their support and help in getting this extension published.

More information on the GeoServer MapML extension is available in the user guide

WPS JDBC extension

The WPS JDBC extension allows to share the status of asynchronous WPS requests across a GeoServer cluster. The status of all requests, past and ongoing, can be stored in a database, for later reference.

The module uses GeoTools JDBC stores to access databases, create the necessary tables, and track status. Connection parameters are provided as property files, e.g.:

user=postgres
port=5432
password=******
passwd=******
host=localhost
database=gsstore
driver=org.postgresql.Driver
dbtype=postgis

For more information, refer to the module documentation.

We’d like to thank Ian Turton for developing the module on behalf of GeoSolutions, Alessio Fabiani (GeoSolutions) for providing documentation for it, and Andrea Aime (GeoSolutions) for performing the QA and graduation steps.

WPS Download extension

The WPS download plugin provides support for the download of large amounts of data, allowing use of asynchronous requests, where using WFS, WCS or WMS for the same task would lead to HTTP timeouts. Also, download limits can be configured to avoid excessively large requests: size in MB, number of features, number of animation frames.

In particular, the following processes are available:

  • DownloadEstimator, verifying that a raster/vector download about to be attempted will fit the download limits.
  • DownloadProcess, allowing to download either raster or vector data, reproject and clip them
  • DownloadMapProcess, allows to download a large map matching what is visible on a client (which may be using tiles and display on a multi-screen), eventually dynamically fetching layers from remote WMS servers as well. It’s also possible to decorate the final map using the standard decoration layouts.
  • DownloadAnimationProcess, allows to build a MP4 movie given a set of layers and times.

GeoNode uses the module to allow download of datasets, eventually clipped and filtered to the current view. The asynchronous download allows to download large datasets, and retrieve them later, once ready.

GeoNode download
Initiating a download in GeoNode

GeoNode download
Configuring the download

GeoNode download
The download package is ready

GeoNode download
Viewing the clipped download in QGIS

For more information, refer to the module documentation.

Thanks to Alessio, Andrea, Daniele, from GeoSolutions, for developing the extension, and GeoNode/MapStore for testing it in various production environments.

WMTS Multidimensional extension

The WMTS multi-dimensional extension is an extension to the WMTS protocol developed during OGC Testbed 12. The extension allows to explore the dimensions attached to a dataset, providing ways to explore them, finding relationships between them.

Here are a couple of real world examples of this functionality:

  • GeoServer is publishing a set of satellite images. Each image is time stamped. The user is browsing the set of data on a map, and the client software wants to show the list of available times for the current area. The WMS/WMTS dimension support cannot help, but the WMTS extension has a request, GetDomainValues, which exactly answers this question.
  • GeoServer is publishing a set of NetCDFs containing weather forecasts. Each dataset has two times associated, a run time (the time the forecast was run) and a time (the predicted time for the weather data). Forecasts are run for the short term future, so the two times are strictly related. A user wants to compare forecasts for a given predicted time. The GetDomainValues request can be used to locate the run times that have a prediction for the given forecast time.
  • GeoServer is publishing a set of timestamped data. The client wants to display a timeline, providing an idea of which times are available for the current view. In addition to that, the clients wants to display how many datasets are available along the timeline. The GetHistogram request can be used to retrieve a count of datasets available over time buckets in a given interval.

The MapStore client uses the module to power its timeline extension, providing time discovery, navigation, animation, and histogram display.

MapStore timeline plugin, with animation controls
MapStore timeline plugin, with animation controls

MapStore timeline plugin, histogram view
MapStore timeline plugin, histogram view

The plugin partially replaces the WMS animator functionality, which is going to be deprecated (since it’s memory bound, and can only be accessed with a synchronous request).

For more information, refer to the module documentation.

Thanks to Nuno Oliveira (GeoSolutions) and Andrea Aime (GeoSolutions) for the initial development, and MapStore for adopting the module, using it in production, and ensuring its long term development

Params-extractor extension

The parameter extractor module is used to inject vendor parameters in all links that a standard OGC client uses, by either reflecting them into the Capabilities documents backlinks, or hiding them in an extra component in the URLs paths.

This can be used, for example, to provide a desktop client, such as QGIS, a different view of a given layer based on viewparams, cql_filter or env parameters, even if the client would not be able to use the parameters natively. Each combination of parameters receives a different starting GetCapabilities request.

A simple query parameter echoing can be setup for clients honoring query parameters in capabilities backlinks:

Parameter echoing
Parameter extractor echoing

For clients ignoring query parameters or even ignoring backlinks, the parameters can be added as a path component instead, and then expanded in a larger templated value:

Parameter extraction
Parameter expansion from path component

With the above setup, a URL ending with H11:

/geoserver/tiger/wms/H11?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap

is interpreted as:

/geoserver/tiger/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&CQL_FILTER=CFCC%3D%27H11%27

For more information, refer to the module documentation.

Thanks to Nuno Oliveira (GeoSolutions) for developing this module.

GeoWebCache-S3 extension

The GeoWebCache S3 blobstore allows storage of GeoWebCache tiles in a S3 bucket. It has been also tested with a few other S3 compatible blob storage mechanisms, such as Minio.

This plugin is particularly useful when deploying GeoServer on AWS, but also when setting up a shared tile storage in Kubernetes.

Parameter extraction
Setting up the S3 tile storage

For more information, refer to the module documentation.

Retire ArcSDE Extensions

The ArcSDE Extension has been retired.

In this case we found that the extension is no longer actively used, and lacked sufficient feedback and resources for continued development. The last tested ArcSDE 10.2.2 version is no longer available, making the required jars required for installation unavailable.

Retire the Script community module

The Script community module has been retired.

The module provided scripting abilities for GeoServer, allowing to add WPS processes and small REST services in scripting languages, and storing them in the data directory.

Unfortunately the module fell un-maintained and would no longer build nor work.

JTS 1.18.1

GeoServer 2.19.0 includes the latest JTS Topology Suite 1.18.1 release, the headline feature is an optional “Overlay Next Generation” implementation that should provide a performance improvement for operations such as tile generation, vector tiles, and get map requests.

To try it out use the system property -Djts.overlay=ng - the effect should be small as we already have several optimizations in place before trying this now faster JTS Overlay.

Thanks to Martin Davis (Crunch Data) and James Hughes (CCRi) for making JTS 1.18.1 available during our release window.

Codebase updates and Quality Assurance

GeoServer continues to be build with the latest open source technologies:

  • GeoTools 25.0
  • GeoWebCache 1.19.0
  • JTS 1.18.1
  • JAI-EXT 1.1.19
  • GeoFence 3.4.7
  • Upgrade oshi-core from 5.4.0 to 5.5.0 for new Apple hardware support
  • Freemarker 2.3.31

We do not get a chance to talk about the code-base that makes up GeoServer often, but recent changes and improvements deserve some praise. The GeoServer team has really embraced automating code checks, starting with simply formatting the code in a consistent fashion, to more advanced techniques checking for common mistakes.

  • Switch most of the unit tests from JUnit 3 to JUnit 4
  • Remove usage of Vector/Hashtable, replace with ArrayList and HashMap, add PMD rule to enforce it
  • Remove un-necessary casts from code, add PMD rule to enforce it
  • Replace try/finally with try-with-resources, add a PMD rule to enforce it
  • Collapse catch statements with the same body in a multi-catch, add PMD rule to enforce it
  • Avoid assertTrue for tests that can be expressed with dedicated assertions. Add PMD rule to enforce it.
  • Replace iterator loops with enhanced for loops, add a QA rule to enforce it.
  • Run PMD checks on test sources as well.
  • Use Collection.isEmpty() when checking for item availability
  • Remove explicit types when diamond operator can be used instead. Added a PMD rule to enforce it.
  • Remove or suppress unchecked casts, enable the Java compiler lint option for it.

Although all these changes sound small in isolation, the fact that they are performed on the entire codebase, and checked each time a pull-request is proposed, really provides confidence in the technology we publish.

Thanks to Andrea for this valuable work.

And more!

There are several other new features and improvements, including:

Find out more in the release notes.

About GeoServer 2.19

Additional information on GeoServer 2.19 series:

Read More

GeoServer repository transition to main branch

The GeoServer project is changing our default branch to main.

The casual use of the words “master” and “slave” in computer software is an unnecessary reference to a painful human experience that continue to impact society.

The change is part of an industry shift made possible by the git, bitbucket, github and gitlab projects. The git command line, repository implementations, now support main as default branch setting.

To update your local repository:

git branch -m master main
git fetch upstream
git branch -u upstream/main main

To configure your local git tool so that new repositories are created with a main branch:

git config --global init.defaultBranch main
Read More

GeoServer 2.19-RC Released

We are happy to announce GeoServer 2.19-RC release candidate is available for testing. Downloads are available (zip and war) along with docs and extensions.

This is a GeoServer release candidate made in conjunction with GeoTools 25-RC and GeoWebCache 1.19-RC.

  • Release candidates are a community building exercise and are not intended for production use.
  • We ask the community (everyone: individuals, organizations, service providers) to download and thoroughly test this release candidate and report back.
  • Participating in testing release candidates is a key expectation of our open source social contract. We make an effort to thank each person who tests in our release announcement and project presentations!
  • GeoServer commercial service providers are fully expected to test on behalf of their customers.

Release Candidate Testing Priorities

This is an exciting release and a lot of great new functionality has been added. We would like to ask for your assistance testing the following:

  • The number one testing priority is to try out GeoServer with your data! Mass market open source thrives on having many people to review. Scientific open source like GeoServer thrives on exposure to many datasets.
  • Help check that new extension download bundles have contain everything needed, including appropriate readme instructions and open source license information.
  • The rest of this blog post highlights new features for GeoServer 2.19, please try out these features, read the documentation links, and ask questions.

Known Issues:

  • Layer configured with missing style throws NPE

MapML extension

In this release, MapML has graduated from community module to extension status. Map Markup Language (MapML) is a proposed extension to HTML, for maps. The objective of the project is to standardize accessible, performant Web maps with native support from Web browsers (maps in HTML). The GeoServer MapML extension will closely track the MapML specification as it evolves. Find out more at https://maps4html.org/, and if you like our goals, join the community group!

The MapML extension works with GeoServer layers and layer groups, and uses WMS, WMTS and WFS facilities built into GeoServer to provide simple map previews layers. The layer previews can be “dragged” from one browser tab onto another map preview to visualize a mashup of the layers of layer groups using the built in MapML viewer.

MapML Layer properties panel
Editing a layer’s MapML properties in the Layers panel

MapML gridsets in the Layers Tile Caching tab
Editing a layer’s MapML gridsets in the Layers panel Tile Caching tab

MapML Preview link is added to the Layer Preview page
Preview a layer in the MapML viewer by following the MapML link

MapML previews can be mashed up by dragging the URL of one preview onto another
Mash up MapML previews by drag and drop

The Maps for HTML community would like to thank Andrea Aime, Jody Garnett and the GeoServer PSC for their support and help in getting this extension published.

More information on the GeoServer MapML extension is available in the user guide

WPS JDBC extension

The WPS JDBC extension allows to share the status of asynchronous WPS requests across a GeoServer cluster. The status of all requests, past and ongoing, can be stored in a database, for later reference.

The module uses GeoTools JDBC stores to access databases, create the necessary tables, and track status. Connection parameters are provided as property files, e.g.:

user=postgres
port=5432
password=******
passwd=******
host=localhost
database=gsstore
driver=org.postgresql.Driver
dbtype=postgis

For more information, refer to the module documentation.

We’d like to thank Ian Turton for developing the module on behalf of GeoSolutions, Alessio Fabiani (GeoSolutions) for providing documentation for it, and Andrea Aime (GeoSolutions) for performing the QA and graduation steps.

WPS Download extension

The WPS download plugin provides support for the download of large amounts of data, allowing use of asynchronous requests, where using WFS, WCS or WMS for the same task would lead to HTTP timeouts. Also, download limits can be configured to avoid excessively large requests: size in MB, number of features, number of animation frames.

In particular, the following processes are available:

  • DownloadEstimator, verifying that a raster/vector download about to be attempted will fit the download limits.
  • DownloadProcess, allowing to download either raster or vector data, reproject and clip them
  • DownloadMapProcess, allows to download a large map matching what is visible on a client (which may be using tiles and display on a multi-screen), eventually dynamically fetching layers from remote WMS servers as well. It’s also possible to decorate the final map using the standard decoration layouts.
  • DownloadAnimationProcess, allows to build a MP4 movie given a set of layers and times.

GeoNode uses the module to allow download of datasets, eventually clipped and filtered to the current view. The asynchronous download allows to download large datasets, and retrieve them later, once ready.

GeoNode download
Initiating a download in GeoNode

GeoNode download
Configuring the download

GeoNode download
The download package is ready

GeoNode download
Viewing the clipped download in QGIS

For more information, refer to the module documentation.

Thanks to Alessio, Andrea, Daniele, from GeoSolutions, for developing the extension, and GeoNode/MapStore for testing it in various production environments.

WMTS Multidimensional extension

The WMTS multi-dimensional extension is an extension to the WMTS protocol developed during OGC Testbed 12. The extension allows to explore the dimensions attached to a dataset, providing ways to explore them, finding relationships between them.

Here are a couple of real world examples of this functionality:

  • GeoServer is publishing a set of satellite images. Each image is time stamped. The user is browsing the set of data on a map, and the client software wants to show the list of available times for the current area. The WMS/WMTS dimension support cannot help, but the WMTS extension has a request, GetDomainValues, which exactly answers this question.
  • GeoServer is publishing a set of NetCDFs containing weather forecasts. Each dataset has two times associated, a run time (the time the forecast was run) and a time (the predicted time for the weather data). Forecasts are run for the short term future, so the two times are strictly related. A user wants to compare forecasts for a given predicted time. The GetDomainValues request can be used to locate the run times that have a prediction for the given forecast time.
  • GeoServer is publishing a set of timestamped data. The client wants to display a timeline, providing an idea of which times are available for the current view. In addition to that, the clients wants to display how many datasets are available along the timeline. The GetHistogram request can be used to retrieve a count of datasets available over time buckets in a given interval.

The MapStore client uses the module to power its timeline extension, providing time discovery, navigation, animation, and histogram display.

MapStore timeline plugin, with animation controls
MapStore timeline plugin, with animation controls

MapStore timeline plugin, histogram view
MapStore timeline plugin, histogram view

For more information, refer to the module documentation.

Thanks to Nuno Oliveira (GeoSolutions) and Andrea Aime (GeoSolutions) for the initial development, and MapStore for adopting the module, using it in production, and ensuring its long term development

Params-extractor extension

The parameter extractor module is used to inject vendor parameters in all links that a standard OGC client uses, by either reflecting them into the Capabilities documents backlinks, or hiding them in an extra component in the URLs paths.

This can be used, for example, to provide a desktop client, such as QGIS, a different view of a given layer based on viewparams, cql_filter or env parameters, even if the client would not be able to use the parameters natively. Each combination of parameters receives a different starting GetCapabilities request.

A simple query parameter echoing can be setup for clients honoring query parameters in capabilities backlinks:

Parameter echoing
Parameter extractor echoing

For clients ignoring query parameters or even ignoring backlinks, the parameters can be added as a path component instead, and then expanded in a larger templated value:

Parameter extraction
Parameter expansion from path component

With the above setup, a URL ending with H11:

/geoserver/tiger/wms/H11?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap

is interpreted as:

/geoserver/tiger/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&CQL_FILTER=CFCC%3D%27H11%27

For more information, refer to the module documentation.

Thanks to Nuno Oliveira (GeoSolutions) for developing this module.

GeoWebCache-S3 extension

The GeoWebCache S3 blobstore allows to store GeoWebCache tiles in a S3 bucket. It has been also tested with a few other S3 compatible blob storage mechanisms, such as Minio.

This plugin is particularly useful when deploying GeoServer on AWS, but also when setting up a shared tile storage in Kubernetes.

Parameter extraction
Setting up the S3 tile storage

For more information, refer to the module documentation.

Retire ArcSDE Extensions

The ArcSDE Extension has been retired.

In this case we found that the extension is no longer actively used, and lacked sufficient feedback and resources for continued development. The last tested ArcSDE 10.2.2 version is no longer available, making the required jars required for installation unavailable.

Retire the Script community module

The Script community module has been retired.

The module provided scripting abilities for GeoServer, allowing to add WPS processes and small REST services in scripting languages, and storing them in the data directory.

Unfortunately the module fell un-maintained and would no longer build nor work.

Codebase updates and Quality Assurance

GeoServer continues to be build with the latest open source technologies:

  • GeoTools 25-RC
  • GeoWebCache 1.19-RC
  • JAI-EXT 1.1.19
  • JTS 1.18.1
  • GeoFence 3.4.7
  • Upgrade oshi-core from 5.4.0 to 5.5.0 for new Apple hardware support
  • Freemarker 2.3.31

We do not get a chance to talk about the code-base that makes up GeoServer often, but recent changes and improvements deserve some praise. The GeoServer team has really embraced automating code checks, starting with simply formatting the code in a consistent fashion, to more advanced techniques checking for common mistakes.

  • Switch most of the unit tests from JUnit 3 to JUnit 4
  • Remove usage of Vector/Hashtable, replace with ArrayList and HashMap, add PMD rule to enforce it
  • Remove un-necessary casts from code, add PMD rule to enforce it
  • Replace try/finally with try-with-resources, add a PMD rule to enforce it
  • Collapse catch statements with the same body in a multi-catch, add PMD rule to enforce it
  • Avoid assertTrue for tests that can be expressed with dedicated assertions. Add PMD rule to enforce it.
  • Replace iterator loops with enhanced for loops, add a QA rule to enforce it.
  • Run PMD checks on test sources as well.
  • Use Collection.isEmpty() when checking for item availability
  • Remove explicit types when diamond operator can be used instead. Added a PMD rule to enforce it.
  • Remove or suppress unchecked casts, enable the Java compiler lint option for it.

Although all these changes sound small in isolation, the fact that they are performed on the entire codebase, and checked each time a pull-request is proposed, really provides confidence in the technology we publish.

Thanks to Andrea for this valuable work.

And more!

There are several other new features and improvements, including:

Find out more in the release notes.

About GeoServer 2.19

Additional information on GeoServer 2.19 series:

Read More