GeoServer Blog

GeoServer 2.10.2 released

The GeoServer team is pleased to announce the release of GeoServer 2.10.2. Download bundles are provided (binwardmg and exe) along with documentation and extensions.

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

New Features and Improvements:

  • Promote YSLD module to extension

  • Add jetty-servlets.jar file to default jetty to help users set up CORS

  • Handle non error http codes (from HttpCodeException) as normal response

  • Reducing output size of PDF with graphic fills by using tiling patterns

Bug Fixes:

  • Disk quota usage page no longer shows negative bytes free (if you already have negative values in your quota DB, follow this instructions)

  • New style editor can now detect and fix old GeoServer CSS styles (which were marked as SLD)

  • Fixes to json output for layergroup

  • Can not display table based pages in Turkish locale

  • WMS 1.3.0 GetCapabilities response doesn’t validate against the schema when using LayerGroups

  • Editing style and moving it into workspace loses the edits

  • Style Edit Page: Apply then Submit causes WicketRuntimeException

  • Force transformation of ROI and NoData to transparent/bg color in direct raster rendering path

And more! For more information on this release check the release notes (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:

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

Read More

GeoServer Code Sprint 2017

GeoSolutions has offered to host the GeoServer team for a Java 2017 code sprint to look at updating, fixing and documenting the the GeoServer REST API. The GeoServer REST API is used to remotely manage a GeoServer instance and has proven highly successful for automation, integration with other applications, with libraries for java and python remote management.

rest-api

The code sprint is dedicated to:

  • Migrating from the restlet library to Spring MVC library. As an early adopter GeoServer selected the restlet library as best of breed at the time. It has not aged well, and Spring MVC represents a supported annotation based solution that is familiar to more developers.

  • Although popular the REST API has not attracted a lot of investment, leading it to have the highest bug count of any of our GeoServer modules! This sprint would like to directly reduce this bug count, and indirectly reduce this bug count by introducing more developers to this area of the codebase.

  • The REST API also has the greatest number of requests for documentation and examples. This code sprint will update the documentation for each area of the REST API as as it is migrated, and look at some of the solutions for the automated collection of examples requests.

  • We will be sure to test against the gsconfig python library and geoserver-manager java library.

The GeoServer team has previously planned and executed a highly successful code sprint. We would like to once again ask for your support and participation in 2017.

Viareggio, Lucca

The code sprint is planned for a week in March in the glamorous GeoSolutions headquarters of Viareggio, Lucca. Thanks to GeoSolutions for providing a venue, space is limited to 10-15 people so hit the wiki to sign up if you are interested.

Viareggio,_passeggiata_a_mare_2

A note on the timing: We were unable to join the Daytona Code Sprint 2017 as it is scheduled too close to the GeoServer 2.11 code freeze. GeoSolution’s offer to host in Europe will reduce travel costs allowing us to run the event with minimal sponsorship.

Participation and Sponsorship

We have the following sponsorship levels available:

  • Gold: $1000

  • Silver: $500

  • Bronze: $250

We are reaching out to international and local sponsors. Contributions will be put towards travel costs for overseas sprinters who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprints.

For more details on participation, sponsorship or budget for the event please see the Java 2017 Code Sprint 2017 on the OSGeo wiki.

Read More

GeoServer 2.10.1 Released

The GeoServer team is pleased to announce the release of GeoServer 2.10.1. Download bundles are provided (binwardmg 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:

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

Read More

GeoServer 2.9.3 Released

The GeoServer team is pleased to announce the release of GeoServer 2.9.3. Download bundles are provided (binwardmg 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.

The team has been working hard, resulting in a wide range of bug fixes:

  • Windows installer fixed allowing port to set for standalone or service use

  • KML Output managed a date-month swap when used in a non-POSIX locale.

  • Improved documentation for the demo pages, including the WCS Request builder.

  • CSS stroke-offset now supports expressions

  • WMS GetCapabilities fix for inadvertently show layer group contents multiple times.

  • Style generation fix for raster data layers

  • Coverage view improvements include preservation of origional band names, and alpha band if available.

  • WFS correctly handles disabled stores

  • REST API

    • Correctly represent empty true/false values for html output

    • Representation of an empty styles list in JSON fixed

    • Cascade delete fixed to correctly handle nested layer groups

  • JMS Clustering has received a number of fixes: correctly handles virtual service configuration, propagation of workspace and service settings.

  • Lots of bug fixes (check the release notes for details)

For more information about GeoServer 2.9.3 refer to release notes (2.9.3 2.9.2   2.9.1   2.9.0   RC1   beta2   beta   M0 ).

Community Modules

Community module updates:

  • A community module is now available allowing GeoServer to authenticate against the OAuth2 protocol (including Google OAuth2).

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.9

Articles, docs, blog posts and presentations:

##

Read More

The new and improved GeoServer Style Editor

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.

screen-shot-2016-11-14-at-10-44-21-am

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.

screen-shot-2016-11-14-at-9-16-24-am

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. screen-shot-2016-11-14-at-9-54-09-am

  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. screen-shot-2016-11-14-at-10-24-17-am

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:

screen-shot-2016-11-14-at-10-05-29-am

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. screen-shot-2016-11-14-at-10-05-43-am

  2. To allow our style to be used as an alternative style for firestations and hospitals click the checkbox under the Associated column. screen-shot-2016-11-14-at-10-06-55-am

  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. screen-shot-2016-11-14-at-9-17-59-am

  2. The style editor remains at the bottom of the page when switching tabs, so we can go ahead and modify our style: screen-shot-2016-11-14-at-9-18-26-am

  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: screen-shot-2016-11-14-at-9-18-50-am

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. screen-shot-2016-11-14-at-9-19-09-am

  2. The Min/Max statistics can be calculated using the “Compute” link. Let’s take a look at the range of elevations:screen-shot-2016-11-14-at-10-08-49-am

  3. We can use this information to set the colour of the points based on their elevation, using the Interpolate function: screen-shot-2016-11-14-at-10-18-15-am

  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: screen-shot-2016-11-14-at-10-18-06-am

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.

Read More