<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://geoserver.org/feed.xml" rel="self" type="application/atom+xml" /><link href="https://geoserver.org/" rel="alternate" type="text/html" /><updated>2026-05-15T04:39:10+00:00</updated><id>https://geoserver.org/feed.xml</id><title type="html">GeoServer</title><subtitle>GeoServer latest posts</subtitle><author><name>GeoServer community</name></author><entry><title type="html">GeoServer 3.0-RC, a crowdfunded success story</title><link href="https://geoserver.org/behind%20the%20scenes/2026/04/21/geoserver-3-rc-crowdfunding-success.html" rel="alternate" type="text/html" title="GeoServer 3.0-RC, a crowdfunded success story" /><published>2026-04-21T00:00:00+00:00</published><updated>2026-04-21T00:00:00+00:00</updated><id>https://geoserver.org/behind%20the%20scenes/2026/04/21/geoserver-3-rc-crowdfunding-success</id><content type="html" xml:base="https://geoserver.org/behind%20the%20scenes/2026/04/21/geoserver-3-rc-crowdfunding-success.html"><![CDATA[<p>GeoServer <a href="/release/3.0-RC/">3.0-RC</a> is now available, and with it we can celebrate something bigger than a release candidate.</p>

<p>This milestone is the concrete outcome of a successful community crowdfunding campaign.</p>

<p>When we launched the <a href="/sponsor/gs3-crowdfunding">GeoServer 3 crowdfunding initiative</a> in September 2024, the goal was ambitious. GeoServer needed more than incremental maintenance. It needed a full platform modernization, including a new generation user experience, a stronger security foundation, a modern Java stack, improved raster processing, and the engineering effort required to carry those changes across the broader GeoServer ecosystem.</p>

<p>That work is now visible in GeoServer 3.0-RC.</p>

<h2 id="from-campaign-to-release-candidate">From campaign to release candidate</h2>

<p>The GeoServer 3 crowdfunding effort set a total target of <strong>550,000 €</strong>. Camptocamp, GeoCat, and GeoSolutions each committed <strong>50,000 €</strong>, establishing a community funding goal of <strong>400,000 €</strong>. In May 2025, the campaign <a href="/behind%20the%20scenes/2025/05/13/gs3-crowdfunding-surpassed.html">surpassed that goal</a>.</p>

<p>That achievement mattered because GeoServer 3 was never a small upgrade. It required coordinated investment in core platform work that is essential for users, but often difficult to fund through routine maintenance alone:</p>

<ul>
  <li>migration to a modern Spring and Jakarta based platform</li>
  <li>alignment with JDK 17 and current deployment environments</li>
  <li>replacement of aging raster processing components with ImageN</li>
  <li>stronger security and vulnerability management</li>
  <li>documentation updates and broad compatibility testing</li>
  <li>user interface and usability improvements across the administration experience</li>
</ul>

<p>The consortium of Camptocamp, GeoCat, and GeoSolutions provided coordination, delivery capacity, and co-funding. Sponsors, community members, and individual donors made it possible to move from planning into implementation.</p>

<h2 id="what-geoserver-30-rc-shows">What GeoServer 3.0-RC shows</h2>

<p>With GeoServer 3.0-RC, the results of that investment are now ready for public testing.</p>

<p>This release candidate introduces a modernized platform with:</p>

<ul>
  <li>a new context-driven user experience</li>
  <li>a responsive administration interface</li>
  <li>a new full-screen layer preview</li>
  <li>updated documentation in Markdown</li>
  <li>support for modern servlet containers including Tomcat 11 and Jetty 12.1</li>
  <li>a straightforward upgrade path from GeoServer 2.28.x, with no changes to the GeoServer data directory</li>
</ul>

<p>GeoServer 3.0-RC is also released together with <strong>GeoTools 35-RC</strong> and <strong>GeoWebCache 2.0-RC</strong>, making this an important ecosystem milestone, not just a version bump.</p>

<p><a href="/img/posts/3.0/welcome-global.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/welcome-global.png" alt="GeoServer 3" class="screensnap" style="max-width: 95%" />
</a></p>

<h2 id="why-this-matters-for-open-source-sustainability">Why this matters for open source sustainability</h2>

<p>Crowdfunding is often discussed in theory as a way to support open source. GeoServer 3 offers a practical example of what that support can achieve.</p>

<p>This campaign did not fund a narrow feature request. It funded the kind of foundational work that keeps a critical open source project healthy: technical modernization, security upgrades, ecosystem testing, documentation improvements, and long-term maintainability.</p>

<p>That is exactly the kind of work communities depend on, and exactly the kind of work that is hardest to finance unless users and organizations step forward together.</p>

<p>GeoServer 3.0-RC proves that this model can work.</p>

<h2 id="help-us-finish-strong">Help us finish strong</h2>

<p>The arrival of GeoServer 3.0-RC is also a call for community testing.</p>

<p>We encourage everyone to try the release candidate in their own environment, especially for:</p>

<ul>
  <li>upgrade workflows from GeoServer 2.28.x</li>
  <li>the new user interface and administration workflows</li>
  <li>deployments on Tomcat 11 and Jetty 12</li>
  <li>raster-heavy and tiling-heavy workloads</li>
  <li>extension compatibility and operational edge cases</li>
</ul>

<p>You can download GeoServer 3.0-RC from the <a href="/release/3.0-RC/">release page</a>, review the <a href="https://docs.geoserver.org/latest/en/user/installation/upgrade3/">upgrade instructions</a>, or quickly test the Docker image:</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>docker run <span class="nt">-p</span> 8080:8080 docker.osgeo.org/geoserver:3.0-RC
</code></pre></div></div>

<p>Please share your feedback on the <a href="https://discourse.osgeo.org/t/geoserver-3-0-rc-release-candidate/153541">GeoServer 3.0-RC discourse thread</a>.</p>

<p><a href="/img/posts/3.0/ol-preview.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/ol-preview.png" alt="New full screen layer preview" class="screensnap" />
</a></p>

<h2 id="thank-you">Thank you</h2>

<p>GeoServer 3.0-RC is an important technical milestone, but it is also a community milestone.</p>

<p>Thank you to the organisations, individual donors, developers, testers, and sponsors who helped make this happen. And thank you to the consortium teams at Camptocamp, GeoCat, and GeoSolutions for carrying the work from campaign to release candidate.</p>

<p>GeoServer 3.0-RC is here because the community decided this work was worth funding.</p>

<p>That is worth celebrating.</p>

<p>
  GeoServer 3 is supported by the following organisations:
</p>
<!-- alphabetical -->
<p><a href="https://www.afrigis.co.za/">
  <img src="/support/img/AfriGIS-full-logo.png" title="AfriGIS" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://camptocamp.com/">
  <img src="/support/img/camptocamp-logo.png" title="Camptocamp" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.dlr.de/de">
  <img src="/sponsor/img/dlr-logo.svg" title="DLR" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.dorsetcouncil.gov.uk">
  <img src="/sponsor/img/dorset-council-logo.png" title="Dorset Council" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.telekom.com">
  <img src="/sponsor/img/telekom-logo.svg" title="Deutsche Telekom" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://frachtwerk.de">
  <img src="/sponsor/img/frachwerk-logo.svg" title="Frachtwerk GmbH" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.geocat.com/">
  <img src="/support/img/core-geocat.png" title="GeoCat BV" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.geocrafter.eu">
  <img src="/sponsor/img/geocrafter-geospatial-studio-logo.png" title="Geocrafter - Geospatial Studio" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.comune.genova.it">
  <img src="/sponsor/img/genova-logo.png" title="Comune di Genova" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.gon.de/en">
  <img src="/sponsor/img/gon-logo.png" title="g.on" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.geosolutionsgroup.com/">
  <img src="/support/img/core-geosolutions.png" title="GeoSolutions SRL" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://geosos.net">
  <img src="/sponsor/img/geosos.png" title="geosos" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.getmap.eu/">
  <img src="/sponsor/img/get-logo.png" title="Geospatial Enabling Technologies (GET)" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://incloud.com">
  <img src="/sponsor/img/incloud-logo.png" title="Incloud Limited" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.linkedin.com/in/lucvanlinden/">
  <img src="/sponsor/img/hl-consulting.png" title="HL Consulting" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://ign.fr/">
  <img src="/sponsor/img/ign-logo.png" title="Institut national de l'information géographique et forestière (IGN)" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.its-digital.de/">
  <img src="/sponsor/img/its-digital.svg" title="ITS Digital" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://jdev.fr">
  <img src="/sponsor/img/jdev-logo.svg" title="JDev" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.kfw.de/">
  <img src="/sponsor/img/kfw-logo.svg" title="Kreditanstalt für Wiederaufbau" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://mammothgeospatial.com">
  <img src="/sponsor/img/mammoth-logo.svg" title="Mammoth Geospatial" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://oceanservice.noaa.gov/">
  <img src="/sponsor/img/nos-logo.png" title="NOA National Ocean Service" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.plangis.de">
  <img src="/sponsor/img/plangis-logo.svg" title="Plangis" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.gov.ie/en/organisation/office-of-public-works/">
  <img src="/sponsor/img/opw-logo.png" title="Office of Public Works" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.osgeo.kr">
  <img src="/sponsor/img/osgeo-kr-logo.svg" title="OSGeo:Korea" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://uk.osgeo.org">
  <img src="/sponsor/img/osgeo-uk-logo.png" title="OSGeo:UK" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.quarticle.ro">
  <img src="/sponsor/img/quarticle-logo.svg" title="Quarticle Research Srl" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://hurrevac.com/">
  <img src="/sponsor/img/sea-island-software-logo.png" title="Sea Island Software" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.tailormap.com/">
  <img src="/sponsor/img/tailormap-logo.svg" title="Tailormap" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.terrestris.de/">
  <img src="/sponsor/img/terrestris-logo.png" title="Terrestris" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.ubigu.fi/en/home//">
  <img src="/sponsor/img/ubigu-logo.png" title="Ubigu" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.value-marktdaten.de/en/portfolio/market-database/real-estate-price-maps/">
  <img src="/sponsor/img/value-logo.png" title="Value AG" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.vgregion.se/">
  <img src="/sponsor/img/vastra-gotaland-logo.svg" title="Region Västra Götaland" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://waldexpert.waldportal-bw.de/">
  <img src="/sponsor/img/waldexpert-logo.svg" title="WaldExpert" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<br /></p>
<p>
  Individual donations: Abhijit Gujar, Hennessy Becerra, Ivana Ivanova, John Bryant, Jason Horning, Jose Macchi, Peter Smythe, Sajjadul Islam, Sebastiano Meier, Stefan Overkamp.
</p>]]></content><author><name>Emmanuel Belo</name></author><category term="Behind The Scenes" /><category term="GeoServer 3" /><category term="Crowdfunding" /><category term="Community" /><category term="Release Candidate" /><summary type="html"><![CDATA[GeoServer 3.0-RC is now available, and with it we can celebrate something bigger than a release candidate.]]></summary></entry><entry><title type="html">GeoServer 3.0-RC Release</title><link href="https://geoserver.org/announcements/2026/04/20/geoserver-3-0-RC-released.html" rel="alternate" type="text/html" title="GeoServer 3.0-RC Release" /><published>2026-04-20T00:00:00+00:00</published><updated>2026-04-20T00:00:00+00:00</updated><id>https://geoserver.org/announcements/2026/04/20/geoserver-3-0-RC-released</id><content type="html" xml:base="https://geoserver.org/announcements/2026/04/20/geoserver-3-0-RC-released.html"><![CDATA[<p>GeoServer <a href="/release/3.0-RC/">3.0-RC</a> is now available, with downloads for
( <a href="https://sourceforge.net/projects/geoserver/files/GeoServer/3.0-RC/geoserver-3.0-RC-bin.zip/download">bin</a>, 
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/3.0-RC/geoserver-3.0-RC-war.zip/download">war</a>
<!-- ,[windows](https://sourceforge.net/projects/geoserver/files/GeoServer/3.0-RC/GeoServer-3.0-RC-winsetup.exe/download)-->), along with 
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/3.0-RC/geoserver-3.0-RC-htmldoc.zip/download">docs</a> and
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/3.0-RC/extensions/">extensions</a>.
We are working with OSGeo for the windows installer download, and will update this post when it is available. Windows users are asked to <a href="https://docs.geoserver.org/main/en/user/installation/win_binary/">test out the bin download</a> while we wait.
Release available as <a href="https://github.com/geoserver/docker">docker image</a> <code class="language-plaintext highlighter-rouge">docker.osgeo.org/geoserver:3.0-RC</code> .</p>

<p>This is a release candidate intended for public review and feedback.
GeoServer 3.0-RC is made in conjunction with GeoTools 35-RC, and GeoWebCache 2.0-RC.</p>

<p>Thanks to Jody Garnett (GeoCat), Andrea Aime (GeoSolutions), and Peter Smythe (AfriGIS) for making this release.</p>

<h3 id="please-test-geoserver-30-rc">Please Test GeoServer 3.0-RC</h3>

<p>We encourage everyone to try GeoServer 3.0-RC in their own environment, especially for <a href="https://docs.geoserver.org/latest/en/user/installation/upgrade3/">upgrade workflows</a>, the new user interface, and deployment on Tomcat 11 and Jetty 12. Real-world testing is the best way to catch regressions and compatibility issues before the final 3.0 release.</p>

<p>You may also quickly test the <a href="https://github.com/geoserver/docker">docker image</a> using:</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>docker run <span class="nt">-p</span> 8080:8080 docker.osgeo.org/geoserver:3.0-RC
</code></pre></div></div>

<p>Please share your success, feedback, questions, and any issues you encounter on the <strong>user forum</strong> <a href="https://discourse.osgeo.org/t/geoserver-3-0-rc-release-candidate/153541">GeoServer 3.0-RC Release Candidate discourse thread</a>.</p>

<h3 id="geoserver-cloud-300-rc">GeoServer Cloud 3.0.0-RC</h3>

<p><a href="https://geoserver.org/geoserver-cloud/">GeoServer Cloud</a> 3.0.0-RC has also been released alongside this candidate. Cloud-native deployments can now try out GeoServer 3 in microservices form, see the <a href="https://github.com/geoserver/geoserver-cloud/releases/tag/v3.0.0-RC">v3.0.0-RC release notes</a> for details.</p>

<p>To get started, follow the <a href="https://geoserver.org/geoserver-cloud/deploy/">Kubernetes quickstart</a> and share your feedback so we can iron out any remaining issues before the final 3.0.0 release.</p>

<h2 id="welcome-to-geoserver-3">Welcome to GeoServer 3</h2>

<p>We are overjoyed to share this update with our community, this is the final stretch of a long road, a year of development, and a lot of planning and support to make it all happen.</p>

<p>There will be more technical details in the final release announcement - but for now we wish to say thank you.</p>

<p><a href="/img/posts/3.0/welcome-global.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/welcome-global.png" alt="GeoServer 3" class="screensnap" style="max-width: 95%" />
</a></p>

<h3 id="straightforward-upgrade">Straightforward upgrade</h3>

<p>We have taken great pains to make the upgrade process seamless from GeoServer 2.28.x.</p>

<ol>
  <li>
    <p>Important: We have made no changes to the GeoServer Data Directory.</p>

    <p>Download and try GeoServer 3.0-RC today!</p>
  </li>
  <li>
    <p>A few modules have migrated from core to extensions:</p>

    <ul>
      <li><a href="https://docs.geoserver.org/latest/en/user/services/wcs/install/">WCS 1.0</a> and <a href="https://docs.geoserver.org/latest/en/user/services/wcs/install/">WCS 1.1</a></li>
      <li><a href="https://docs.geoserver.org/latest/en/user/data/raster/arcgrid/#arcgrid_install">World Image</a> and <a href="https://docs.geoserver.org/latest/en/user/data/raster/arcgrid/#arcgrid_install">ArcGRID</a> raster data sources.</li>
    </ul>

    <p>The pure Java <code class="language-plaintext highlighter-rouge">H2</code> database is no longer provided.</p>
  </li>
  <li>
    <p>The <a href="https://docs.geoserver.org/latest/en/user/configuration/logging/#logging_location">log file location</a> setting
is now managed using the <code class="language-plaintext highlighter-rouge">GEOSERVER_LOG_LOCATION</code> application property.</p>
  </li>
  <li>
    <p>The NetCDF index support has been simplified and is now self-contained. With this improvement, NetCDF
no longer needs a database or local <code class="language-plaintext highlighter-rouge">.idx</code> files to operate.</p>

    <p>Instructions are provided for how to clean up these now unused files.</p>
  </li>
  <li>
    <p>The new <a href="https://docs.geoserver.org/main/en/user/community/oidc/">OIDC</a> plugin is available to take over the responsibilities of the previously available <code class="language-plaintext highlighter-rouge">Keycloak</code> and <code class="language-plaintext highlighter-rouge">OAuth2</code> plugins.</p>
  </li>
</ol>

<p>Please see the <a href="https://docs.geoserver.org/latest/en/user/installation/upgrade3/">upgrade instructions</a> for details.</p>

<h3 id="new-context-driven-user-experience">New Context-Driven User Experience</h3>

<p>GeoServer 3 features a new “context-driven” user experience, which we really hope you enjoy.</p>

<ul>
  <li>
    <p><strong>Search</strong>: Using the left hand side search field to find information. Autocomplete results are shown as you type, and results are listed in a tree which can be navigated below.</p>

    <p><a href="/img/posts/3.0/context-search.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/context-search.png" alt="User Interface Search" class="screensnap" />
</a></p>
  </li>
  <li>
    <p><strong>Context</strong>: Clicking on a search item establishes the context which is shown as breadcrumbs along the top of the page.
A drop-down context menu provides quick access to actions that can be performed.</p>

    <p><a href="/img/posts/3.0/context-menu.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/context-menu.png" alt="User Interface Context Menu" class="screensnap" />
</a></p>
  </li>
  <li>
    <p><strong>Page</strong>: Page content adjusts to the current context. The welcome page adjusts to showing the layer tile and description, along with preview links, sample data downloads, metadata and data links configured.</p>

    <p><a href="/img/posts/3.0/welcome-layer.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/welcome-layer.png" alt="User Interface Welcome Layer Page" class="screensnap" />
</a></p>
  </li>
  <li>
    <p><strong>Menu</strong>: The menu bar at the top of the page provides login on the right hand side, and access to the familiar GeoServer top-level menus. Many of these pages now adjust their content to reflect the current context.</p>

    <p><a href="/img/posts/3.0/menus.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/menus.png" alt="User Interface Top Level Menus" class="screensnap" />
</a></p>
  </li>
  <li>
    <p><strong>Feedback</strong>: Admins are provided additional context-menu commands, and per-layer feedback and shortcuts,
making the application easier and faster to use.</p>

    <p><a href="/img/posts/3.0/welcome-layer-feedback.png " target="_blank" rel="noopener">
  <img src="/img/posts/3.0/welcome-layer-feedback.png " alt="User Interface Feedback" class="screensnap" style="max-width: 50%" />
</a></p>
  </li>
</ul>

<p>For more information see the <a href="https://docs.geoserver.org/main/en/user/webadmin/">user guide</a>.</p>

<p>Thanks to Stefano Bovio (GeoSolutions), Jody Garnett (GeoCat), and others for this major improvement.</p>

<h3 id="new-user-interface-responsive-design-theme">New User Interface Responsive Design Theme</h3>

<p>GeoServer now provides a responsive-design theme:</p>

<ul>
  <li>
    <p><strong>Navigation</strong>: Navigation is reduced to a hamburger menu when using a narrow width display.</p>

    <p><a href="/img/posts/3.0/menus-responsive.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/menus-responsive.png" alt="Responsive Theme: Menus" class="screensnap" style="max-width: 50%" />
</a></p>
  </li>
  <li>
    <p><strong>Forms</strong>: Forms have adopted a two-column layout adapting to page width.</p>

    <p><a href="/img/posts/3.0/form-two-column.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/form-two-column.png" alt="Responsive Theme: Form two-column layerout" class="screensnap" style="max-width: 50%" />
</a></p>
  </li>
</ul>

<p>Details coming soon to the developers guide!</p>

<p>Thanks to Stefano Bovio (GeoSolutions) for leading this frequently requested improvement, the entire GeoServer 3 team for implementing and checking, and testers at AfriGIS and GeoCat for verifying and updating screenshots.</p>

<h3 id="new-layer-preview">New Layer Preview</h3>

<p>A new full-screen layer preview is provided using the latest OpenLayers library.</p>

<p><a href="/img/posts/3.0/ol-preview.png" target="_blank" rel="noopener">
  <img src="/img/posts/3.0/ol-preview.png" alt="New full screen layer preview" class="screensnap" />
</a></p>

<p>Thanks to Stefano Bovio (GeoSolutions) for the welcome improvement.</p>

<h3 id="updated-environment">Updated Environment</h3>

<p>GeoServer 3 is overjoyed to support Tomcat 11.0.x and Jetty 12.1 application servers after completing our transition to Spring Framework 7 and Jakarta EE Servlet API 6.1.</p>

<p>We have been extensively testing GeoServer 3 with Java 17 and Java 21, maintaining the same Java runtime baseline as GeoServer 2.28.x. Java 25 is subject to automated testing, but we are going to hold off recommending it until the user community has had an opportunity to try it out and report back.</p>

<p>If you are wondering about the compatibility between the Java web stack and GeoServer, here is a table showing the various supported options:</p>

<table class="compat-table">
  <thead>
    <tr>
      <th>GeoServer</th>
      <th>Java</th>
      <th>Tomcat</th>
      <th>Jetty</th>
      <th>Java EE</th>
      <th>Jakarta EE</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>GeoServer 3.0</td>
      <td>17, 21</td>
      <td>Tomcat 11.0.x</td>
      <td>Jetty 12.1</td>
      <td> </td>
      <td>Servlet API 6.1</td>
    </tr>
    <tr>
      <td>Not supported</td>
      <td> </td>
      <td>Tomcat 10.1.x</td>
      <td>Jetty 12.0</td>
      <td> </td>
      <td>Servlet API 6.0</td>
    </tr>
    <tr>
      <td>Not supported</td>
      <td> </td>
      <td>Tomcat 10.0.x</td>
      <td>Jetty 11.0</td>
      <td> </td>
      <td>Servlet API 5.0</td>
    </tr>
    <tr>
      <td>GeoServer 2.28.x</td>
      <td>17, 21</td>
      <td>Tomcat 9.x</td>
      <td> </td>
      <td>Servlet API 4</td>
      <td> </td>
    </tr>
    <tr>
      <td>GeoServer 2.28.x</td>
      <td>17, 21</td>
      <td> </td>
      <td>Jetty 9.4</td>
      <td>Servlet API 3.1</td>
      <td> </td>
    </tr>
  </tbody>
</table>

<p>For more information see <a href="https://docs.geoserver.org/latest/en/user/production/container/">container considerations</a>.</p>

<p>Thanks to the entire GeoServer 3 team and <a href="/sponsor/gs3-crowdfunding">crowdfunding campaign</a> for this major accomplishment, representing the completion of Milestone 3.</p>

<h3 id="new-oauth2-openid-connect-security-integration">New OAuth2 OpenID Connect Security Integration</h3>

<p>The transition to Spring Security 7 was one of the big tasks accomplished for GeoServer 3. This work includes the creation of a new <code class="language-plaintext highlighter-rouge">OIDC</code> plugin. The new plugin has taken over the responsibilities of previously available <code class="language-plaintext highlighter-rouge">Keycloak</code> and <code class="language-plaintext highlighter-rouge">OAuth2</code> plugins.</p>

<ul>
  <li>If you previously used <code class="language-plaintext highlighter-rouge">Keycloak</code>, there are setup instructions for <a href="https://docs.geoserver.org/main/en/user/community/oidc/oauth2/keycloak/">configuring with Keycloak</a>.</li>
  <li>If you previously used an <code class="language-plaintext highlighter-rouge">OAuth2</code> integration, you can find individual setup instructions for <a href="https://docs.geoserver.org/main/en/user/community/oidc/oauth2/google/">Google</a>, <a href="https://docs.geoserver.org/main/en/user/community/oidc/oauth2/azure/">Azure</a>, and <a href="https://docs.geoserver.org/main/en/user/community/oidc/oauth2/azure/">GitHub</a>.</li>
</ul>

<p>We are asking specifically for public testing during 3.0-RC timeframe allowing this module to be included as an extension for 3.0.0 release.</p>

<p>Thanks to Alessio Fabiani and others for key improvement. We are very much looking forward to having <a href="https://docs.geoserver.org/main/en/user/community/oidc/">OAuth2 OpenID Connect</a> support included in GeoServer.</p>

<h3 id="new-documentation">New Documentation</h3>

<p>The long-awaited transition to Markdown documentation has finally arrived. Welcome to our new <a href="https://docs.geoserver.org/latest/en/user/">User Manual</a>.  The older GeoServer 2.x documentation is available at <a href="https://docs-archive.geoserver.org/">Docs Archive</a> or via the version switcher.  Please help out by fixing any remaining <a href="https://docs.geoserver.org/latest/en/docguide/quickfix/">small issues</a> or log an issue for Peter to address.</p>

<p><a href="https://docs.geoserver.org/main/en/user/">
    <img src="/img/posts/3.0/user-manual.png" alt="The new user manual" class="screensnap" />
  </a></p>

<p>Thanks to Peter Smythe (AfriGIS) and Jody Garnett (GeoCat) for working on this activity which ended up being an incredible amount of work.</p>

<h3 id="thanks-to-the-geoserver-3-sponsors">Thanks to the GeoServer 3 Sponsors</h3>

<p>GeoServer 3 would not exist without the organizations and individuals who supported the <a href="/sponsor/gs3-crowdfunding">GeoServer 3 crowdfunding campaign</a>. Their sponsorship made this work possible.</p>

<p>
  GeoServer 3 is supported by the following organisations:
</p>
<!-- alphabetical -->
<p><a href="https://www.afrigis.co.za/">
  <img src="/support/img/AfriGIS-full-logo.png" title="AfriGIS" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://camptocamp.com/">
  <img src="/support/img/camptocamp-logo.png" title="Camptocamp" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.dlr.de/de">
  <img src="/sponsor/img/dlr-logo.svg" title="DLR" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.dorsetcouncil.gov.uk">
  <img src="/sponsor/img/dorset-council-logo.png" title="Dorset Council" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.telekom.com">
  <img src="/sponsor/img/telekom-logo.svg" title="Deutsche Telekom" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://frachtwerk.de">
  <img src="/sponsor/img/frachwerk-logo.svg" title="Frachtwerk GmbH" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.geocat.com/">
  <img src="/support/img/core-geocat.png" title="GeoCat BV" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.geocrafter.eu">
  <img src="/sponsor/img/geocrafter-geospatial-studio-logo.png" title="Geocrafter - Geospatial Studio" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.comune.genova.it">
  <img src="/sponsor/img/genova-logo.png" title="Comune di Genova" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.gon.de/en">
  <img src="/sponsor/img/gon-logo.png" title="g.on" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.geosolutionsgroup.com/">
  <img src="/support/img/core-geosolutions.png" title="GeoSolutions SRL" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://geosos.net">
  <img src="/sponsor/img/geosos.png" title="geosos" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.getmap.eu/">
  <img src="/sponsor/img/get-logo.png" title="Geospatial Enabling Technologies (GET)" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://incloud.com">
  <img src="/sponsor/img/incloud-logo.png" title="Incloud Limited" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.linkedin.com/in/lucvanlinden/">
  <img src="/sponsor/img/hl-consulting.png" title="HL Consulting" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://ign.fr/">
  <img src="/sponsor/img/ign-logo.png" title="Institut national de l'information géographique et forestière (IGN)" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.its-digital.de/">
  <img src="/sponsor/img/its-digital.svg" title="ITS Digital" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://jdev.fr">
  <img src="/sponsor/img/jdev-logo.svg" title="JDev" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.kfw.de/">
  <img src="/sponsor/img/kfw-logo.svg" title="Kreditanstalt für Wiederaufbau" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://mammothgeospatial.com">
  <img src="/sponsor/img/mammoth-logo.svg" title="Mammoth Geospatial" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://oceanservice.noaa.gov/">
  <img src="/sponsor/img/nos-logo.png" title="NOA National Ocean Service" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.plangis.de">
  <img src="/sponsor/img/plangis-logo.svg" title="Plangis" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.gov.ie/en/organisation/office-of-public-works/">
  <img src="/sponsor/img/opw-logo.png" title="Office of Public Works" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.osgeo.kr">
  <img src="/sponsor/img/osgeo-kr-logo.svg" title="OSGeo:Korea" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://uk.osgeo.org">
  <img src="/sponsor/img/osgeo-uk-logo.png" title="OSGeo:UK" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.quarticle.ro">
  <img src="/sponsor/img/quarticle-logo.svg" title="Quarticle Research Srl" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://hurrevac.com/">
  <img src="/sponsor/img/sea-island-software-logo.png" title="Sea Island Software" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.tailormap.com/">
  <img src="/sponsor/img/tailormap-logo.svg" title="Tailormap" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.terrestris.de/">
  <img src="/sponsor/img/terrestris-logo.png" title="Terrestris" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.ubigu.fi/en/home//">
  <img src="/sponsor/img/ubigu-logo.png" title="Ubigu" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.value-marktdaten.de/en/portfolio/market-database/real-estate-price-maps/">
  <img src="/sponsor/img/value-logo.png" title="Value AG" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.vgregion.se/">
  <img src="/sponsor/img/vastra-gotaland-logo.svg" title="Region Västra Götaland" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://waldexpert.waldportal-bw.de/">
  <img src="/sponsor/img/waldexpert-logo.svg" title="WaldExpert" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<br /></p>
<p>
  Individual donations: Abhijit Gujar, Hennessy Becerra, Ivana Ivanova, John Bryant, Jason Horning, Jose Macchi, Peter Smythe, Sajjadul Islam, Sebastiano Meier, Stefan Overkamp.
</p>

<h2 id="release-notes">Release notes</h2>

<p>New features:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12063">GEOS-12063</a> [GSIP-238] GeoServer 3 UI / UX Refresh</li>
</ul>

<p>Improvements:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11886">GEOS-11886</a> Sort entries in all .properties files alphabetically</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12015">GEOS-12015</a> Switch tests using H2 to GeoPackage</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12023">GEOS-12023</a> Improve developer logging during catalog resources loading and WMS capabilities requests</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12024">GEOS-12024</a> Add Git branch name in GEOSERVER_NODE_OPTS</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12072">GEOS-12072</a> Remove deprecated REST endpoint on the DataStoreFileController</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12077">GEOS-12077</a> Remove H2/DB based index and binary index from CoverageMultidim/NetCDF stores</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12081">GEOS-12081</a> Update MapML.js (<mapml-viewer> custom element suite) to v0.17.0</mapml-viewer></li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12082">GEOS-12082</a> CoverageStore - quick fail for incorrect files</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12083">GEOS-12083</a> Skip brute force login delays when checking for default administrator password</li>
</ul>

<p>Bugs:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-10509">GEOS-10509</a> WFS Request fails when XML POST body is larger than 8kB</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11903">GEOS-11903</a> WPS does not respect raw response output selection when there are multiple outputs</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11916">GEOS-11916</a> Data directory migration performed on built-in default security configuration</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11926">GEOS-11926</a> ogcapi plugin makes WFS advertising an outputFormat which is actually unavailable</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11930">GEOS-11930</a> OGC-API extension breaks security REST API</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11942">GEOS-11942</a> ImagePPIO does not run any longer</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11964">GEOS-11964</a> Metadata Bulk Operations: wicket error</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11965">GEOS-11965</a> KMZ export incorrectly references remote icon URLs instead of embedding them in the KMZ archive</li>
  <li>
    <table>
      <tbody>
        <tr>
          <td><a href="https://osgeo-org.atlassian.net/browse/GEOS-11981">GEOS-11981</a> POST /security/authproviders</td>
          <td>400: Unsupported className</td>
        </tr>
      </tbody>
    </table>
  </li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11988">GEOS-11988</a> Fix bug: preserve metaTilingThreads=0 in saneConfig()</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11999">GEOS-11999</a> The version of Jetty (12) no longer supports web.xml CORS configuration</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12065">GEOS-12065</a> WMS Layer REST PUT always returns 500 due to Collections.emptySet() in getRemoteStyleInfos()</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12073">GEOS-12073</a> Remove log location configuration from Admin Console and REST API</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12084">GEOS-12084</a> TemplateController REST endpoints accept non-existent workspace, store, and resource names</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12085">GEOS-12085</a> LocalSettingsController does not validate workspace existence</li>
</ul>

<p>Tasks:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11987">GEOS-11987</a> ImageN 0.9.1 migration requires renaming of registryFile.jai to registryFile.imagen</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12004">GEOS-12004</a> Make WMS independent of WFS</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12005">GEOS-12005</a> Remove GeoServer H2 extension</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12006">GEOS-12006</a> GWC, removal of leftover H2 references</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12011">GEOS-12011</a> Move KML module to extension</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12016">GEOS-12016</a> Move WCS 1.1 module to extension</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12017">GEOS-12017</a> Move WCS 1.0 to extension</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12018">GEOS-12018</a> Switch GeoServer tests away from H2</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12019">GEOS-12019</a> Turn arcgrid and worldimage formats into plugins</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12025">GEOS-12025</a> Split WMS 1.1 and 1.3</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12040">GEOS-12040</a> Updating BouncyCatle libraries to LTS 2.73.10</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12041">GEOS-12041</a> Update Spring LDAP to 4.0.1</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12071">GEOS-12071</a> Remove the WPS remote module</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12064">GEOS-12064</a> CSS: add documentation for localized @title and @abstract metadata</li>
</ul>

<p>Sub-tasks:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12066">GEOS-12066</a> Present keywords as a table</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12067">GEOS-12067</a> Add Full Screen OpenLayers 10.8.0 layer preview</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12086">GEOS-12086</a> Keyboard navigation for file browser</li>
</ul>

<p>For the complete list see <a href="https://github.com/geoserver/geoserver/releases/tag/3.0-RC">3.0-RC</a> release notes.</p>

<h2 id="community-updates">Community Updates</h2>

<p>Community module development:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11904">GEOS-11904</a> OGC API Processes: add support for envelope input/output</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11905">GEOS-11905</a> OGC API processes status response lacks jobid and links to self</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11906">GEOS-11906</a> OGC API Processes: use correct error code for access to results when execution is not complete</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11907">GEOS-11907</a> OGC API Processes: support multiple raw responses</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11908">GEOS-11908</a> OGC API Processes page should be pageable</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11909">GEOS-11909</a> Add support for OGC API Echo process</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11915">GEOS-11915</a> OGC API Processes: improve support for binary input and output</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11972">GEOS-11972</a> GSIP 233 - Community Pending Release Profile</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11980">GEOS-11980</a> Add support for uploading a single parquet file to GeoServer via REST</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11983">GEOS-11983</a> GSR /query fails with HTTP 500 when where parameter is empty</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12000">GEOS-12000</a> Ignore DescribeFeatureType requests without typeName in Features Templating schemas override</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12002">GEOS-12002</a> hz-cluster: homepage pop-up fails</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12007">GEOS-12007</a> Add AWS credential chain authentication UI and documentation for GeoParquet</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12013">GEOS-12013</a> Support vector datasets ingestion in VectorMosaic via REST</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12044">GEOS-12044</a> STAC search endpoint should report invalid collection names as invalid parameters instead of internal errors</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12061">GEOS-12061</a> New Community Module for PNG-WIND output format for wind datasets</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12062">GEOS-12062</a> Add DuckDB datastore community extension (gs-duckdb)</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12069">GEOS-12069</a> Align the hazelcast version in hz-cluster to the rest of GeoServer</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12074">GEOS-12074</a> Remove activeMQ-broker community module</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12089">GEOS-12089</a> GWC sqlite community module breaks legend preview in style page</li>
</ul>

<p>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.</p>

<h1 id="about-geoserver-30x-series">About GeoServer 3.0.x Series</h1>

<p>Additional information on the GeoServer 3.0.x series:</p>

<ul>
  <li><a href="https://docs.geoserver.org/3.0.x/en/user/">GeoServer 3.0.x User Manual</a></li>
</ul>

<p>Release notes:
( <a href="https://github.com/geoserver/geoserver/releases/tag/3.0-RC">3.0-RC</a>
)</p>]]></content><author><name>Jody Garnett</name></author><category term="Announcements" /><category term="Release" /><category term="Release Candidate" /><summary type="html"><![CDATA[GeoServer 3.0-RC is now available, with downloads for ( bin, war ), along with docs and extensions. We are working with OSGeo for the windows installer download, and will update this post when it is available. Windows users are asked to test out the bin download while we wait. Release available as docker image docker.osgeo.org/geoserver:3.0-RC .]]></summary></entry><entry><title type="html">GeoServer 2.28.3 Release</title><link href="https://geoserver.org/announcements/2026/03/20/geoserver-2-28-3-released.html" rel="alternate" type="text/html" title="GeoServer 2.28.3 Release" /><published>2026-03-20T00:00:00+00:00</published><updated>2026-03-20T00:00:00+00:00</updated><id>https://geoserver.org/announcements/2026/03/20/geoserver-2-28-3-released</id><content type="html" xml:base="https://geoserver.org/announcements/2026/03/20/geoserver-2-28-3-released.html"><![CDATA[<p>GeoServer <a href="/release/2.28.3/">2.28.3</a> release is now available
with downloads
(<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.3/geoserver-2.28.3-bin.zip/download">bin</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.3/geoserver-2.28.3-war.zip/download">war</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.3/GeoServer-2.28.3-winsetup.exe/download">windows</a>), along with 
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.3/geoserver-2.28.3-htmldoc.zip/download">docs</a> and
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.3/extensions/">extensions</a>.</p>

<p>This is a maintenance release of GeoServer providing existing installations with minor updates and bug fixes.
GeoServer 2.28.3 is made in conjunction with GeoTools 34.3, and GeoWebCache 1.28.3.</p>

<p>Thanks to Andrea Aime (GeoSolutions) for making this release.</p>

<h2 id="release-notes">Release notes</h2>

<p>Improvement:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11886">GEOS-11886</a> Sort entries in all .properties files alphabetically</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12033">GEOS-12033</a> Allow to configure custom CRS authorities and transformations</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12037">GEOS-12037</a> Support Metatiling on MapBox Vectortiles</li>
</ul>

<p>Bug:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11964">GEOS-11964</a> Metadata Bulk Operations: wicket error</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12038">GEOS-12038</a> ModificationProxy.replaceCatalogInfo() precludes converting Filters to native query language</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12047">GEOS-12047</a> Lock timeout and nested lock support in GeoServer</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12055">GEOS-12055</a> GeoServerSecurityManager.reload() not clearing service caches</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12060">GEOS-12060</a> REST API with PUT does not allow un un-set a field</li>
</ul>

<p>Task:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12027">GEOS-12027</a> Removing not needed org.restlet.ext.fileupload dependency</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12028">GEOS-12028</a> Update ‘com.google.code.gson’ dependency version</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12029">GEOS-12029</a> Update ‘com.google.protobuf’ dependency version</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12049">GEOS-12049</a> Remove GWC InMemory cache support</li>
</ul>

<p>For the complete list see <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.3">2.28.3</a> release notes.</p>

<h2 id="community-updates">Community Updates</h2>

<p>Community module development:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11509">GEOS-11509</a> OGC API 3D GeoVolumes community module</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12002">GEOS-12002</a> hz-cluster: homepage pop-up fails</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12030">GEOS-12030</a> Features templating xstream tags conflict with geofence</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12044">GEOS-12044</a> STAC search endpoint should report invalid collection names as invalid parameters instead of internal errors</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12061">GEOS-12061</a> New Community Module for PNG-WIND output format for wind datasets</li>
</ul>

<p>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.</p>

<h1 id="about-geoserver-228-series">About GeoServer 2.28 Series</h1>

<p>Additional information on GeoServer 2.28 series:</p>

<ul>
  <li><a href="https://docs.geoserver.org/2.28.x/en/user/">GeoServer 2.28 User Manual</a></li>
  <li><a href="/behind%20the%20scenes/2025/10/14/developer-update.html">GeoServer 2025 Q4 Developer Update</a>* <a href="https://github.com/geoserver/geoserver/wiki/GSIP-234">Advertise and Enforce Attribute Restrictions</a></li>
</ul>

<p>Release notes:
( <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.3">2.28.3</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.2">2.28.2</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.1">2.28.1</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.0">2.28.0</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.28-M0">2.28-M0</a>
)</p>]]></content><author><name>Andrea Aime</name></author><category term="Announcements" /><category term="Release" /><summary type="html"><![CDATA[GeoServer 2.28.3 release is now available with downloads (bin, war, windows), along with docs and extensions.]]></summary></entry><entry><title type="html">GeoServer 2.27.5 Release</title><link href="https://geoserver.org/announcements/2026/02/18/geoserver-2-27-5-released.html" rel="alternate" type="text/html" title="GeoServer 2.27.5 Release" /><published>2026-02-18T00:00:00+00:00</published><updated>2026-02-18T00:00:00+00:00</updated><id>https://geoserver.org/announcements/2026/02/18/geoserver-2-27-5-released</id><content type="html" xml:base="https://geoserver.org/announcements/2026/02/18/geoserver-2-27-5-released.html"><![CDATA[<p>GeoServer <a href="/release/2.27.5/">2.27.5</a> release is now available
with downloads
(<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.5/geoserver-2.27.5-bin.zip/download">bin</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.5/geoserver-2.27.5-war.zip/download">war</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.5/GeoServer-2.27.5-winsetup.exe/download">windows</a>), along with 
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.5/geoserver-2.27.5-htmldoc.zip/download">docs</a> and
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.5/extensions/">extensions</a>.</p>

<p>This is the last scheduled maintenance release of GeoServer series 2.27 - providing existing installations with minor updates and bug fixes.
GeoServer 2.27.5 is made in conjunction with GeoTools 33.5, and GeoWebCache 1.27.5.</p>

<p>Are you aware that the all new <a href="https://geoserver.org/behind%20the%20scenes/2026/02/17/gs3-first-public-release-date.html">GeoServer 3</a> is just around the corner?</p>

<hr />

<p>And, separately as a special sneak peek, if you’re interested in ARM64 docker images (for example, on AWS, Graviton3 offers a 40% better price performance) then check out <a href="https://hub.docker.com/repository/docker/petersmythe/geoserver-test/tags?name=2.27">this 2.27.5 release</a> as a multi-platform (amd64 &amp; arm4) build, which will very soon be <a href="https://github.com/geoserver/docker/pull/263">merged</a> into the official <a href="https://docker.osgeo.org/#browse/browse:docker:v2%2Fgeoserver%2Ftags%2F2.27.5">docker.osgeo.org repo</a> as the new multi-architecture builder going forward.</p>

<p>Thanks to Peter Smythe (AfriGIS) for making this release and driving the ARM64 docker images.</p>

<h2 id="release-notes">Release notes</h2>

<p>Improvement:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12023">GEOS-12023</a> Improve developer logging during catalog resources loading and WMS capabilities requests</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12033">GEOS-12033</a> Allow to configure custom CRS authorities and transformations</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12037">GEOS-12037</a> Support Metatiling on MapBox Vectortiles</li>
</ul>

<p>Task:</p>

<p>For the complete list see <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.5">2.27.5</a> release notes.</p>

<h1 id="about-geoserver-227-series">About GeoServer 2.27 Series</h1>

<p>Additional information on GeoServer 2.27 series:</p>

<ul>
  <li><a href="https://docs.geoserver.org/2.27.x/en/user/">GeoServer 2.27 User Manual</a></li>
  <li><a href="/announcements/2025/07/16/cite-certification.html">CITE Certification achieved</a></li>
  <li><a href="/behind%20the%20scenes/2025/05/13/developer-update.html">GeoServer 2025 Q2 Developer Update</a></li>
  <li><a href="/behind%20the%20scenes/2025/01/13/roadmap.html">GeoServer 2025 Roadmap</a></li>
  <li><a href="https://github.com/geoserver/geoserver/wiki/GSIP-227">Content-Security-Policy Headers</a></li>
  <li><a href="https://github.com/geoserver/geoserver/wiki/GSIP-230">OGCAPI Features Extension</a></li>
  <li><a href="https://github.com/geoserver/geoserver/wiki/GSIP-229">File system access isolation</a></li>
  <li><a href="https://github.com/geoserver/geoserver/wiki/GSIP-231">Promote data dir catalog loader to core</a></li>
</ul>

<p>Release notes:
( <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.5">2.27.5</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.4">2.27.4</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.3">2.27.3</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.2">2.27.2</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.1">2.27.1</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.0">2.27.0</a>
)</p>]]></content><author><name>Peter Smythe</name></author><category term="Announcements" /><category term="Release" /><summary type="html"><![CDATA[GeoServer 2.27.5 release is now available with downloads (bin, war, windows), along with docs and extensions.]]></summary></entry><entry><title type="html">GeoServer 3 First public release date</title><link href="https://geoserver.org/behind%20the%20scenes/2026/02/17/gs3-first-public-release-date.html" rel="alternate" type="text/html" title="GeoServer 3 First public release date" /><published>2026-02-17T00:00:00+00:00</published><updated>2026-02-17T00:00:00+00:00</updated><id>https://geoserver.org/behind%20the%20scenes/2026/02/17/gs3-first-public-release-date</id><content type="html" xml:base="https://geoserver.org/behind%20the%20scenes/2026/02/17/gs3-first-public-release-date.html"><![CDATA[<p>We are happy to announce that GeoServer 3 is approaching general availability with a target release date of <strong>15th of April 2026</strong>.</p>

<p><img src="/img/posts/3.0/gs3-release-date.png" alt="GeoServer 3 Milestone Progress" style="display:block; margin-left:auto; margin-right:auto; width:100%;" /></p>

<p>This major upgrade modernises the platform’s foundation with the migration to Spring 7 and JDK 17, brings a refreshed user experience and replaces legacy image-processing components with ImageN to deliver significantly improved raster performance and maintainability. The release aligns GeoServer with current Java ecosystems, strengthens security and vulnerability management, and simplifies cloud-native deployments. You can read more about the GeoServer 3 initiative on <a href="/sponsor/gs3-crowdfunding">this</a> page.</p>

<p>GeoServer 3 progress has been made possible by a successful community crowdfunding campaign.  This activity is possible due to financial support of sponsors listed below, and a consortium (Camptocamp, GeoCat and GeoSolutions) providing coordination and additional co-funding to move from planning into delivery.</p>

<p>We will publish additional announcements, along with upgrade and testing instructions in the coming weeks. The core team will ask for focused community testing on upgrade paths, high-volume raster workflows,and tiling scenarios. Final QA, packaging and documentation work is ongoing to ensure a smooth upgrade experience and clear operational guidance for administrators.</p>

<p>Watch the usual GeoServer channels for the release announcement and release notes. Contact the project team if your organisation can help with final testing or needs tailored migration assistance.</p>

<p>
  GeoServer 3 is supported by the following organisations:
</p>
<!-- alphabetical -->
<p><a href="https://www.afrigis.co.za/">
  <img src="/support/img/AfriGIS-full-logo.png" title="AfriGIS" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://camptocamp.com/">
  <img src="/support/img/camptocamp-logo.png" title="Camptocamp" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.dlr.de/de">
  <img src="/sponsor/img/dlr-logo.svg" title="DLR" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.dorsetcouncil.gov.uk">
  <img src="/sponsor/img/dorset-council-logo.png" title="Dorset Council" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.telekom.com">
  <img src="/sponsor/img/telekom-logo.svg" title="Deutsche Telekom" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://frachtwerk.de">
  <img src="/sponsor/img/frachwerk-logo.svg" title="Frachtwerk GmbH" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.geocat.com/">
  <img src="/support/img/core-geocat.png" title="GeoCat BV" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.geocrafter.eu">
  <img src="/sponsor/img/geocrafter-geospatial-studio-logo.png" title="Geocrafter - Geospatial Studio" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.comune.genova.it">
  <img src="/sponsor/img/genova-logo.png" title="Comune di Genova" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.gon.de/en">
  <img src="/sponsor/img/gon-logo.png" title="g.on" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.geosolutionsgroup.com/">
  <img src="/support/img/core-geosolutions.png" title="GeoSolutions SRL" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://geosos.net">
  <img src="/sponsor/img/geosos.png" title="geosos" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.getmap.eu/">
  <img src="/sponsor/img/get-logo.png" title="Geospatial Enabling Technologies (GET)" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://incloud.com">
  <img src="/sponsor/img/incloud-logo.png" title="Incloud Limited" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.linkedin.com/in/lucvanlinden/">
  <img src="/sponsor/img/hl-consulting.png" title="HL Consulting" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://ign.fr/">
  <img src="/sponsor/img/ign-logo.png" title="Institut national de l'information géographique et forestière (IGN)" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.its-digital.de/">
  <img src="/sponsor/img/its-digital.svg" title="ITS Digital" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://jdev.fr">
  <img src="/sponsor/img/jdev-logo.svg" title="JDev" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.kfw.de/">
  <img src="/sponsor/img/kfw-logo.svg" title="Kreditanstalt für Wiederaufbau" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://mammothgeospatial.com">
  <img src="/sponsor/img/mammoth-logo.svg" title="Mammoth Geospatial" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://oceanservice.noaa.gov/">
  <img src="/sponsor/img/nos-logo.png" title="NOA National Ocean Service" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.plangis.de">
  <img src="/sponsor/img/plangis-logo.svg" title="Plangis" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.gov.ie/en/organisation/office-of-public-works/">
  <img src="/sponsor/img/opw-logo.png" title="Office of Public Works" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.osgeo.kr">
  <img src="/sponsor/img/osgeo-kr-logo.svg" title="OSGeo:Korea" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://uk.osgeo.org">
  <img src="/sponsor/img/osgeo-uk-logo.png" title="OSGeo:UK" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.quarticle.ro">
  <img src="/sponsor/img/quarticle-logo.svg" title="Quarticle Research Srl" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://hurrevac.com/">
  <img src="/sponsor/img/sea-island-software-logo.png" title="Sea Island Software" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.tailormap.com/">
  <img src="/sponsor/img/tailormap-logo.svg" title="Tailormap" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.terrestris.de/">
  <img src="/sponsor/img/terrestris-logo.png" title="Terrestris" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.ubigu.fi/en/home//">
  <img src="/sponsor/img/ubigu-logo.png" title="Ubigu" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.value-marktdaten.de/en/portfolio/market-database/real-estate-price-maps/">
  <img src="/sponsor/img/value-logo.png" title="Value AG" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://www.vgregion.se/">
  <img src="/sponsor/img/vastra-gotaland-logo.svg" title="Region Västra Götaland" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<a href="https://waldexpert.waldportal-bw.de/">
  <img src="/sponsor/img/waldexpert-logo.svg" title="WaldExpert" style="display:inline; margin-left:5px; margin-right:5px; min-width: 80px; max-width: 150px; max-height: 80px;" /> 
</a>
<br /></p>
<p>
  Individual donations: Abhijit Gujar, Hennessy Becerra, Ivana Ivanova, John Bryant, Jason Horning, Jose Macchi, Peter Smythe, Sajjadul Islam, Sebastiano Meier, Stefan Overkamp.
</p>]]></content><author><name>Jody Garnett</name></author><category term="Behind The Scenes" /><summary type="html"><![CDATA[We are happy to announce that GeoServer 3 is approaching general availability with a target release date of 15th of April 2026.]]></summary></entry><entry><title type="html">GeoServer 2.28.2 Release</title><link href="https://geoserver.org/announcements/2026/01/21/geoserver-2-28-2-released.html" rel="alternate" type="text/html" title="GeoServer 2.28.2 Release" /><published>2026-01-21T00:00:00+00:00</published><updated>2026-01-21T00:00:00+00:00</updated><id>https://geoserver.org/announcements/2026/01/21/geoserver-2-28-2-released</id><content type="html" xml:base="https://geoserver.org/announcements/2026/01/21/geoserver-2-28-2-released.html"><![CDATA[<p>GeoServer <a href="/release/2.28.2/">2.28.2</a> release is now available
with downloads
(<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.2/geoserver-2.28.2-bin.zip/download">bin</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.2/geoserver-2.28.2-war.zip/download">war</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.2/GeoServer-2.28.2-winsetup.exe/download">windows</a>), along with 
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.2/geoserver-2.28.2-htmldoc.zip/download">docs</a> and
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.2/extensions/">extensions</a>.</p>

<p>This is a stable release of GeoServer recommended for production use.
GeoServer 2.28.2 is made in conjunction with GeoTools 34.2, and GeoWebCache 1.28.2.</p>

<p>Thanks to Gabriel Roldan for making this release.</p>

<h2 id="release-notes">Release notes</h2>

<p>Improvement:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11996">GEOS-11996</a> Security for STAC/Opensearch for EO</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12012">GEOS-12012</a> Switching CSVPPIO Strategy from ATTRIBUTES_ONLY_STRATEGY to WKT_STRATEGY</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12023">GEOS-12023</a> Improve developer logging during catalog resources loading and WMS capabilities requests</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12024">GEOS-12024</a> Add Git branch name in GEOSERVER_NODE_OPTS</li>
</ul>

<p>Bug:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-10509">GEOS-10509</a> WFS Request fails when XML POST body is larger than 8kB</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11926">GEOS-11926</a> ogcapi plugin makes WFS advertising an outputFormat which is actually unavailable</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11979">GEOS-11979</a> CloseableIterators not closed by OGC API Features</li>
</ul>

<p>Sub-task:</p>

<p>For the complete list see <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.2">2.28.2</a> release notes.</p>

<h2 id="community-updates">Community Updates</h2>

<p>Community module development:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11947">GEOS-11947</a> Add the ability to skip numberMatched in STAC/OpenSearch for EO responses</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12000">GEOS-12000</a> Ignore DescribeFeatureType requests without typeName in Features Templating schemas override</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12007">GEOS-12007</a> Add AWS credential chain authentication UI and documentation for GeoParquet</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12013">GEOS-12013</a> Support vector datasets ingestion in VectorMosaic via REST</li>
</ul>

<p>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.</p>

<h1 id="about-geoserver-228-series">About GeoServer 2.28 Series</h1>

<p>Additional information on GeoServer 2.28 series:</p>

<ul>
  <li><a href="https://docs.geoserver.org/2.28.x/en/user/">GeoServer 2.28 User Manual</a></li>
  <li><a href="/behind%20the%20scenes/2025/10/14/developer-update.html">GeoServer 2025 Q4 Developer Update</a>* <a href="https://github.com/geoserver/geoserver/wiki/GSIP-234">Advertise and Enforce Attribute Restrictions</a></li>
</ul>

<p>Release notes:
( <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.2">2.28.2</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.1">2.28.1</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.0">2.28.0</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.28-M0">2.28-M0</a>
)</p>]]></content><author><name>Gabriel Roldan</name></author><category term="Announcements" /><category term="Release" /><summary type="html"><![CDATA[GeoServer 2.28.2 release is now available with downloads (bin, war, windows), along with docs and extensions.]]></summary></entry><entry><title type="html">CITE 2026 Sponsorship</title><link href="https://geoserver.org/announcements/2025/12/30/cite-sponsorship-opportunity.html" rel="alternate" type="text/html" title="CITE 2026 Sponsorship" /><published>2025-12-30T00:00:00+00:00</published><updated>2025-12-30T00:00:00+00:00</updated><id>https://geoserver.org/announcements/2025/12/30/cite-sponsorship-opportunity</id><content type="html" xml:base="https://geoserver.org/announcements/2025/12/30/cite-sponsorship-opportunity.html"><![CDATA[<p>A major accomplishment in 2025 was <a href="/announcements/2025/07/16/cite-certification.html">re-achieving CITE Certification</a> status for GeoServer. Many thanks to all who were involved!  After approximately 10 years, we can once again officially confirm that GeoServer is OGC compliant.</p>

<p>Maintaining Certification is an annual expense for the project - and a sponsorship opportunity for you!</p>

<p>Thanks to <a href="https://gaia3d.com/">Gaia3D</a> and <a href="https://uk.osgeo.org/">OSGeo:UK</a> for sponsorship covering the expense of CITE Certification for 2025.</p>

<p><a href="https://gaia3d.com">
  <img src="/sponsor/img/gaia3d-logo.png" title="Gaia3D" style="height: auto; width: auto; max-width: 140px; max-height: 52px;" />
</a>
<a href="https://uk.osgeo.org">
  <img src="/sponsor/img/osgeo-uk-logo.png" title="OSGeo:UK" style="height: auto; width: auto; max-width: 140px; max-height: 52px;" />
</a></p>

<h3 id="certification-january-9th-2026-deadline">Certification January 9th 2026 Deadline</h3>

<p>Our 2025 CITE Certification for GeoServer 2.27 expires on January 9th.</p>

<p><img src="/img/posts/2.28/cite-sponsorship-opening.png" alt="CITE Sponsorship Opening" style="display:block; margin-left:auto; margin-right:auto; width:100%;" /></p>

<p>This certification process is an annual expense of around $1000 USD, and we will require sponsorship for 2026 to maintain certified status. GeoServer implements a number of different standards, each one of which costs $150 USD to certify each year. The $150 per certification cost makes use of <a href="https://www.ogc.org/how-our-compliance-program-works/">an agreed on rate</a> offered to the Open Source Geospatial Foundation as a not-for-profit organization. The approximate $1000 USD expense will increase slightly as we gradually adopt additional OGC API standards into the application.</p>

<h3 id="cite-2026-sponsorship-opportunity">CITE 2026 Sponsorship Opportunity</h3>

<p>OGC CITE Certification is important for several reasons:</p>

<ul>
  <li>Provides assurance that GeoServer may be integrated in solutions as intended by Open Geospatial Consortium.</li>
  <li>Offers an independent source of black-box testing ensuring that each GeoServer release behaves as intended.</li>
  <li>The Provides a logo and visibility for the project helping to promote the use of open standards.</li>
  <li>Inclusion in the <a href="https://portal.ogc.org/public_ogc/compliance/compliant.php">list of certified products</a> helps people discover GeoServer, and allows GeoServer to be used by organizations requiring certification.</li>
</ul>

<p>In addition to CITE certification offering value for the project, sponsoring can provide excellent visibility
for potential sponsors, with your logo appearing on the GeoServer home page, and in presentations when each
standard is mentioned.</p>

<p><img src="/img/posts/2.28/cite-sponsorship-homepage.png" alt="CITE Home Page Visibility" style="width:45%;" /> <img src="/img/posts/2.28/cite-sponsorship-slides.png" alt="Service Slides Visibility" style="width:45%;" /></p>

<p>If you/your organization is in position to support this activity, please contact any member of <a href="https://docs.geoserver.org/latest/en/developer/policies/psc.html">Project Steering Committee</a>, or the <a href="mailto:treasurer@osgeo.org?subject=GeoServer 2026 CITE Sponsorship&amp;body=We would like to sponsor the GeoServer Project 2026 CITE Certification activity.">OSGeo treasurer</a>. For details visit the <a href="/sponsor">GeoServer Sponsorship Page</a>. The more organizations that are able to sponsor, the lower the expense will be to each organization (sharing the approx USD $1,000 per year cost).</p>

<p>Thank you for your support!</p>

<h3 id="cite-2026-sponsorship-fulfilled">CITE 2026 Sponsorship Fulfilled</h3>

<p><strong>Sponsorship:</strong> Thanks to the following organizations for stepping forward with financial assistance. We are now in position to maintain certification for calendar year 2026.</p>

<p><a href="https://gaia3d.com">
  <img src="/sponsor/img/gaia3d-logo.png" title="Gaia3D" style="height: auto; width: auto; max-width: 140px; max-height: 52px;" />
</a>
<a href="https://www.geocat.com">
  <img src="/support/img/core-geocat.png" title="GeoCat BV" style="height: auto; width: auto; max-width: 140px; max-height: 52px;" />
</a></p>

<p><strong>In-Kind:</strong> Thanks to following organizations for “reference implementation” certification. To act as a reference implementation GeoServer must maintain a service operating as an example of how the standard is intended to function. The Open Source Geospatial Foundation has provided hosting, and AfriGIS provided setup and maintenance.</p>

<p><a href="https://www.afrigis.co.za/">
  <img src="/support/img/AfriGIS-full-logo.png" width="179" style="height: auto; width: auto; max-width: 140px; max-height: 52px;" title="AfriGIS" />
</a>
<a href="https://osgeo.org">
  <img src="/img/osgeo-logo.png" width="179" style="height: auto; width: auto; max-width: 140px; max-height: 52px;" title="Open Source Geospatial Foundation" />
</a></p>

<p><strong>In-Kind:</strong> Finally, thanks to the organizations that have directly contributed to passing the test and integrating these tests into our quality assurance workflows.</p>

<p><a href="https://www.geosolutionsgroup.com">
  <img src="/support/img/core-geosolutions.png" width="179" style="height: auto; width: auto; max-width: 140px; max-height: 52px;" title="GeoSolutions" />
</a>
<a href="https://camptocamp.com/">
  <img src="/support/img/camptocamp-logo.png" width="179" style="height: auto; width: auto; max-width: 140px; max-height: 52px;" title="Camptocamp" />
</a></p>]]></content><author><name>Jody Garnett</name></author><category term="Announcements" /><summary type="html"><![CDATA[A major accomplishment in 2025 was re-achieving CITE Certification status for GeoServer. Many thanks to all who were involved! After approximately 10 years, we can once again officially confirm that GeoServer is OGC compliant.]]></summary></entry><entry><title type="html">GeoServer 2.27.4 Release</title><link href="https://geoserver.org/announcements/vulnerability/2025/12/18/geoserver-2-27-4-released.html" rel="alternate" type="text/html" title="GeoServer 2.27.4 Release" /><published>2025-12-18T00:00:00+00:00</published><updated>2025-12-18T00:00:00+00:00</updated><id>https://geoserver.org/announcements/vulnerability/2025/12/18/geoserver-2-27-4-released</id><content type="html" xml:base="https://geoserver.org/announcements/vulnerability/2025/12/18/geoserver-2-27-4-released.html"><![CDATA[<p>GeoServer <a href="/release/2.27.4/">2.27.4</a> release is now available
with downloads
(<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.4/geoserver-2.27.4-bin.zip/download">bin</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.4/geoserver-2.27.4-war.zip/download">war</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.4/GeoServer-2.27.4-winsetup.exe/download">windows</a>), along with 
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.4/geoserver-2.27.4-htmldoc.zip/download">docs</a> and
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.27.4/extensions/">extensions</a>.</p>

<p>This is a maintenance release of GeoServer providing existing installations with minor updates and bug fixes.
GeoServer 2.27.4 is made in conjunction with GeoTools 33.4, and GeoWebCache 1.27.4.</p>

<p>Thanks to Peter Smythe (AfriGIS) for making this release.</p>

<h2 id="security-considerations">Security Considerations</h2>

<p>This release addresses security vulnerabilities and is an important upgrade for production systems.</p>

<p>See project <a href="https://github.com/geoserver/geoserver/blob/main/SECURITY.md">security policy</a> for more information on how security vulnerabilities are managed.</p>

<h2 id="release-notes">Release notes</h2>

<p>Improvement:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12012">GEOS-12012</a> Switching CSVPPIO Strategy from ATTRIBUTES_ONLY_STRATEGY to WKT_STRATEGY</li>
</ul>

<p>Bug:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-10509">GEOS-10509</a> WFS Request fails when XML POST body is larger than 8kB</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11926">GEOS-11926</a> ogcapi plugin makes WFS advertising an outputFormat which is actually unavailable</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11930">GEOS-11930</a> OGC-API extension breaks security REST API</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11965">GEOS-11965</a> KMZ export incorrectly references remote icon URLs instead of embedding them in the KMZ archive</li>
  <li>
    <table>
      <tbody>
        <tr>
          <td><a href="https://osgeo-org.atlassian.net/browse/GEOS-11981">GEOS-11981</a> POST /security/authproviders</td>
          <td>400: Unsupported className</td>
        </tr>
      </tbody>
    </table>
  </li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11988">GEOS-11988</a> Fix bug: preserve metaTilingThreads=0 in saneConfig()</li>
</ul>

<p>For the complete list see <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.4">2.27.4</a> release notes.</p>

<h2 id="community-updates">Community Updates</h2>

<p>Community module development:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11947">GEOS-11947</a> Add the ability to skip numberMatched in STAC/OpenSearch for EO responses</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11983">GEOS-11983</a> GSR /query fails with HTTP 500 when where parameter is empty</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-12000">GEOS-12000</a> Ignore DescribeFeatureType requests without typeName in Features Templating schemas override</li>
</ul>

<p>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.</p>

<h1 id="about-geoserver-227-series">About GeoServer 2.27 Series</h1>

<p>Additional information on GeoServer 2.27 series:</p>

<ul>
  <li><a href="https://docs.geoserver.org/2.27.x/en/user/">GeoServer 2.27 User Manual</a></li>
  <li><a href="/announcements/2025/07/16/cite-certification.html">CITE Certification achieved</a></li>
  <li><a href="/behind%20the%20scenes/2025/05/13/developer-update.html">GeoServer 2025 Q2 Developer Update</a></li>
  <li><a href="/behind%20the%20scenes/2025/01/13/roadmap.html">GeoServer 2025 Roadmap</a></li>
  <li><a href="https://github.com/geoserver/geoserver/wiki/GSIP-227">Content-Security-Policy Headers</a></li>
  <li><a href="https://github.com/geoserver/geoserver/wiki/GSIP-230">OGCAPI Features Extension</a></li>
  <li><a href="https://github.com/geoserver/geoserver/wiki/GSIP-229">File system access isolation</a></li>
  <li><a href="https://github.com/geoserver/geoserver/wiki/GSIP-231">Promote data dir catalog loader to core</a></li>
</ul>

<p>Release notes:
( <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.4">2.27.4</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.3">2.27.3</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.2">2.27.2</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.1">2.27.1</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.27.0">2.27.0</a>
)</p>]]></content><author><name>Peter Smythe</name></author><category term="Announcements" /><category term="Vulnerability" /><category term="Release" /><summary type="html"><![CDATA[GeoServer 2.27.4 release is now available with downloads (bin, war, windows), along with docs and extensions.]]></summary></entry><entry><title type="html">Master GeoServer WPS - Buffer &amp;amp; Intersection Analysis</title><link href="https://geoserver.org/tutorials/2025/12/03/WPS-Buffer-Intersection.html" rel="alternate" type="text/html" title="Master GeoServer WPS - Buffer &amp;amp; Intersection Analysis" /><published>2025-12-03T00:00:00+00:00</published><updated>2025-12-03T00:00:00+00:00</updated><id>https://geoserver.org/tutorials/2025/12/03/WPS-Buffer-Intersection</id><content type="html" xml:base="https://geoserver.org/tutorials/2025/12/03/WPS-Buffer-Intersection.html"><![CDATA[<p><a href="https://www.youtube.com/@geospatialtechno">GeoSpatial Techno</a> 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.</p>

<p>( <a href="https://www.youtube.com/@geospatialtechno">YouTube</a>
| <a href="https://www.linkedin.com/in/geospatialtechno">LinkedIn</a>
| <a href="https://www.facebook.com/geospatialtechno">Facebook</a>
| <a href="https://twitter.com/geospatialtechn">X</a>
)</p>

<hr />
<h3 id="master-geoserver-wps---essential-buffer--intersection-analysis-techniques">Master GeoServer WPS - Essential Buffer &amp; Intersection Analysis Techniques!</h3>
<p>This blog post provides how to use the Buffer and Intersection analysis in the WPS Request Builder. 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.</p>

<p>If you want to access the complete tutorial, click on the <a href="https://www.youtube.com/watch?v=sCu661DeuL0&amp;list=PL_ITaxp1Ob4sjk24Stboa5XbO0LGdEKbL">link</a>.</p>

<p><a href="https://www.youtube.com/watch?v=sCu661DeuL0&amp;list=PL_ITaxp1Ob4sjk24Stboa5XbO0LGdEKbL"><img src="https://img.youtube.com/vi/sCu661DeuL0/0.jpg" alt="" /></a></p>

<h2 id="introduction">Introduction</h2>
<p>Buffer analysis is a crucial process in Geographic Information Systems (GIS). It involves creating a zone around geographic features — such as points, lines, or polygons — to analyze spatial relationships and proximity. This type of analysis has various applications, including determining influence areas, assessing environmental impacts, and evaluating accessibility. It provides insights for decision-making in fields such as Urban planning, Natural resource management, and Emergency response planning.</p>

<p>In GeoServer, users can create buffer zones around geographic features by specifying the input geometries and the buffer distance. This functionality is part of the GeoServer WPS extension, which provides a standardized interface for various geospatial processing algorithms.</p>

<p>To create buffers in GeoServer, navigate to the <strong>Demos</strong> section and select the <strong>WPS Request Builder</strong> option. In the <strong>Choose Process</strong> section, type <code class="language-plaintext highlighter-rouge">buffer</code> to see a list of available buffer related process. As you can see, GeoServer has six such processes.</p>

<p>As mentioned in our previous blog post, the <strong>JTS</strong> and <strong>geo</strong> processes do not directly access to the GeoServer layers. Instead, these processes utilize external libraries, specifically the Java Topology Suite (JTS) and GeoTools.</p>

<h2 id="jtsbuffer">JTS:buffer</h2>

<ul>
  <li>From the list, select <strong>JTS:buffer</strong>. This operation requires three inputs for execution: <code class="language-plaintext highlighter-rouge">Text</code>, <code class="language-plaintext highlighter-rouge">Reference</code>, and <code class="language-plaintext highlighter-rouge">SubProcess</code>.</li>
</ul>

<p>In the text mode, you need to enter the geometry data in a standard formats For this example, use the <strong>application/wkt</strong> as the input format, and enter the geometry data:</p>

<div class="language-text highlighter-rouge"><div class="highlight"><pre class="highlight"><code>POINT(-100 50)
</code></pre></div></div>

<ul>
  <li>Enter the buffer distance in the <strong>Distance</strong> textbox. This parameter defines the size of the buffer created around the input feature and is represented as a double data type. In this case, enter <code class="language-plaintext highlighter-rouge">0.1</code> degrees, which is based on <strong>EPSG:4326</strong> coordinate system.</li>
</ul>

<p><strong>Note</strong>: The distance value is mandatory and corresponds to the geometric units being used.</p>

<ul>
  <li>
    <p>Choose your desired output format from the <strong>Process Outputs</strong> section. This enabled you to select the most appropriate format for your specific usecase or workflow. The result can be further processed, visualized, or used for additional spatial analysis. The available formats include:  <strong>application/wkt</strong> ,	<strong>application/json</strong>.</p>
  </li>
  <li>
    <p>Select the <strong>application/wkt</strong> format and press the <strong>Execute process in New Page</strong> button.</p>
  </li>
</ul>

<p>Now that you have executed the buffer operation, you can view the results. Navigate to <a href="https://www.wktmap.com/">WKT Map</a> and enter the resulting geometries in the WKT textbox to visualize the buffer created around the specified point.</p>

<p><img src="/img/posts/2.26/buffer.png" alt="buffer" style="display:block; margin-left:auto; margin-right:auto; width:70%;" /></p>

<p>Go back to geoserver software to explain other parameters:</p>

<ul>
  <li>
    <p>The <strong>quadrantSegments</strong> parameter in the <strong>JTS:buffer</strong>, is an optional parameter for shaping quarter-circle buffers. Increasing its value enhances the buffer’s smoothness and circularity but also raises vertex count, which can affect performance.</p>
  </li>
  <li>
    <p>The default is 8 segments, which create 32 sides that are more circular than the others. It’s important to balance precision with processing efficiency, as a higher value improves curve quality but increases computational complexity.</p>
  </li>
  <li>
    <p>Set the <strong>distance</strong> buffer to <code class="language-plaintext highlighter-rouge">0.11</code> and <strong>quadrantSegments</strong> to <code class="language-plaintext highlighter-rouge">3</code>, then press the <strong>Execute process in New page</strong>. Now see the resulting shape. Note that the distance value is measured in units provided by coordinate reference system (not in pixels).</p>
  </li>
</ul>

<p>As you can see, the result is somewhat circular due to the smaller number of sides.</p>

<p><img src="/img/posts/2.26/buffer_quad.png" alt="buffer_quad" style="display:block; margin-left:auto; margin-right:auto; width:70%;" /></p>

<p>Go back to geoserver again to explain the last parameter, capStyle.</p>

<ul>
  <li>
    <p>The <strong>capStyle</strong> is an optional parameter that specifies the type of cap style used at the ends of buffer polygons. There are three available options: <strong>Round</strong>, <strong>Flat</strong>, and <strong>Square</strong>.</p>
  </li>
  <li><strong>Round</strong>: This is the default option, which creates a rounded appearance at the ends of a buffer around a line feature.</li>
  <li><strong>Flat</strong>: This option creates clean and straight ends.</li>
  <li><strong>Square</strong>: This option creates a more pronounced squared-off effect.</li>
</ul>

<p>By selecting the appropriate cap style, you can customize the appearance of your buffer areas according to your visualization needs.</p>

<ul>
  <li>To use the capStyle option, enter the geometry data in the <strong>application/wkt</strong> format.</li>
</ul>

<div class="language-text highlighter-rouge"><div class="highlight"><pre class="highlight"><code>- Geometry data: LINESTRING (-101.9 37.36, -101.92 37.7, -100.9 37.46)
- Distance value: 0.01
</code></pre></div></div>

<p>Press the <strong>Execute process in New page</strong> button. Repeat this process for the <strong>Flat</strong> and <strong>Square</strong> cap styles and then view the results.</p>

<p><img src="/img/posts/2.26/buffer_capstyle.png" alt="buffer_capstyle" style="display:block; margin-left:auto; margin-right:auto; width:70%;" /></p>

<h2 id="gsbufferfeaturecollection">GS:BufferFeatureCollection</h2>

<p>This function utilizes the GeoTools library to process feature collections by generating buffered geometries around each feature. Users can specify the buffer distance as either a fixed value or dynamically based on a specific field’s value.</p>

<p>The first input parameter is the <strong>InputFeatureCollection</strong>, which can accept four types of input: <strong>Text</strong>, <strong>Reference</strong>, <strong>subprocess</strong>, and <strong>vector_layer</strong>. The default option is the <strong>vector layer</strong>.</p>

<p>For this example, we will use the <code class="language-plaintext highlighter-rouge">archsites</code> layer from GeoServer. Select this layer from the <strong>Choose one</strong> drop-down menu.</p>

<p>We will first apply a fixed value for the buffer distance parameter, followed by using a specific field to dynamically adjust the buffer distance.</p>

<h3 id="fixed-value-buffering">Fixed Value Buffering</h3>
<ul>
  <li>Enter a distance value suited to the coordinate reference system (CRS) of the layer. As the <code class="language-plaintext highlighter-rouge">archsites</code> layer uses the UTM crs, you can set a value like <code class="language-plaintext highlighter-rouge">20</code>.</li>
</ul>

<p><strong>Note</strong>: Filling this parameter is mandatory.</p>

<ul>
  <li>
    <p>Once the input features and distance have been defined, choose the output format for displaying the results of the buffering operation.</p>
  </li>
  <li>
    <p>Select the <strong>application/zip</strong> format from the <strong>Process Outputs</strong> section, and then press the <strong>Execute process in New Page</strong> button.</p>
  </li>
</ul>

<p>After the process is complete, open the result file using QGIS software. You will see that buffer areas of 20 meters have been created around each feature.</p>

<p><img src="/img/posts/2.26/buffer_fixed.png" alt="buffer_fixed" style="display:block; margin-left:auto; margin-right:auto; width:70%;" /></p>

<h3 id="dynamic-value-buffering">Dynamic Value Buffering</h3>
<ul>
  <li>
    <p>To use a specific field for buffer distance, first, enter a <code class="language-plaintext highlighter-rouge">zero</code> value in the mandatory distance box, then specify the attribute name that contains numerical values for the buffer distances.</p>
  </li>
  <li>
    <p>In this example, we will use the <code class="language-plaintext highlighter-rouge">cat</code> attribute.</p>
  </li>
  <li>
    <p>Again, choose the <strong>application/zip</strong> mime-type for the output file format and press the <strong>Execute process in New Page</strong> button.</p>
  </li>
</ul>

<p>After processing is complete, add the resulting file to QGIS software. As you can see the buffer areas around each feature have different distances based on the values found in the <strong>cat</strong> field.</p>

<h2 id="intersection-analysis">Intersection analysis</h2>

<p>Intersection analysis is a crucial spatial technique used in GIS to explore and understand the relationships between various geographic features or datasets. This method focuses on examining how different data layers overlap and interact, which provides valuable insights for decision-making processes in areas such as urban planning, environmental management, and resource allocation.</p>

<p>In GeoServer, Intersection analysis facilitates the identification of overlapping areas between features from two distinct datasets. This operation can be efficiently implemented through the WPS request builder, making spatial analysis both effective and user-friendly.</p>

<p>To carry out an intersection analysis, select <strong>gs:IntersectionFeatureCollection</strong> from the <strong>Choose process</strong> menu.</p>

<ul>
  <li>
    <p>The first and second feature collections, serve as the main input features and are considered mandatory parameters for this process. Other parameters are optional.</p>
  </li>
  <li>
    <p>For this example, choose <code class="language-plaintext highlighter-rouge">sf:streams</code> as the first feature collection and <code class="language-plaintext highlighter-rouge">sf:restricted</code> as the second feature collection.</p>
  </li>
  <li>
    <p>Select the <strong>application/json</strong> format from the <strong>Process Outputs</strong> section, then press the <strong>Execute process in New Page</strong> button.</p>
  </li>
</ul>

<p>After execution, you can view the results by navigating to <a href="https://geojson.io/">geojson.io</a> and entering the resulting geometries in the textbox provided.</p>

<p><img src="/img/posts/2.26/intersection.png" alt="intersection" style="display:block; margin-left:auto; margin-right:auto; width:70%;" /></p>

<p>Go back to geoserver software to explain other parameters:</p>

<p>The intersection analysis also allows you to specify which attributes from the input feature collections should be retained in the output. If this selection is not made, all fields from each layer will be included by default.</p>

<ul>
  <li>In this example, enter <code class="language-plaintext highlighter-rouge">label</code> to retain this specific field from the first layer.</li>
</ul>

<p><strong>IntersectionMode</strong>: This parameter allows users to specify how to handle the intersection of two feature collections. By choosing between the <strong>Intersection</strong>, <strong>First</strong>, and <strong>Second</strong> options, users can tailor the results to fit their specific spatial analysis needs.</p>

<p>Let’s describe each of them:</p>

<ul>
  <li>
    <p><strong>Intersection</strong>: This is the default option, which includes only the features that geometrically overlap between the two input collections. Only areas where both inputs intersect will be represented in the output.</p>
  </li>
  <li>
    <p><strong>First</strong>: This mode filters the first feature collection by retaining only those features that intersect with any feature from the second collection. Features in the first collection without any intersection will be excluded from the output.</p>
  </li>
  <li>
    <p><strong>Second</strong>: This mode outputs features from the second collection, retaining only those that intersect with any feature from the first collection.</p>
  </li>
  <li>
    <p>For this example, we select the <strong>First</strong> option in the <strong>intersectionMode</strong> parameter.</p>
  </li>
</ul>

<p>To view the results and incorporate the resulting geometries into QGIS, press the <strong>Execute process in New Page</strong> button again. The output will consist only the <code class="language-plaintext highlighter-rouge">streams_label</code> field from the first layer.</p>

<p><img src="/img/posts/2.26/intersection_mode.png" alt="interscetion_mode" style="display:block; margin-left:auto; margin-right:auto; width:70%;" /></p>

<p>This means that the output features will only include those from the first collection that intersect with features in the second collection.</p>

<p>Additionally, the analysis includes two boolean options that determine if additional area attributes are included in the output:</p>
<ul>
  <li>
    <p><strong>percentagesEnabled</strong>: When set to <strong>true</strong>, this option includes attributes indicating the percentage of each feature’s area relative to the total area of each respective input feature collection. By default, this option is set to <strong>false</strong>.</p>
  </li>
  <li>
    <p><strong>areasEnabled</strong>: Similar to the <strong>percentagesEnabled</strong> mode, this option when enabled or set to <strong>true</strong>, includes attributes representing the area of each feature in the intersection. Its default setting is also <strong>false</strong>.</p>
  </li>
</ul>

<p>By carefully defining the parameters and choosing the appropriate options, users can effectively perform intersection analysis in GeoServer and generate meaningful spatial insights.</p>

<hr />

<p>In this session, how to use the Buffer and Intersection analysis in the WPS Request Builder. To access the full tutorial, click on this <a href="https://www.youtube.com/watch?v=sCu661DeuL0&amp;list=PL_ITaxp1Ob4sjk24Stboa5XbO0LGdEKbL">link</a>.</p>]]></content><author><name>Nima Ghasemloo</name></author><category term="Tutorials" /><summary type="html"><![CDATA[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.]]></summary></entry><entry><title type="html">GeoServer 2.28.1 Release</title><link href="https://geoserver.org/announcements/vulnerability/2025/11/25/geoserver-2-28-1-released.html" rel="alternate" type="text/html" title="GeoServer 2.28.1 Release" /><published>2025-11-25T00:00:00+00:00</published><updated>2025-11-25T00:00:00+00:00</updated><id>https://geoserver.org/announcements/vulnerability/2025/11/25/geoserver-2-28-1-released</id><content type="html" xml:base="https://geoserver.org/announcements/vulnerability/2025/11/25/geoserver-2-28-1-released.html"><![CDATA[<p>GeoServer <a href="/release/2.28.1/">2.28.1</a> release is now available
with downloads
(<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.1/geoserver-2.28.1-bin.zip/download">bin</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.1/geoserver-2.28.1-war.zip/download">war</a>,
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.1/GeoServer-2.28.1-winsetup.exe/download">windows</a>), along with 
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.1/geoserver-2.28.1-htmldoc.zip/download">docs</a> and
<a href="https://sourceforge.net/projects/geoserver/files/GeoServer/2.28.1/extensions/">extensions</a>.</p>

<p>This is a stable release of GeoServer recommended for production use.
GeoServer 2.28.1 is made in conjunction with GeoTools 34.1, and GeoWebCache 1.28.1.</p>

<p>Thanks to Andrea Aime for making this release.</p>

<h2 id="security-considerations">Security Considerations</h2>

<p>This release addresses security vulnerabilities and is considered an important upgrade for production systems.</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11921">GEOS-11921</a> - <a href="https://github.com/geoserver/geoserver/security/advisories/GHSA-w66h-j855-qr72">CVE-2025-21621</a> - Reflected Cross-Site Scripting (XSS) vulnerability in WMS GetFeatureInfo HTML format (Moderate)</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11922">GEOS-11922</a> - <a href="https://github.com/geoserver/geoserver/security/advisories/GHSA-fjf5-xgmq-5525">CVE-2025-58360</a> - Unauthenticated XXE via WMS GetMap (High)</li>
</ul>

<p>The use of the CVE system allows the GeoServer team to reach a wider audience than blog posts.</p>

<p>See project <a href="https://github.com/geoserver/geoserver/blob/main/SECURITY.md">security policy</a> for more information on how security vulnerabilities are managed.</p>

<h2 id="release-notes">Release notes</h2>

<p>Improvement:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11950">GEOS-11950</a> WMS cascade: fully respect ‘restrict to layer bounds’ flag on GetMap requests</li>
</ul>

<p>Bug:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-4159">GEOS-4159</a> Layer from SQL view feature type details not refreshing after editing sql query (and refreshing attributes there)</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11930">GEOS-11930</a> OGC-API extension breaks security REST API</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11963">GEOS-11963</a> BlobStorePage breaks when failing to save a blob store configuration</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11965">GEOS-11965</a> KMZ export incorrectly references remote icon URLs instead of embedding them in the KMZ archive</li>
  <li>
    <table>
      <tbody>
        <tr>
          <td><a href="https://osgeo-org.atlassian.net/browse/GEOS-11981">GEOS-11981</a> POST /security/authproviders</td>
          <td>400: Unsupported className</td>
        </tr>
      </tbody>
    </table>
  </li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11988">GEOS-11988</a> Fix bug: preserve metaTilingThreads=0 in saneConfig()</li>
</ul>

<p>Task:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11898">GEOS-11898</a> GeoFence: issues in evaluation of virtual layer services access</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11962">GEOS-11962</a> Run CITE tests against Java 17, 21 and 25</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11987">GEOS-11987</a> ImageN 0.9.1 migration requires renaming of registryFile.jai to registryFile.imagen</li>
</ul>

<p>For the complete list see <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.1">2.28.1</a> release notes.</p>

<h2 id="community-updates">Community Updates</h2>

<p>Community module development:</p>

<ul>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11959">GEOS-11959</a> New community module GeoWebCache Google Cloud Storage</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11961">GEOS-11961</a> OSEO layer management: Support creation of image mosaics in CRS other than 4326</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11980">GEOS-11980</a> Add support for uploading a single parquet file to GeoServer via REST</li>
  <li><a href="https://osgeo-org.atlassian.net/browse/GEOS-11983">GEOS-11983</a> GSR /query fails with HTTP 500 when where parameter is empty</li>
</ul>

<p>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.</p>

<h1 id="about-geoserver-228-series">About GeoServer 2.28 Series</h1>

<p>Additional information on GeoServer 2.28 series:</p>

<ul>
  <li><a href="https://docs.geoserver.org/2.28.x/en/user/">GeoServer 2.28 User Manual</a></li>
  <li><a href="/behind%20the%20scenes/2025/10/14/developer-update.html">GeoServer 2025 Q4 Developer Update</a>* <a href="https://github.com/geoserver/geoserver/wiki/GSIP-234">Advertise and Enforce Attribute Restrictions</a></li>
</ul>

<p>Release notes:
( <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.1">2.28.1</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.28.0">2.28.0</a>
| <a href="https://github.com/geoserver/geoserver/releases/tag/2.28-M0">2.28-M0</a>
)</p>]]></content><author><name>Andrea Aime</name></author><category term="Announcements" /><category term="Vulnerability" /><category term="Release" /><summary type="html"><![CDATA[GeoServer 2.28.1 release is now available with downloads (bin, war, windows), along with docs and extensions.]]></summary></entry></feed>