GeoServer 2.17-RC Released

We are happy to announce GeoServer 2.17-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 23-RC and GeoWebCache 1.17-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!

We will provide a more extensive description of new functionality when GeoServer 2.17 is released.

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.
  • The application download bundles, and extension download bundles have been repackaged. Please help check they contain everything needed, including appropriate readme instructions and open source license information.
  • MBStyle support has received a lot of work and has been packaged up as extension for the first time. Please try this out, and if you work with vector tiles compare the output between client side and server side rendering.
  • The rest of this blog post highlights new features for GeoServer 2.17, please try out these features, read the documentation links, and ask questions.

Known Issues:

  • Download bundles README links to the developers guide are broken

MBStyle module graduated to extension

The MBStyles module has received a deep review and many visual differences have been resolved, to the point that it can now display properly some of the OpenMapTiles styles as-is, with good fidelity, here is an example:

The module has also graduated to extension status, so you will now find it in all releases.

MBTiles community module reading vector tiles

The above map has been rendered not with one functionality, but two! Did you know one can put vector tiles in a MBTiles file? The community module mbtiles-store can read both raster and vector tiles now, and will serve the tiles for vector rendering.

It makes the perfect match with the MBStyle module, one can read vector tiles and render them using the styles they were designed for. Want to give it a quick try? Go to the OpenMapTiles web site and download an area of interest, for personal usage, and configure all layers. Then grab the osm-bright-gl-style, set it up, and configure it as a “style group” layer group type. Done:

Web resource extension

Ever had to fiddle with the data directory on a remote server, maybe trying to setup the control-flow configuration, or upload a Freemarker template? It can be annoying business, one often needs some sort of side access, like SSH. The Resource Browser module, freshly graduated into a supported extension, comes to the rescue, providing a tools page where administrators can browse the data directory, inspect files, edit them, and upload new ones too:

Manage authorization from each resource

Ever added a new layer and forgot to setup security for it? It’s a common occurrence, when the configuration of the layers and its security are done in different pages.

GeoServer 2.17 has a new “Security” tab in each page, allowing you to setup the security for a given resource directly in its configuration page:

Edit security settings there, and the layer security configuration will be updated as a consequence. The same goes for workspaces and layer groups.

Track last change of each resource

GeoServer 2.17 tracks, and allows to show, the date of creation and last modification of major configuration resources, such as workspaces, stores and layers, in their respective list page.

Turn it on in the server configuration page, and see the result in list pages:

This new setting is off by default, you’ll have to go and explicitly turn it on if you care to see the dates.

Map rendering improvements

GeoTools label “shield” support already allowed to put together a graphic along with a label, with the goal of supporting road label shields. GeoServer 2.17.0 includes the ability to lay them out separately, so that the mark and labels are not centered with each other but, for example, one above the other. This allows to setup point markers that appear only as long as their label is showing up too:

It’s also possible to setup a background color for the map at the style level, using a new Background element inside UserStyle. Background is a fill:

<?xml version="1.0" encoding="UTF-8"?><sld:StyledLayerDescriptor xmlns="http://www.opengis.net/sld" xmlns:sld="http://www.opengis.net/sld" xmlns:gml="http://www.opengis.net/gml" xmlns:ogc="http://www.opengis.net/ogc" version="1.0.0">
  <sld:NamedLayer>
    <sld:Name>Sea color background</sld:Name>
    <sld:UserStyle>
      <sld:Name>Background sample</sld:Name>
      <sld:Background>
        <sld:CssParameter name="fill">#F2EFE9</sld:CssParameter>
      </sld:Background>
      <sld:FeatureTypeStyle>
        <sld:Rule>
           ...
        </sld:Rule>  
    </sld:UserStyle>
  </sld:NamedLayer>
</sld:StyledLayerDescriptor>

Traditionally one can render multi-script labels by specifying a long list of family names in the “font-family”, e.g.:

<sld:Font>
  <sld:CssParameter name="font-family">Noto Sans Regular</sld:CssParameter>
  <sld:CssParameter name="font-family">Noto Sans Adlam Regular</sld:CssParameter>
  <sld:CssParameter name="font-family">Noto Sans Adlam Unjoined Regular</sld:CssParameter>
  <sld:CssParameter name="font-family">Noto Sans Armenian Regular</sld:CssParameter>
  <sld:CssParameter name="font-family">Noto Sans Balinese Regular</sld:CssParameter>
   ...
</sld:Font>

If the font names all share a common prefix, it’s now possible to be more concise and just use a function instead, specifying the common base name, letting GeoServer find all possible variants e.g.:

<sld:Font>
  <sld:CssParameter name="font-family">
    <ogc:Function name="fontAlternatives">
      <ogc:Literal>Noto Sans</ogc:Literal>
    </ogc:Function>
  </sld:CssParameter>
...
</sld:Font>

As a further labelling related feature, when performing conflict resolution the map renderer can now try to shrink the size of labels in search of a place to fit them. The new vendor option is called “fontShrinkSizeMin” and represents the minimum size to use. Here is an example, the two polygons share the same TextSymbolizer definition, in one the label size has been reduced to allow the label to fit:

Moving to line symbolizers, it’s now possible to drape a linear mark along a line. Before, it was just possible to repeat it along a line, but the output would not have looked continuous, especially at turns. Now, if you have a mark that starts and ends at the same height, it can literally be made continuous along the line, e.g. using this style:

       <LineSymbolizer>
<Stroke>
<GraphicStroke>
<Graphic>
<Mark>
<WellKnownName>wkt://LINESTRING (0 0, 0 -0.5, 0.5 -0.5, 0.5 0.5, 1 0.5, 1 0)</WellKnownName>
<Stroke>
<CssParameter name="stroke">0xFF0000
</CssParameter>
<CssParameter name="stroke-width">2</CssParameter>
<CssParameter name="stroke-linecap">round</CssParameter>
</Stroke>
</Mark>
<Size>20</Size>
</Graphic>
</GraphicStroke>
</Stroke>
<VendorOption name="markAlongLine">true</VendorOption>
</LineSymbolizer>

Results in the following (you cannot see at first it, but the size of the mark can be slightly altered to fit the segments length, and if it’s not enough, it gets cut and reconnected):

As a final note, there has been a number of small improvements to rendering performance, that will be especially visible when rendering a complex map, with many rules, features to be rendered, and labels (you know, like OpenStreetMap).

Enabled/advertised for layer groups

Up to now, the ability to enable/disable and advertise was limited to layers. No more, in GeoServer 2.17 you can now do the same with layer groups:

Custom WMS dimension for vector layers too

GeoServer supports standard WMS dimensions, TIME and ELEVATION, on both raster and vector datasets. However, user defined dimensions, also known as custom dimensions, were supported only by raster layers (typically, image mosaics). You can now configure them on vector layers as well:

WMS cascading improvements

The WMS cascading functionality has seen several improvements, including:

  • Possibility to choose the cascading format, expose the remote layer styles, while choosing which ones to advertise.
  • Possibility to configure min/max scale denominators for cascaded layers, as well as restrict cascading to the bounding box declared in the capabilities document.

GeoWebCache love

Significant improvements have been made to GeoWebCache and its integration with GeoServer, including:

  • Much better startup performance when integrated in GeoServer, the time to load the tiled layers configuration is a fraction of what it used to be.
  • Much faster tile layer listing in the GeoServer “tile layers” page
  • File system tile layout can be configured between classic (small folders), XYZ and TMS (for static cache generation)
  • Better control over failed tile seed operations. Seeding threads used to stop at the first failure, now error tolerance can be configured on the single thread and across the seed job:

JSON-LD community module

GeoServer 2.16 introduced a number of improvements in the WFS GeoJSON complex feature output. This release adds instead support for JSON-LD, as a community module.

Unlike the GeoJSON approach, based on automatic conventions, the JSON-LD module is driven by configuration, a JSON file giving the output format directives on how to encode the output based on complex input features.

The output format is available for both the WFS and new OGC Features API modules

OGC API community module updates

The OGC API community module delivers latest updates for OGC API services:

  • An up to date OGC Features API, updated to the last official release, with draft extensions to support filtering and multiple CRSs, along with tiling vector data
  • A OGC Tiles API, providing tiled collections in both rendered (maps, pngs, jpeg) and data (vector tiles) format, with draft extension to support on the fly filtering
  • A draft implementation of the OGC Styles API, supporting description and discovery of styles in multiple formats, and links from collections to their relevant styles, and back.
  • Two more experimental APIs, image API to manage image mosaic contents, and changeset API to figure out which areas of a tiled collection changed as a result of changes to the image mosaic backing them.

Development is still heavily ongoing, and specs are still evolving at a fast pace, but we invite you to try them out, enjoy their simplicity, and contribute to their evolution.

FlatGeoBuf community module

Are you using GML or GeoJSON to fetch data client side, and you’re not happy with the data transfer performance? You need to actually use the geometries client side, for editing, analysis and topological operations, and would like to avoid the clipping done in vector tiles?

Then you are the perfect candidate to try out our new FlatGeoBuf output format community module. FlatGeoBuf is “a performant binary encoding for geographic data based on flatbuffers that can hold a collection of Simple Features including circular interpolations as defined by SQL-MM Part 3.” While new, it’s making its way in several open source projects, it’s supported by the latest versions of GDAL/OGR and easy to embed in both OpenLayers and Leaflet. The format can also be streamed out, and rendered progressively client side, like in this OpenLayers demo.

And more!

There are several other new features and improvements, including:

  • Curved geometries are now supported in SQL Server too, in addition to the existing support for PostGIS and Oracle.
  • Support for workspace specific stored queries.
  • java.util.Math has been exposed in Freemarker templates.
  • It’s now possible to contribute an extension without signing an OSGeo CLA, as long as it’s self-contained and has a license compatible with GeoServer own.
  • The ncWMS compatibility community module has been improved, allowing to query a time list or a time range in GetTimeSeries, as well as ignoring NODATA pixels.
  • When renaming the layers, the pertinent authorization rules will be updated to match.
  • GeoTools has a new “ElasticGeo” community module, which allows to read data from ElasticSearch geo extensions. It still needs a nightly build packaging in Geoserver, volunteers welcomed.
  • GeoPackage can now be used with WMS and WFS time support.
  • Stand alone GeoWebCache has a new Swift blob store module, the integration with GeoServer would require custom packaging for it, volunteers welcomed.

Find out more in the release notes.

About GeoServer 2.17

Additional information on GeoServer 2.17 series:

GeoServer 2.15.5 Released

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

This is a maintenance release and is a recommended update for existing installations. This is the final scheduled 2.15 maintenance release and we recommend planning your upgrade to 2.16.

This release is made in conjunction with GeoTools 21.5 and GeoWebCache 1.15.5. Thanks to everyone who contributed to this release.

For more information see the GeoServer 2.15.5 release notes.

Improvements and Fixes

This release includes a number of improvements, including:

  • Improve ncWMS extension to support time list and time range.
  • Truncate of tiles fixed use of parameters.
  • Upgrade of XStream and Jackson libraries.

A number of fixes are also present:

  • [GEOS-8940] – Tile Layers page layer names bring to the “Publishing” tab by default
  • [GEOS-9375] – WCS 2.0 scalefactor=0 can cause excess memory usage
  • [GEOS-9428] – Authkey role service filters broken on 2.16+
  • [GEOS-9431] – Integrated GWC does not kick in when making request not qualified by workspace
  • [GEOS-9484] – ADMIN_ROLE is assigned by default if no role is returned for a user inside Web Service Body Response
  • Fix cascading WMTS use of credentials
  • ncWMS extension now respects no-data values.
  • Importer fixed to respect shapefile charset encoding.

About GeoServer 2.15 Series

Additional information on the 2.15 series:

GeoServer is now on Twitter

GeoServer now has an official twitter account, thanks to Simone for setting this up!

If you have a twitter account, please follow our @GeoServerO profile to stay in touch!

GeoServer 2.16.2 released

We are pleased to announce the release of GeoServer 2.16.2 with downloads (war|zip), documentation (html|pdf) and extensions.

This is a stable release recommended for production systems.

Improvements and Fixes

This release includes a number of improvements, including:

  • Support for vector custom dimensions (in addition to time and elevation)
  • Allow limiting the number of concurrent jobs in the importer extension
  • Default style descriptions wording improvement (as they are visible in capabilities documents)

Fixes included in this release:

  • The REST API fixes regarding datastore and feature type handling (see notes for details)
  • Fixed 100% CPU usage at idle on data directories with tens of thousands of layers
  • Don’t delay startup on an unresponsive cascaded WMS server
  • Make sure to truncate fully tile caches with parameters
  • Make GWC caching kick in also when using local workspaces along with non qualified layer names
  • And various others!

For more information check the 2.16.2 release notes.

Community Updates

For developers building from source, our community modules are a great place to collaborate on functionality and improvements.

About GeoServer 2.16

Features, presentations and reference material on the 2.16 series:

GeoServer 2.15.4 Released

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

This is a maintenance release and is a recommended update for existing installations. This is the last scheduled 2.15 maintenance release and we recommend planning your upgrade to 2.16.

This release is made in conjunction with GeoTools 21.3 and GeoWebCache 1.15.3. Thanks to everyone who contributed to this release.

For more information see the GeoServer 2.15.4 release notes.

Improvements and Fixes

This release includes a number of improvements, including:

  • Improve ncWMS extension to support time list and time range.
  • Truncate of tiles fixed use of parameters.
  • Upgrade of XStream and Jackson libraries.

A number of fixes are also present:

  • Fix cascading WMTS use of credentials
  • ncWMS extension now respects no-data values.
  • Importer fixed to respect shapefile charset encoding.

About GeoServer 2.15 Series

Additional information on the 2.15 series:

GeoServer 2.16.1 released

We are pleased to announce the release of GeoServer 2.16.1 with downloads (war|zip), documentation (html|pdf) and extensions.

This is a stable release recommended for production systems.

Note: Our builds detected a change in Oracle JDK 8u221 URL handling; this release was made with 8u202 as a result. Future releases will be made using OpenJDK.

Improvements and Fixes

This release includes a number of improvements, including:

  • The REST API now supports configuring the WMTS
  • New hideEmptyRules LEGEND_OPTION to hide rules not matching any features

Fixes included in this release:

  • SLDService generated raster classifiers are not overwriting the default style any longer
  • Monitoring extension fixed to respect GEOSERVER_AUDIT_PATH setting
  • Cascaded WMTS now makes use of provided credentials

For more information check the 2.16.1 release notes.

Security Updates

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

If you encounter a security vulnerability in GeoServer please respect our responsible disclosure policy.

Community Updates

For developers building from source, our community modules are a great place to collaborate on functionality and improvements.

  • ncWMS GetTimeSeries now supports time ranges with period and excludes nodata from results
  • hz-cluster improved synchronization events

About GeoServer 2.16

Features, presentations and reference material on the 2.16 series:

CITE Test Automation Request for Proposal

GeoServer Project Steering Committee is seeking a solution for automated CITE TEAM Engine tests for build.geoserver.org.

If you or your organization is interested in this work please respond to the geoserver-devel email list with your interest by the end of November. Applicants are welcome to email geoserver-devel list, or attend bi-weekly GeoServer meeting, with any questions or clarifications of requirements.

For details, including detailed requirements, see GSIP-176 fundraising, maintenance activity wiki page, and prior blog post.

Schedule Update: Please email geoserver-devel if you are interested in this activity by the end of November, we will evaluate proposal during GeoServer Meeting December 10th.

Clarrifications

There are three approaches discussed:

  • cite command line: our previous scripts made use of a the cite engine to run tests on the command line.
  • cite engine service: The new cite engine has a rest-api, so the testing script could use CURL commands to ask the engine to run the tests
  • cite engine docker: The cite engine is also distributed as a docker image, if that makes it easier to manage the rest-api approach 

Any of these approaches can be viable, or you may have additional ideas. The challenge (after our last experience) is setting up something that can be maintained.

Notes:

  • The WFS-T tests required a database to run, the tests created a couple of tables each time (since the transaction request modifies the content)

Thanks to sponsors

We would like to thank everyone who has supported this activity via sponsorship and donation. Special thanks OSGeo along with activity sponsors Gaia3D, and OSGeo:UK for help making this possible.

GeoServer 2.15.3 released

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

This is a maintenance release and is a recommended update for existing installations. This release is made in conjunction with GeoTools 21.3 and GeoWebCache 1.15.3. Thanks to everyone who contributed to this release.

For more information see the GeoServer 2.15.3 release notes.

Improvements and Fixes

This release includes a number of improvements, including:

  • Enhance mongodb schema generation
  • Allow setting Entity Expansion limit on WFS XML Readers
  • Promote authkey to extension (GSIP-174)
  • Make MongoDB App-Schema schema rebuilder endpoints only rebuild schemas present in mappings.
  • Promote status-monitoring module from Community to Extension
  • Upgrade Jetty to 9.4.18.v20190429

A number of fixes are also present:

  • WMS GetFeatureInfo formats text/html, text/plain, text/xml and application/vnd.ogc.gml (GML2) don’t handle time correctly
  • Wrong URL scheme in layer preview (when using HTTPS)
  • GetCapabilities on a single layer fails if a style is duplicated
  • Renaming a layer doesn’t update Data Security rules
  • SLD file renamed with REST PUT request when not needed
  • GeoTIFF sources configured with GeoServer 2.14.x might not work in 2.15.x
  • Style editor extension point not working
  • NullPointerException on WFS ComplexGeoJsonWriter Link check
  • Switching from System Status to Modules tab gives an error.
  • Nodata is not made transparent after channelSelect+contrastEnhancement on multibands dataset
  • WFS GeoJSONBuilder limits max nested level to 20

About GeoServer 2.15 Series

Additional information on the 2.15 series:

Java 11 comparability is the result of a successful code-sprint. Thanks to participating organizations (BoundlessGeoSolutionsGeoCatAstun TechnologyCCRi) and sprint sponsors (Gaia3Datolosgeo:ukAstun Technology).

GeoServer 2.16.0 released

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

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

Faster map rendering of complex styles

If you have very complex styles, with lots of rules and complex filtering conditions you’ll be pleased to hear that GeoServer 2.16.x can locate the right symbolizer much quicker than previous versions. This is useful, for example, in the GeoServer home page demo map, rendered from OSM data using a OSM Bright clone built with the CSS module.

The GeoSolutions offices in Massarosa (Viareggio), Italy, in the geoserver.org demo map

Dynamic densification on reprojection

GeoServer has always reprojected data “point by point”, this typically caused long lines represented by just two points to be turn into straight lines, instead of curves, as they were supposed to.

In GeoServer there is a new “advanced projection handling” option in WMS enabling on the fly densification of data, the rendering engine computes how much deformation the projection applies in the area being rendered, and densifies the long lines before reprojection, resulting in eye pleasing curves in output. See a “before and after” comparison here:

Reprojection, original point by point versus densified mode in 2.16.x

EPSG database updated to v 9.6

Thanks to the sponsorship of GeoScience Australia the EPSG database has been updated to version 9.6, including roughly a thousand more codes than the previous version available in GeoServer. The code has also been updated to ensure the NTv2 grid shift files between GDA94 and GDA2020 work properly.

Complex GeoJSON output changes

GeoServer WFS can already output GeoJSON out of complex features data sources (app-schema). However, the output can be less than pleasing at times, the following improvements have been made:

  • The property/element alternation typical of GML is preserved, causing deeply nested and ugly to look structures. Not everyone loves to write a “container.x.x” access to reach the x value, with 2.16.x the output skips one of the containers and exposes a direct “container.x” structure
  • XML attributes are now turned into plain JSON properties, and prefixed with a “@”
  • Feature and data types are not lost anymore in translations, preserved by a “@feaureType” and “@dataType” attributes
  • Full nested features are encoded as GeoJSON again, keeping their identifiers

Thanks to the sponsorship of the French geological survey – BRGM and the French environmental information systems research center – INSIDE, the 2.16.0 output now looks as follows:

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "id": "0001000001",
      "geometry": {
        "type": "Point",
        "coordinates": [51.0684, 1.4298]
      },
      "properties": {
        "@featureType": "Borehole",
        "identifier": {
          "value": "BSS000AAAA",
          "@codeSpace": "http://www.ietf.org/rfc/rfc2616"
        },
        "bholeHeadworks": [
          {
            "type": "Feature",
            "geometry": {
              "type": "Point",
              "coordinates": [51.0684, 1.4298]
            },
            "properties": {
              "@featureType": "BoreCollar",
              "collarElevation": {
                "value": -32,
                "@srsName": "http://www.opengis.net/def/crs/EPSG/0/5720",
                "@srsDimension": "1",
                "@uomLabels": "m"
              }
            }
          }
        ],

Status Monitoring module promoted to Core

The Status Monitoring module has been promoted to core, and is now included in the GeoServer status page by default!

This module adds a new tab to the Server Status page, with system statistics so that you can monitor the system which GeoServer is running on from the Web GUI.

../../_images/gui.png

Authentication key module graduated to extension

The “Authkey” module has been graduated to extension, allowing security unaware applications to access GeoServer. Reminder, in order to keep the system secure the keys should be managed as temporary session tokens by an external application (e.g. MapStore can do this).

PostGIS data store improvements

The PostGIS data store sees a few improvements, including:

  • TWKB encoding for geometries for all WMS/WMTS requests, reducing the amount of data travelling from the database to GeoServer
  • The JDBC driver used to transfer all data as ASCII, the code was modified to allow full binary transfer when prepared statements are enabled (driver limitation, binary can only be enabled in that case)
  • SSL encryption control, the driver defaults to have it on with a significant overhead, if the communication is in a trusted network the encryption can be disabled with benefit to performance
  • Improved encoding of “or-ed” filters, which now use the “in” operator where possible, increasing the likeliness that an eventual index o nthat column will be used
  • Native KNN nearest search when using the “nearest” filter function

OGC/GDAL stores updated to GDAL 2.x

The OGR datastore as well as the GDAL image readers have been updated and now work against GDAL 2.x official binaries, without requiring custom builds any longer.

The OGR datastore can open any vector data source and, in particular, it can use the native FileGBD library when using Windows. It’s also interesting to note that it can open Spatialite files, quite important now that the direct Spatialite store is gone.

Azure GWC blobstore

Tiles can now be stored in Azure blob containers, increasing GWC compatibility with cloud environments, after the already existing S3 support.

A warning though, Azure does not provide, unlike S3, a mass blob delete API, so on truncate GWC will have to go and remove tiles making a DELETE request for each (using parallel requests of course).

SLDService community module graduated to extension

The SLDService community module allowed to generated classified maps of vector data based on criterias such as equal interval, quantiles and unique values.

The same module has now graduated to extension, providing also data filtering based on standard deviation, equal area classification, and offering all the same services on raster data as well (with automatic sub-sampling when the source image is too large).

For example, creating a five classes quantile classification based on states persons over a custom color ramp can be achieved using the following:

curl -v -u admin:geoserver -XGET
  http://localhost:8080/geoserver/rest/sldservice/states/classify.xml?attribute=PERSONS&method=quantile&intervals=5&ramp=CUSTOM&startColor=0xf7fcb9&endColor=0x31a354&fullSLD=true

New Community Modules

  • WMTS styling module, which adds the ability to get/put a style on a per layer basis using restful resources exposed as ResourceURL
  • OGC API module, including implementations of the new OGC Web APIs for Features, Tiles and Styles (more to come in the upcoming months). Mind, these are cool but also prototypes based on specifications still in draft form, we have warned you, the API will likely have a few rounds of changes still before it stabilizes.
  • MapML community module. See this video for step by step installation instructions.

Other assorted improvements

There are many improvements to look at in the 2.16.0 release notes, as well as in the 2.16-RC release notes. Cherry picking a few, we hav:

  • Integrated GWC fails to seed layers if any data security is configured
  • Default Datastore Parameters panel does not allow https:// protocol values
  • Parameter Extractor plugin cannot mangle URL correctly if Monitor plugin is installed
  • Permit extensibility of Common Formats from Layer Preview page
  • Update name to id in OGC API Collection
  • Add support for configuring ACL in gwc-s3 community module
  • Enhance mongodb schema generation

About GeoServer 2.16

GeoServer 2.16 has been first released in September 2019.

Join Me in Funding an Important GeoServer Initiative


TLTR

GeoServer Project has been at the forefront of the standards-based geospatial web since 2001. Meanwhile, it’s been some years since GeoServer has been formally certified OGC-compliant. There is an opportunity to permanently improve how this is done by boosting a crucial component of the GeoServer software build infrastructure.

Fundraising progress
Fundraising progress

OSGeo has put forth an initiative and provided an initial budget towards regaining OGC certification status and making automatic certification a feature of the GeoServer software build process. The initiative and the implementation plan are outlined here. Once implemented, the GeoServer build server will continuously execute against OGC’s CITE TEAM Engine test suite, resulting in an ongoing certification status check with every release.

The Open Source Foundation has arranged to submit generated test results each year to reestablish formal certification. This will allow GeoServer to display the appropriate OGC logos on our website.

To help fund this initiative, please donate via PayPal or credit here. Please consider that your contribution will make a mark on every release and every copy of GeoServer which is downloaded thousands of times per week worldwide.


7 Reasons Why This Matters

  • Integrators and implementers will gain increased confidence that GeoServer-based products and solutions remain interoperable with other software in the OGC standards ecosystem
  • Added qualification for government procurements requiring proof of OGC certification
  • Quality assurance via early detection and remediation of variances impacting interoperability
  • Overall improvement of software reliability and decreased integration friction
  • Streamlining practical validation of emerging standards in the OGC
  • Free, standards-compliant software is indispensable in driving adoption, education, and innovation around geospatial data and standards-based system integration
  • Ensuring that GeoServer remains a stable, trusted, open-source component 


On a Personal Note

I’ve come to rely on GeoServer for a multitude of solutions and development projects. Being able to use this constantly evolving software afforded me a lot of self-sufficiency and creative freedom for the past 15 years, ever since GeoServer was a small software library. It doesn’t take a lot to appreciate that this has been made possible by the efforts of a small, committed, international community. While at OpenGeo and Boundless (recently acquired by Planet), I had a distinct honor and a pleasure to work closely with this community, making many lasting friendships along the way. 

Helping fund this initiative is an easy and meaningful way to lend tangible support to the project team that remains committed to advancing GeoServer. I’m delighted to know that my contribution will help fund the planning and development activities necessary to implement this feature.


How to contribute using PayPal or credit card:

Donate

Please join me and make your contribution! Also, please take a minute to Like, Share, retweet and reach others with this message. To become a corporate sponsor, please follow this link.

Thanks in advance you for your thoughtfulness and support.

Ilya Rosenfeld

Download GeoServer