GeoServer 2.28.0 release is now available with downloads (bin, war, windows), along with docs and extensions.

This is a stable release of GeoServer, recommended for production use. GeoServer 2.28.0 is made in conjunction with GeoTools 34.0, GeoWebCache 1.28.0, ImageIO-Ext 2.0.0, and ImageN 0.9.0.

Thanks to Jody Garnett (GeoCat) for making this release. Thanks to Daniel Calliess, Sören Kalesse and Gabriel Roldan for providing feedback and testing of the 2.28-M0 milestone release.

Security Considerations

This release addresses security vulnerabilities and is an important upgrade for production systems.

See project security policy for more information on how security vulnerabilities are managed.

Upgrade instructions

Please take note of the Upgrade Instructions, specifically:

• This release requires Java 17 LTS minimum, Java 11 is no longer supported.

  GeoServer is tested with Long Term Support releases: Java 17 LTS and Java 21 LTS. For more information see Java Considerations in the user manual.

• The global setting Unrestricted XML External Entity Resolution has been replaced with the ENTITY_RESOLUTION_UNRESTRICTED application property.

  This change primarily affects application schema users that have not yet adopted ENTITY_RESOLUTION_ALLOWLIST. See update instructions for details.

• Due to a user interface change, it is no longer necessary to generate a masterpw.info when upgrading an older data directory.

  If this file is present from an earlier upgrade, it is still considered a security warning and is noted on the welcome page.

Image Processing Engine updated

Updating the image processing engine used by GeoServer to be Java 17 compatible is one of the first major objectives of the GeoServer 3 crowdfunding activity. We are pleased to provide the upgrade from Java Advanced Imaging 1.1.3 to Eclipse ImageN 0.9.0 as part of the GeoServer 2.28.0 release.

Eclipse ImageN 0.9.0 is a stable release of two established codebases (Java Advanced Imaging and JAI-Ext) combined together into a single project. ImageN 1.0.0 will be released once the team has had an opportunity to increase the test coverage and update the user manual, over the course of the GeoServer 3.0 series.

Thanks to Jody (GeoCat), Andrea and Daniele (GeoSolutions) for this work and GeoServer 3 Crowdfunding for accomplishing this key objective for the future of GeoServer. We would also like to thank the Eclipse Foundation for working with Oracle to finally make this Sun Microsystems technology open source, alongside OpenJDK.

For more information see Eclipse ImageN and updated Wikipedia Entry for Java Advanced Imaging.

Legend: Symbology Encoding Functions

This release includes a long-awaited improvement for legend graphic generation - creating a legend graphic when the Symbology Encoding Recode, Interpolate and Categorize functions are used.

<Fill>
  <CssParameter name="fill">
    <ogc:Function name="Recode">
      <!-- Value to Transform -->
      <ogc:Function name="strTrim">
        <ogc:PropertyName>SUB_REGION</ogc:PropertyName>
      </ogc:Function>
      <!-- Map of input to output values -->
      <ogc:Literal>N Eng</ogc:Literal>   <ogc:Literal>#6495ED</ogc:Literal>
      <ogc:Literal>Mid Atl</ogc:Literal> <ogc:Literal>#B0C4DE</ogc:Literal>
      <ogc:Literal>S Atl</ogc:Literal>   <ogc:Literal>#00FFFF</oac:Literal>
      <ogc:Literal>E N Cen</ogc:Literal> <ogc:Literal>#9ACD32</ogc:Literal>
      <ogc:Literal>E S Cen</ogc:Literal> <ogc:Literal>#00FA9A</ogc:Literal>
      <ogc:Literal>W N Cen</ogc:Literal> <ogc:Literal>#FFF8DC</ogc:Literal>
      <ogc:Literal>W S Cen</ogc:Literal> <ogc:Literal>#F5DEB3</ogc:Literal>
      <ogc:Literal>Mtn</ogc:Literal>     <ogc:Literal>#F4A460</ogc:Literal>
      <ogc:Literal>Pacific</ogc:Literal> <ogc:Literal>#87CEEB</ogc:Literal>
    </ogc:Function>
  </CssParameter>
</Fill>

Thanks to Andrea (GeoSolutions) for this improvement.

• GEOS-8002 LegendGraphic does not display when using transformation functions (recode, interpolate, categorize)

OAuth2 OpenID Connect community modules

A new community module sec-oidc is now available based directly on Spring Security Core. This new community module is intended as a direct replacement for the existing sec-oauth2-geonode, sec-oauth2-github, sec-oauth2-google, and sec-oauth2-openid-connectplugins which have reached end of life.

For more information see OAUTH2 OIDC in the user manual. Extensive information (and notes) are provided for working with Google, GitHub, Microsoft Azure, and Keycloak. We are really pleased that the new OIDC community plugin is available alongside the existing OAuth2 implementations for comparison and testing.

The initial work was performed by Andreas Watermeyer (ITS Digital Solutions), and completed for GeoServer 2.28.0 by David Blasby (GeoCat), Ian Turton, and Alessio Fabiani (GeoSolutions). Thanks to the GeoServer 3 Crowdfunding sponsors for supporting this important development.

Developer Updates

A number of significant changes affect developers working on the GeoServer codebase:

• The change to Java 17 LTS minimum brings new language features to the codebase

• Java 17 build improvements

• Maven bill-of-materials import to manage both GeoTools library modules and syncrhonize third-party dependencies with the GeoTools project.

Thanks to Gabriel Roldan (Camptocamp) for working on these activities on behalf of GeoServer 3 sponsors.

Release notes

New Feature:

• GEOS-11949 Support MS Excel download from WPS-download
• GEOS-11800 Implement GeoServer WPS SpatioTemporalZonalStatistics process
• GEOS-11911 Application property ROOT_LOGIN_ENABLED

Improvement:

• GEOS-11934 Image processing tile cache: better logging and deeper cleanups
• GEOS-11788 Apply feedback from CSP testing
• GEOS-11833 Unnecessary antiCache parameter on some GUI images
• GEOS-11837 MapML Support for LayerGroups
• GEOS-11867 Improve entity resolution
• GEOS-11892 Column mentioning user that performed last modification for layers and stores list UI
• GEOS-11938 Add support for property selection in OGC API Features

Bug:

• GEOS-11823 Quality Degradation in Scanned Map Rendering (GeoServer 2.25.3 onward)
• GEOS-11944 GetLegendGraphic Fails When Using RasterSymbolizer With Interval ColorMap And ENV variables
• GEOS-11946 DirectRasterRenderer may fail on creating AlphaBand from ROI using Lookup
• GEOS-11957 Cannot logout due remember-me cookie with oidc
• GEOS-10728 Cannot download GeoPackage if the source data contains UUID types
• GEOS-11274 Cannot get a JSON legend with an external reference to a non published directory
• GEOS-11620 Smart Data Loader plugin for GeoServer 2.26 produces a Mapping file data source definition and tries to establish a connection pool, but fails
• GEOS-11688 After restart unable to load External Style SLD when requesting multiple tiles
• GEOS-11708 STAC breadcrumbs rendering as plain text
• GEOS-11751 Symbolizer URL in GetLegendGraphic JSON Request is Broken
• GEOS-11808 Attribute names containing characters the XML Encoder can’t handle are accepted for input, causing errors
• GEOS-11832 count=0 service exception for some formats
• GEOS-11857 Random NPE In LocalWorkspaceCallback
• GEOS-11860 MapML does not match raster rendering geometry simplification behavior
• GEOS-11862 Layer Preview and Tile Layers page dropdown links broken after updating table
• GEOS-11863 Use GetTile or GetMap requests in for cached raster coverages where appropriate
• GEOS-11865 MapDownloadProcess washes out 1 band gray images when transparency is on
• GEOS-11866 Prevent requests setting variables that should only be set by GeoServer
• GEOS-11879 Xalan causes a java.lang.NoClassDefFoundError
• GEOS-11902 More compact, easier to maintain conformance configuration UI
• GEOS-11910 JMS Cluster settings Section is not showing properly
• GEOS-11917 INSPIRE configuration does not get properly saved when OGC API module is included
• GEOS-11931 GeoServer binary package fails to start after Jetty 9.x to 10.0.25 upgrade

Task:

• GEOS-11848 Migrate use of JAITools to JAI-Ext
• GEOS-11956 Fix build server WfsCompatibilityTest failure (when testing against “local” GeoServer on port 8080)
• GEOS-11813 Create REST API For Security Providers
• GEOS-11814 Create a REST API for Filter Chains
• GEOS-11815 Create authentication filter REST API
• GEOS-11831 OseoDispatcherCallback improvements
• GEOS-11852 Remove master password info page
• GEOS-11853 Clarify keystore vs master vs root password
• GEOS-11854 Generation of security/masterpw.info no longer required
• GEOS-11855 global settings cog warning in release data directory
• GEOS-11869 Replace entity resolution setting with application property
• GEOS-11881 Update postgis-jdbc
• GEOS-11882 Cleanup postgis-jdbc dependencies
• GEOS-11932 Upgrade Oracle JDBC driver to Java 17

For the complete list see 2.28.0 release notes.

Community Updates

Community module development:

• GEOS-11951 Add PMTiles DataStore community module for reading Protomaps vector tiles
• GEOS-11816 Features templating OGC API fetch by ID fails
• GEOS-11819 Make smart data loader skip unsupported column types
• GEOS-11822 OGC API procesess basic implementation
• GEOS-11829 Features templating ability to override schema
• GEOS-11839 New Community Module for WPS Download in NetCDF output format for spatiotemporal coverages
• GEOS-11870 Singlestore(MemSql) datastore community module
• GEOS-11885 Smart Data Loader does not support postgresql UUID data type
• GEOS-11887 Features Templating does not returns content type and charset header on OGC-API

Community modules are shared as source code to encourage collaboration. If a topic being explored is of interest to you, please contact the module developer to offer assistance.

Developer updates

• GEOS-11845 GSIP-232 Upgrade GeoServer and GeoWebCache Build to Java 17
• GEOS-11943 remove PDF generation of manual from build process
• GEOS-11952 GeoServer 2.28.0 Release cleanup
• GEOS-11836 Upgrade ErrorProne to 2.31.0
• GEOS-11843 Use Spring framework BOM to manage Spring and Spring Security dependencies
• GEOS-11851 Remove unnecessary javac lint suppressions
• GEOS-11858 Update to PMD 7.14 and enable unnecessary suppression rule

About GeoServer 2.28 Series

Additional information on GeoServer 2.28 series:

• GeoServer 2.28 User Manual

Release notes: ( 2.28.0 | 2.28-M0 )

The GeoServer team is making great progress on our 2025 roadmap plans, with CITE Certification Achieved, and GeoServer 3 underway, the project is going well.

Thanks to GeoServer 2025 sponsors:

CITE Certification

We are really happy to the see the CITE Certified banner restored to the main GeoServer website for calendar year 2025. Andrea continues to work on certifying the new OGCAPI services:

• OGCAPI - Tiles: Passing tests on Team Engine 2.0 Engine

• OGCAPI - Process: Making progress on certification

A reminder that if CITE Certification is valuable to you GeoServer will need to pay OGC each year - which requires sponsorship. We are certified for calendar year 2025 thanks to the prior sponsorship. We find that many organizations assume GeoServer is certified, this is not be the case without your financial support.

Thanks to Gaia3D and OSGeo:UK for sponsoring 2025 CITE Certification.

Security

We continue to be in need of resources, both developer resources and funding, to address the expectations placed on open source projects. If you are in a position to support this activity, please contact us at geoserver-security@lists.osgeo.org .

GeoServer 3

The big news is the completion of Milestone 1 : Preparation with the release of GeoServer 2.28.0, allowing the Milestone 2 : Migration activities to proceed as scheduled.

For more information on GeoServer 3 development, review the project plan and GeoServer 3 Crowdfunding FAQ.

GeoServer 3 Milestone 1 Completed

The release of GeoServer 2.28.0 represents the end of Milestone 1: Preparation:

• Upgrade from Java Advanced Imaging 1.1.3 to Eclipse ImageN 0.9.0.

• Java 17 LTS minimum, ending support for Java 11.

• Lots of build improvements, with the highlight being a bill-of-materials “geotools” pom.xml file to manage versions across GeoTools, GeoWebCache, and GeoServer.

• A new community module, gs-sec-oidc-plugin, replacing gs-oauth2 plugins.

GeoServer 3 Milestone 2 Underway

GeoServer 3 Milestone 2: Migration is underway:

• Friday 17 October: Code Freeze

  We will be freezing the main branches of the related projects on Friday 17 Oct 2025, in preparation for the Milestone 2 code sprint. Please follow the announcement on Discourse.

• Monday 20 October: Code Sprint

  With the branches frozen, the GeoServer 3 team is assembling for an intensive code sprint to start the migration to Spring Framework 3.

Crowdfunding

Thanks to sponsors for supporting GeoServer 3 crowdfunding, we hope you are pleased with the progress thus far and look forward to sharing GeoServer 3 with you in the months ahead.

GeoServer 3 is supported by the following organisation:

Individual donations: Abhijit Gujar, Hennessy Becerra, Ivana Ivanova, John Bryant, Jason Horning, Peter Smythe, Sajjadul Islam, Sebastiano Meier, Stefan Overkamp.

GeoSpatial Techno is a startup focused on geospatial information that is providing e-learning courses to enhance the knowledge of geospatial information users, students, and other startups. The main approach of this startup is providing quality, valid specialized training in the field of geospatial information.

( YouTube | LinkedIn | Facebook | X )

Master GeoServer WPS - Key Input Categories You Need to Know

The WPS Request Builder is a demo page used to try out the Web Processing Service (WPS) used to execute geospatial processes for transformation, summary and analysis. This session provides a detailed overview of the various inputs and categories in the WPS Request Builder.

If you want to access the complete tutorial, click on the link.

Introduction

In GeoServer, the WPS request builder enables users to perform various geospatial processing operations with different functionality to analyze and manipulate geospatial data. Each category provides a set of specific operations tailored to a range of geospatial tasks.

Note: Be sure to download the WPS extension that corresponds exactly to your GeoServer version—mismatched versions will result in errors.

Some categories available in the WPS request builder are JTS, Geo, GS, and Vec.

• JTS: The JTS process uses the Java Topology Suite library to perform various geometry manipulation and analysis operations such as Buffer, Intersection, Union, Simplify, etc.
• Geo: This process includes geospatial operations that may involve coordinate transformations and spatial analysis. Some common functions include Reproject, Centroid, Convex Hull, etc.
• GS: The GS or ‘GeoServer Specific’ process uses the GeoTools library and provides a set of geospatial processing operations specifically designed for use in the GeoServer environment. Some common functions include Feature Count, Centroid, BufferFeatureCollection, etc.
• Vec: This process contains operations specifically designed for working with vector data, such as merge, dissolve, aggregate, etc.

The built-in GS (for GeoServer) and Vec (for Vector) processes have direct access to the layers provided by GeoServer.

The JTS (from JTS Topology Suite library) and Geo (from GeoTools library) processes are provided by external libraries. If you are interested in making your own process there is a Process Tutorial for Java Developers.

First, we will introduce the inputs of the JTS and Geo processes, and then we will delve into the GS and Vec processes.

JTS and Geo processes

The JTS and Geo processes refer to different sets of processing functions that are specifically dedicated to handling geometries and performing geospatial operations.

From the Demo menu, navigate to the WPS Request Builder. This section contains several types of processes, which you can view in the Choose Process section. They accept three inputs for execution: Text, Reference, and Subprocess.

TEXT

In Text mode, you can enter the data geometry information in one of the standard formats supported by WPS. These standard formats are:

• text/xml; subtype=gml
• application/wkt
• application/gml
• application/json

The main differences between these MIME types are:

• text/xml; subtype=gml is more suitable for human readability and debugging, while application/gml is intended for machine-to-machine interactions, APIs, and programmatic consumption.
• Use text/xml; subtype=gml for scenarios that require easy readability or manual processing, and application/gml for cases where data is consumed directly by applications without being rendered as text.

Overall, the choice between the two should depend on the intended use case: for human interaction, use text/xml; subtype=gml; for application-oriented needs, choose application/gml.

application/wkt

The application/wkt is a MIME type that represents data encoded in the Well-Known Text (WKT) format. WKT is a text-based format for representing and exchanging geospatial data, particularly geometric shapes and objects. It supports various geometric types, including: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon.

The application/wkt and application/ewkt formats in GeoServer WPS represent geometry; WKT defines shapes without CRS, suitable for basic 2D/3D geometry. EWKT adds an SRID, embedding CRS info in the geometry string for essential context.

Here is an example of the application/wkt format:

- POINT(48.23 11.56)
- LINESTRING(45.67 9.12, 50.45 12.34, 55.89 10.67)
- POLYGON((45.67 9.12, 50.45 12.34, 55.89 10.67, 45.67 9.12))
- MULTIPOINT((45.67 9.12), (50.45 12.34), (55.89 10.67))
- MULTILINESTRING((45.67 9.12, 50.45 12.34), (55.89 10.67, 45.67 9.12))
- MULTIPOLYGON(((45.67 9.12, 50.45 12.34, 55.89 10.67, 45.67 9.12)), ((60.12 8.34, 62.45 11.67, 65.89 10.01, 60.12 8.34)))

application/json

The application/json is a MIME type used to represent data encoded in GeoJSON format for encoding geographic data structures. It is based on the JSON format and allows the representation of simple geographic features along with their associated non-spatial attributes stored in the Properties object.

This MIME type is commonly used in Web mapping applications, GIS, and various other geospatial applications because it provides a standardized way to represent and exchange geographic data.

Here is an example of the application/json document:

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [-122.41, 37.78]
      },
      "properties": {
        "name": "San Francisco",
        "population": 883306,
        "elevation": 16
      }
    },
    {
      "type": "Feature",
      "geometry": {
        "type": "Polygon",
        "coordinates": [[
          [-122.4194, 37.7749],
          [-122.4244, 37.7749],
          [-122.4244, 37.7799],
          [-122.4194, 37.7799],
          [-122.4194, 37.7749]
        ]]
      },
      "properties": {
        "name": "San Francisco City Hall",
        "type": "government"
      }
    }
  ]
}  

REFERENCE

The Reference mode for specifying input geometry involves linking to an external resource containing the necessary geometry data for processing. This mode is beneficial when the geometry data is stored in a separate file or service, allowing you to provide a reference instead of including the data directly in the WPS request.

To use this option, you can choose between the GET or POST method. The choice depends on the size and nature of the referenced data, as well as any security considerations.

• GET: This method includes the reference to an external resource, such as a URL pointing to a file or service endpoint, directly in the request URL. It’s ideal for retrieving small to moderate-sized data, as the data is transmitted via URL query parameters.
• POST: This method includes the reference to the external resource in the body of the HTTP request, rather than in the URL. The POST method preferred for larger datasets or confidential data, because it’s more secure and allow larger amounts of data to be transferred without URL length limitations.

SUBPROCESS

Using the Subprocess mode for input geometry in a WPS request, allows for seamless chaining of multiple processes. It enables you to reference data from another process without writing intermediate results to disk, significantly enhancing workflow efficiency.

This approach is particularly beneficial when managing large datasets or executing multiple processing tasks rapidly, as it eliminates unnecessary handling steps and facilitates direct data transfer between interconnected processes.

Select Subprocess from the Process Inputs dropdown menu in the WPS Request Builder section. Then, click the Define/Edit link to open a new page where you can choose an additional process for chaining.

OUTPUT

The result output refers to a spatial data layer, typically represented in a vector format such as GML, GeoJSON, or WKT. This output can be processed further, visualized, or utilized in various spatial analyses. When generating the WPS result geometry, you can choose from several standard spatial data formats, each described in detail.

These formats are:

• text/xml; subtype=gml
• application/wkt
• application/gml
• application/json

Selecting the appropriate format allows you to tailor the output to suit your specific use case or workflow.

GS and Vec processes

These processes are specifically designed to integrate seamlessly with GeoServer layers, thereby enhancing the utilization of geospatial data. The GS process includes various GeoServer-specific operations for interacting with and managing GeoServer resources, while the Vec process specializes in vector data processing, offering tools for analyzing and transforming vector geometries.

They accept four inputs for execution: Text, Reference, Subprocess, and Vector layers.

TEXT

In this mode, you can use various standard formats supported by WPS. These formats are:

• text/xml;subtype=wfs-collection
• application/wfs-collection
• application/zip
• text/csv
• application/json
• application/vnd.google-earth.kml+xml

text/xml;subtype=wfs-collection

Using this format allows you to submit a collection of geometries directly from a WFS request to a WPS process in GeoServer. When you use a WFS-Collection as input, you reference a set of geometries that the WPS operation can manipulate directly.

Here’s an example of how to use a WFS collection 1.1 in a WPS request:

<wfs:FeatureCollection xmlns:wfs="http://www.opengis.net/wfs" xmlns:feature="http://www.openplans.org/topp" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml" xmlns:ogc="http://www.opengis.net/ogc" xmlns:ows="http://www.opengis.net/ows" xmlns:xlink="http://www.w3.org/1999/xlink">
  <gml:boundedBy>
    <gml:Envelope srsDimension="2" srsName="http://www.opengis.net/gml/srs/epsg.xml#4326">
      <gml:lowerCorner>147.291 -42.851002</gml:lowerCorner>
      <gml:upperCorner>147.291 -42.851002</gml:upperCorner>
    </gml:Envelope>
  </gml:boundedBy>
  <gml:featureMember>
    <feature:tasmania_cities gml:id="tasmania_cities.1">
      <gml:boundedBy>
        <gml:Envelope srsDimension="2" srsName="http://www.opengis.net/gml/srs/epsg.xml#4326">
          <gml:lowerCorner>147.291 -42.851002</gml:lowerCorner>
          <gml:upperCorner>147.291 -42.851002</gml:upperCorner>
        </gml:Envelope>
      </gml:boundedBy>
      <feature:the_geom>
        <gml:Point srsDimension="2" srsName="http://www.opengis.net/gml/srs/epsg.xml#4326">
          <gml:pos>147.291 -42.851002</gml:pos>
        </gml:Point>
      </feature:the_geom>
      <feature:CITY_NAME>Hobart</feature:CITY_NAME>
      <feature:ADMIN_NAME>Tasmania</feature:ADMIN_NAME>
      <feature:CNTRY_NAME>Australia</feature:CNTRY_NAME>
      <feature:STATUS>Provincial capital</feature:STATUS>
      <feature:POP_CLASS>100,000 to 250,000</feature:POP_CLASS>
    </feature:tasmania_cities>
  </gml:featureMember>
</wfs:FeatureCollection>

application/vnd.google-earth.kml+xml

It is a MIME type used for representing geospatial data in the Keyhole Markup Language (KML) format which primarily associated with Google Earth and various mapping applications. KML enables the encoding of diverse geographic features, such as points, lines, and polygons, along with their associated attributes.

Here’s an example of how to use an application/vnd.google-earth.kml+xml mime type in a WPS request:

  <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  <kml xmlns="http://www.opengis.net/kml/2.2" xmlns:ns2="http://www.google.com/kml/ext/2.2" xmlns:ns3="http://www.w3.org/2005/Atom" xmlns:ns4="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0">
      <Document>
          <Schema name="poi" id="poi">
              <SimpleField type="string" name="NAME"/>
          </Schema>
          <Folder>
              <name>poi</name>
              <Placemark id="poi.1">
                  <ExtendedData>
                      <SchemaData schemaUrl="#poi">
                          <SimpleData name="NAME">museam</SimpleData>
                      </SchemaData>
                  </ExtendedData>
                  <Point>
                      <coordinates>-74.01046109936333,40.707587626256554</coordinates>
                  </Point>
              </Placemark>
              <Placemark id="poi.2">
                  <ExtendedData>
                      <SchemaData schemaUrl="#poi">
                          <SimpleData name="NAME">stock</SimpleData>
                      </SchemaData>
                  </ExtendedData>
                  <Point>
                      <coordinates>-74.0108375113659,40.70754683896324</coordinates>
                  </Point>
              </Placemark>
              <Placemark id="poi.3">
                  <ExtendedData>
                      <SchemaData schemaUrl="#poi">
                          <SimpleData name="NAME">art</SimpleData>
                      </SchemaData>
                  </ExtendedData>
                  <Point>
                      <coordinates>-74.01053023879955,40.70938711687079</coordinates>
                  </Point>
              </Placemark>            
          </Folder>
      </Document>
  </kml>

Vector Layer

This mode in GeoServer allows users to utilize predefined geographical data for advanced spatial analyses, including overlay analysis, buffering, and spatial querying. This access to well-organized data, such as points, lines, and polygons, significantly enhances analytical capabilities compared to relying solely on JTS or Geo processes.

By integrating vector layers into the WPS request builder, users can perform sophisticated geospatial analyses, enabling deeper insights from their datasets and making GeoServer a preferred choice for complex spatial processing tasks.

OUTPUT

The result output typically provides a spatial data layer in various vector formats, including GML, GeoJSON, CSV, and Shapefile. This output can be further processed, visualized, or used in other spatial analyses, making it highly versatile for different applications.

When generating geometry, you can choose the result in a variety of standard data formats, including:

• text/xml;subtype=wfs-collection
• application/wfs-collection
• application/zip
• text/csv
• application/json
• application/vnd.google-earth.kml+xml

This flexibility allows you to choose the most appropriate format for your specific use case or workflow, ensuring compatibility with your analysis tools and visualization platforms. By offering these multiple output formats, GeoServer effectively supports a wide range of geoprocessing needs, facilitating seamless integration and analysis of spatial data.

In this session, we discussed the types of different categories and various inputs in the WPS Request Builder. To access the full tutorial, click on this link.

Reference:

• Web Processing Service (WPS) (User Manual)
• Process Cookbook (User Manual)

GeoServer 2.28-M0 release is now available with downloads (bin, war, windows), along with docs, extensions, and data directory.

This is a milestone release previewing the GeoServer 2.28.x series to let everyone try out our new ImageN raster processing engine.

This release is made as part of the GeoServer 3 “Milestone 1” activity. It is made in conjunction with ImageN 0.4.0, ImageIO-Ext 2.0.0-M0, GeoTools 34-M0, mapfish-print-v2 2.4-M0, and GeoWebCache 1.28-M0.

Thanks to Jody Garnett (GeoCat) and Ian Turton for making this release.

Milestone Release

Milestone releases are a chance to share what we have been working on, and ask you to try it with your own data:

• A new Eclipse ImageN (pronounced “imagine”) processing engine.

  This project combining Java Advanced Imaging (donated by Oracle) and JAI-Ext (donated by GeoSolutions) into a single image processing engine optmized for a modern Java environment.

• Speaking of modern Java Environment GeoServer now requires Java 17 minimum. Java 11 is no longer supported. GeoServer is testing with Long Term Support releases: Java 17 LTS and Java 21 LTS.

• Lots of build improvements with the highlight being a bill-of-materials “geotools” pom.xml file to share managing versions across GeoTools, GeoWebCache and GeoServer

• A new community module gs-sec-oidc-plugin under active development.

  This plugin will be taking over the responsibilities of gs-oauth2 plugins as they are being retired for GeoServer 3.

This is a milestone release so we welcome your feedback, we already know of a couple of things:

• javadocs download is empty

  This is due to changing to JDK 17, and a large number of javadoc warrnings we now need to resolve.

• GeoServer 2.28-M0 artifacts were not published to repo.osgeo.org

About GeoServer 2.28

Release notes: ( 2.28-M0 )

GeoServer 2.26.4 release is now available with downloads (bin, war, windows), along with docs and extensions.

This is a maintenance (now archive) release of GeoServer, providing existing installations with minor updates and bug fixes. GeoServer 2.26.4 is made in conjunction with GeoTools 32.4, and GeoWebCache 1.26.4. Please note that this is the final scheduled release in the 2.26.x series - it is time to upgrade to a supported version.

Thanks to Peter Smythe (AfriGIS) for making this release, and to Jody for testing it.

Security Considerations

This release addresses security vulnerabilities and is considered an important update for existing installations.

The use of the CVE system allows the GeoServer team to reach a wider audience than blog posts. See project security policy for more information on how security vulnerabilities are managed.

Upgrade instructions

Please take note of the Upgrade Instructions, specifically:

• The global setting Unrestricted XML External Entity Resolution has been replaced with the ENTITY_RESOLUTION_UNRESTRICTED application property.

  This change primarily affects application schema users that have not yet adopted ENTITY_RESOLUTION_ALLOWLIST. See update instructions for details.

• Due to a user interface change, it is no longer necessary to generate a masterpw.info when upgrading an older data directory.

  If this file is present from an earlier upgrade, it is still considered a security warning and is noted on the welcome page.

Release notes

New Feature:

• GEOS-11805 Option to disable the management of stored queries
• GEOS-11911 Application property ROOT_LOGIN_ENABLED

Improvement:

• GEOS-11867 Improve entity resolution
• GEOS-11877 Improve CoverageView composition to support noData fill on missing bands/coverages
• GEOS-11892 Column mentioning user that performed last modification for layers and stores list UI

Bug:

• GEOS-10728 Cannot download GeoPackage if the source data contains UUID types
• GEOS-11820 WCS spatial sub-setting does not work when native CRS != declared CRS
• GEOS-11832 count=0 service exception for some formats
• GEOS-11866 Prevent requests setting variables that should only be set by GeoServer
• GEOS-11896 WPS map download flips east/west coordinates
• GEOS-11900 CRS:XY syntax builds isolated CRSs that do not leverage the EPSG database transformation library

Task:

• GEOS-11831 OseoDispatcherCallback improvements
• GEOS-11852 Remove master password info page
• GEOS-11853 Clarify keystore vs master vs root password
• GEOS-11854 Generation of security/masterpw.info no longer required
• GEOS-11869 Replace entity resolution setting with application property

For the complete list see 2.26.4 release notes.

Community Updates

Community module development:

• GEOS-11829 Features templating ability to override schema
• GEOS-11830 Smart data loader create store page fails when environment variables are in use
• GEOS-11839 New Community Module for WPS Download in NetCDF output format for spatiotemporal coverages
• GEOS-11847 Next link is missing in “Search” OGC API - Features proposal implementation when startIndex is not set
• GEOS-11871 Allow native execution of group by in DGGS store, when grouping on geometries
• GEOS-11876 WPS Vertical Longitudinal Profile: Support automatic distance computation
• GEOS-11878 WFS HITS request returns the whole data records on a GML feature templated layer
• GEOS-11880 OGC API Maps is not showing up in GeoServer home page

Community modules are shared as source code to encourage collaboration. If a topic being explored is of interest to you, please contact the module developer to offer assistance.

About GeoServer 2.26 Series

Additional information on GeoServer 2.26 series:

• GeoServer 2.26 User Manual
• GeoServer 2024 Q3 Developer Update
• Raster Attribute Table extension
• Community module graduation, amending generality rule
• Individual contributor clarification
• Migrate geoserver-users from SourceForge to discourse

Release notes: ( 2.26.4 | 2.26.3 | 2.26.2 | 2.26.1 | 2.26.0 | 2.26-M0 )