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

( YouTube | LinkedIn | Facebook | Reddit | X )

GeoServer installation methods: “Windows Installer” and “Web Archive”

GeoServer installation methods: “Windows Installer” and “Web Archive” In this session, we will talk about how to install GeoServer software by two common methods in Windows. If you want to access the complete tutorial, simply click on the link.

Introduction

GeoServer can be installed on different operating systems, since it’s a Java based application. You can run it on any kind of operating system for which exists a Java virtual machine. GeoServer’s speed depends a lot on the chosen Java Runtime Environment (JRE). The latest versions of GeoServer are tested with both OracleJRE and OpenJDK. These versions are:

• Java 17 for GeoServer 2.23 and above
• Java 11 for GeoServer 2.15 and above
• Java 8 for GeoServer 2.9 to GeoServer 2.22
• Java 7 for GeoServer 2.6 to GeoServer 2.8
• Java 6 for GeoServer 2.3 to GeoServer 2.5
• Java 5 for GeoServer 2.2 and earlier

But remember that the older versions are unsupported and won’t receive fixes nor security updates, and contain well-known security vulnerabilities that have not been patched, so use at own risk. That is true for both GeoServer and Java itself.

There are many ways to install GeoServer on your system. This tutorial will cover the two most commonly used installation methods on Windows.

• Windows Installer
• Web Archive

Windows installer

The Windows installer provides an easy way to set up GeoServer on your system, as it requires no configuration files to be edited or command line settings.

Installation

• GeoServer requires a Java environment (JRE) to be installed on your system, available from Adoptium for Windows Installer, or provided by your OS distribution. For more information, please refer to this link: https://docs.geoserver.org/latest/en/user/installation/index.html#installation

Consider the operating system architecture and memory requirements when selecting a JRE installer. 32-bit Java version is restricted to 2 GB memory, while the 64-bit version is recommended for optimal server memory. Utilizing JAI with the 32-bit JRE can enhance performance for WMS output generation and raster operations.

• Install JRE by following the default settings and successfully complete the installation.
• Navigate to the GeoServer.org and download the desired version of GeoServer.
• Launch the GeoServer installer and agree to the license.
• Enter the path to the JRE installation and proceed with the installation. The installer will attempt to automatically populate this box with a JRE if it is found, but otherwise you will have to enter this path manually.
• Provide necessary details like the GeoServer data directory, administration credentials, and port configuration.
• Review the selections, install GeoServer, and start it either manually or as a service.
• Finally, navigate to localhost:8080/geoserver (or wherever you installed GeoServer) to access the GeoServer Web administration interface.

Uninstallation

GeoServer can be uninstalled in two ways:

• By running the uninstall.exe file in the directory where GeoServer was installed
• By standard Windows program removal

Web Archive

GeoServer is packaged as a web-archive (WAR) for use with an application server such as Apache Tomcat or Jetty. It has been mostly tested using Tomcat, and so is the recommended application server. There are reasons for installing it such as it is widely used, well-documented, and relatively simple to configure. GeoServer requires a newer version of Tomcat (7.0.65 or later) that implements Servlet 3 and annotation processing. Other application servers have been known to work, but are not guaranteed.

Installation

• Make sure you have a JRE installed on your system, then download Apache Tomcat from its website(https://tomcat.apache.org). For the Windows installation package, scroll down and choose the 32bit/64bit Windows Service Installer option.
• Configure Tomcat by selecting components, setting up a username and password, and specifying memory settings. So, before start the Tomcat service, you have to configure the memory settings that will use for Java VM. To do it, open the Tomcat9w from the bin folder, then click on the Java tab. This tab allows for configuration of memory settings, including initial and maximum memory pool sizes. Recommended values are 512MB for the initial memory pool and 1024MB for the maximum memory pool.
• Start Tomcat service and verify its functionality, then navigate to localhost:8080, and get the Tomcat9 web page.
• Navigate to the GeoServer.org and Download page. Select Web Archive on the download page from the version of GeoServer that you wish to download.
• Deploy the GeoServer web archive as you would normally. Often, all that is necessary is to copy the GeoServer.war file to the Tomcat’s webapps directory, then the application will be deployed automatically.
• Now to access the Web administration interface, open a browser and navigate to localhost:8080 and press Manager App button. Enter the username and password of apache tomcat. Click on the start button for the GeoServer. Once it has started, click the GeoServer link. This will take you to the GeoServer web page.

Uninstallation

Stop the container application. Remove the GeoServer webapp from the container application’s webapps directory. This will usually include the GeoServer.war file as well as a GeoServer directory.

Difference between GEOSERVER.war and GEOSERVER.exe?

• The ‘GeoServer.exe’ NSIS installer registers GeoServer as a Windows Service, which uses the Jetty application server to run GeoServer. The ‘GeoServer.war’ is a platform independent web-archive package to be deployed in your own application server (we recommend Apache Tomcat). Using the ‘GeoServer.exe’ installer is a reliable way to setup GeoServer as a windows background service. The downside is the included Jetty application server is managed using text files (jetty.ini) once installed.
• Use of ‘GeoServer.war’ web-archive is provided to install into your own application server (we recommend Apache Tomcat as the market leader, with excellent documentation and integration options). A single application server may support several web application allowing GeoServer to be run alongside your own java web application.

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

This is a stable release of GeoServer recommended for production use. GeoServer 2.24.1 is made in conjunction with GeoTools 30.1, and GeoWebCache 1.24.1.

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

Security Considerations

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

• CVE-2023-51444 Arbitrary file upload vulnerability in REST Coverage Store API (High).
• CVE-2024-23819 Stored Cross-Site Scripting (XSS) vulnerability in MapML HTML Page (Moderate).
• CVE-2024-23640 Stored Cross-Site Scripting (XSS) vulnerability in WMS OpenLayers Format (Moderate).
• CVE-2024-23821 Stored Cross-Site Scripting (XSS) vulnerability in GWC Demos Page (Moderate).
• CVE-2024-23643 Stored Cross-Site Scripting (XSS) vulnerability in GWC Seed Form (Moderate).
• CVE-2024-23642 Stored Cross-Site Scripting (XSS) vulnerability in Simple SVG Renderer (Moderate).

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

Release notes

Improvement:

• GEOS-11152 Improve handling special characters in the Simple SVG Renderer
• GEOS-11153 Improve handling special characters in the WMS OpenLayers Format
• GEOS-11154 Improve handling special characters in the MapML HTML Page
• GEOS-11155 Add the X-Content-Type-Options header
• GEOS-11173 Default to using HttpOnly session cookies
• GEOS-11176 Add validation to file wrapper resource paths
• GEOS-11188 Let DownloadProcess handle download requests whose pixel size is larger than integer limits
• GEOS-11189 Add an option to throw a service exception when nearest match “allowed interval” is exceeded
• GEOS-11193 Add an option to throw an exception when the time nearest match does not fall within search limits

Bug:

• GEOS-11074 GeoFence may not load property file at boot
• GEOS-11166 OGC API Maps HTML representation fail without datetime parameter
• GEOS-11184 ncwms module has a compile dependency on gs-web-core test jar
• GEOS-11190 GeoFence: align log4j2 deps
• GEOS-11196 NPE in VectorDownload if ROI not defined
• GEOS-11200 GetFeatureInfo can fail on rendering transformations that generate a different raster
• GEOS-11203 WMS GetFeatureInfo bad WKT exception for label-geometry
• GEOS-11206 Throw nearest match mismatch exceptions only for WMS

For the complete list see 2.24.1 release notes.

Community Module Updates

OAuth2 OpenID-Connect improvements

Two improvements have been made to the community module for OAuth2 OpenID-Connect authentication:

• GEOS-11209 Open ID Connect Proof Key of Code Exchange (PKCE)
• GEOS-11212 OIDC accessToken verification using only JWKs URI

In addition the module includes an OIDC_LOGGING profile and updated documentation covering new settings and troubleshooting guidance.

Thanks Jody Garnett for these improvements on behalf of GeoBeyond.

note: Over the course of 2024 the OAuth2 plugins will need to be rewritten for spring-framework 6. Interested parties are encouraged to reach out to geoserver-devel email list; ideally we would like to see this functionality implemented and included as part of GeoServer.

About GeoServer 2.24 Series

Additional information on GeoServer 2.24 series:

• GeoServer 2.24 User Manual
• State of GeoServer 2.24 (foss4g-na presentation)
• Control remote HTTP requests sent by GeoTools/GeoServer
• Multiple CRS authority support, planetary CRS
• Extensive GeoServer Printing improvements
• Upgraded security policy

Release notes: ( 2.24.1 | 2.24.0 | 2.24-RC )

GeoServer is an Open Source Geospatial Foundation project supported by a mix of volunteer and service provider activity. We reply on sponsorship to fund activities beyond the reach of individual contributors.

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

This is a maintenance release of GeoServer providing existing installations with minor updates and bug fixes. GeoServer 2.23.3 is made in conjunction with GeoTools 29.3, and GeoWebCache 1.23.2.

Thanks to Peter Smythe (AfriGIS) for making this release.

Security Considerations

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

• CVE-2024-23818 Stored Cross-Site Scripting (XSS) vulnerability in WMS OpenLayers Format (Moderate).
• CVE-2024-23640 Stored Cross-Site Scripting (XSS) vulnerability in Style Publisher (Moderate).
• CVE-2023-51445 Stored Cross-Site Scripting (XSS) vulnerability in REST Resources API (Moderate).

This release includes security patches from projects that GeoServer depends on.

• GEOS-11030 Update jetty-server to 9.4.51.v20230217

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

Also, another reminder of the URL check security setting that was introduced in version 2.22.4 and version 2.23.2 (but turned off by default). The latest GeoServer 2.24.0 release has this setting enabled by default. If you are not yet in a position to upgrade to 2.24.0 you are encouraged to enable this recommended setting.

Release notes

New Feature:

• GEOS-11000 WPS process to provide elevation profile for a linestring

Improvement:

• GEOS-10856 geoserver monitor plugin - scaling troubles
• GEOS-11081 Add option to disable GetFeatureInfo transforming raster layers
• GEOS-11087 Fix IsolatedCatalogFacade unnecessary performance overhead
• GEOS-11089 Performance penalty adding namespaces while loading catalog
• GEOS-11090 Use Catalog streaming API in WorkspacePage
• GEOS-11099 ElasticSearch DataStore Documentation Update for RESPONSE_BUFFER_LIMIT
• GEOS-11100 Add opacity parameter to the layer definitions in WPS-Download download maps
• GEOS-11102 Allow configuration of the CSV date format
• GEOS-11114 Improve extensibility in Pre-Authentication scenarios
• GEOS-11116 GetMap/GetFeatureInfo with groups and view params can with mismatched layers/params
• GEOS-11120 Create aggregates filterFunction in OSEO to support STAC Datacube extension implementation
• GEOS-11130 Sort parent role dropdown in Add a new role
• GEOS-11142 Add mime type mapping for yaml files
• GEOS-11148 Update response headers for the Resources REST API
• GEOS-11149 Update response headers for the Style Publisher
• GEOS-11153 Improve handling special characters in the WMS OpenLayers Format
• GEOS-11155 Add the X-Content-Type-Options header

Bug:

• GEOS-10452 Use of Active Directory authorisation seems broken since 2.15.2 (LDAP still works)
• GEOS-11032 Unlucky init order with GeoWebCacheExtension gwcFacade before DiskQuotaMonitor
• GEOS-11138 Jetty unable to start cvc-elt.1.a / org.xml.sax.SAXParseException
• GEOS-11140 WPS download can leak image references in the RasterCleaner
• GEOS-11145 The GUI “wait spinner” is not visible any longer
• GEOS-11166 OGC API Maps HTML representation fail without datetime parameter

Task:

• GEOS-10248 WPSInitializer NPE failure during GeoServer reload
• GEOS-11030 Update jetty-server to 9.4.51.v20230217
• GEOS-11084 Update text field css styling to look visually distinct
• GEOS-11091 Upgrade spring-security to 5.7.10
• GEOS-11092 acme-ldap.jar is compiled with Java 8
• GEOS-11094 Bump org.hsqldb:hsqldb:2.7.1 to 2.7.2
• GEOS-11124 Update json dependency to 20230227 in geowebcache-rest
• GEOS-11141 production consideration for logging configuration hardening

For the complete list see 2.23.3 release notes.

About GeoServer 2.23 Series

Additional information on GeoServer 2.23 series:

• GeoServer 2.23 User Manual
• Drop Java 8
• GUI CSS Cleanup
• Add the possibility to use fixed values in Capabilities for Dimension metadata
• State of GeoServer 2.23
• GeoServer Feature Frenzy 2023
• GeoServer used in fun and interesting ways
• GeoServer Orientation

Release notes: ( 2.23.3 | 2.23.2 | 2.23.1 | 2.23.0 | 2.23-RC1 )

This is a community blog post introducing Geospatial Techno, along with a sample of one of their GeoServer training videos.

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

( YouTube | LinkedIn | Reddit | Facebook | X )

Getting to know OGC web services and GeoServer software

The course guides you in using GeoServer software to create geospatial web services, styles and publish them step by step simply and practically. Now, before delving into OGC web services, it is important to familiarize yourself with the various types of services.

In this session, we introduced you to the basics of the OGC web services and GeoServer software. If you want to access the complete tutorial, simply click on the link.

I would highly appreciate it if you could subscribe to my channel and share it with your friends to help spread this tutorial. By subscribing, you will gain complete access to the training video, which will enable you to enhance your skills. Moreover, sharing it with your friends guarantees that they can also benefit from this valuable resource. Thank you for your support.

What is Service?

A collection of operations, accessible through an interface, that allows a user to invoke a behavior of value to the user.

What are Web Services?

Web services are internet-based applications that can perform a wide range of functions, from simple tasks to complex business processes.

What are GeoSpatial Web Services?

GeoSpatial web services are online platforms that offer access to and analyze geographical information. They aim to overcome the lack of compatibility between different geospatial systems.

Why do you need standard web services?

Standard web services provide a common platform for communication between modern-day business applications that use different programming languages. This enables convenient interaction regardless of development language.

What is OGC?

The Open Geospatial Consortium (OGC) is an international organization that promotes the use of open standards to make geospatial information and services to be “FAIR”, which stands for Findable, Accessible, Interoperable, and Reusable. This goal applies to various areas such as data sharing, data processing, sensor web, and the Internet of Things.

What are OGC Web Services?

OGC Web Services (OWS) are a set of standards that allow for seamless integration of various online geoprocessing and location services. With OWS, users can access and utilize services such as the Web Map Service (WMS), Web Feature Service (WFS), Web Coverage Service (WCS), and Web Map Tile Service (WMTS).

WMS enables users to retrieve and obtain detailed information on maps of geospatial data. WFS allows for data manipulation operations on geographic features, including querying, creating, modifying, and deleting features. WCS provides access to raster datasets like elevation models and remote sensing imagery. WMTS serves pre-rendered or computed map tiles over the internet.

These services provide an interoperable framework for accessing, integrating, analyzing, and visualizing online geodata sources, sensor-derived information, and geoprocessing capabilities.

What is GeoServer?

GeoServer is a Java-based server that allows users to view and edit geospatial data. Using open standards set forth by the Open Geospatial Consortium (OGC), GeoServer allows for great flexibility in map creation and data sharing.

Open and Share Your Spatial Data

GeoServer is a powerful open-source tool for displaying spatial information through maps in various formats. The tool integrates OpenLayers, a free mapping library, for easy and quick map generation. Moreover, It supports standards like WMS, WFS, WCS, and WMTS, enabling data sharing, editing, and easy integration with web and mobile applications. With modular functionality and extensions, GeoServer offers extensive processing options. For example, the Web Processing Service (WPS) extension provides a wide range of processing options, and users can even create their extensions.

Use Free and Open Source Software

GeoServer is a free and open-source software that brings down the financial barrier to using GIS products. It is released every six months with new features, bug fixes, and improvements, providing a quick turnaround time. This transparent process often leads to faster advancements compared to closed software solutions. By using GeoServer, organizations can avoid software lock-in and save money on support contracts in the future.

Integrate With Mapping APIs

GeoServer is a versatile software that can integrate with popular mapping applications like Google Maps and Microsoft Bing Maps. It can also connect with traditional GIS architectures such as ESRI ArcGIS. OpenLayers and Leaflet are recommended as complementary tools to GeoServer for web mapping needs.

Join the Community

GeoServer has an active global community of users and developers, offering support through email lists. The software has a fixed release cycle and public issue tracker, ensuring transparency and regular updates. Commercial support is also available. Overall, using GeoServer means being part of a supportive community.

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

This is a stable release of GeoServer recommended for production use. GeoServer 2.24.0 is made in conjunction with GeoTools 30.0, mapfish-print-v2 2.3.0 and GeoWebCache 1.24.0.

Thanks to Peter Smythe (AfriGIS) and Jody Garnett (GeoCat) for making this release.

Thanks to everyone who helped test the release candidate: JP Motaung & Nicolas Kemp, Georg Weickelt, Peter Smythe, Tobia Di Pisa, and Giovanni Allegri.

We would like to thank our 2023 sponsors North River Geographic Systems Inc and How 2 Map for their financial assistance.

Keeping GeoServer sustainable requires a long term community commitment. If you were unable to contribute time testing the release candidate, sponsorship options are available via OSGeo.

Upgrade Notes

GeoServer strives to maintain backwards compatibility allowing for a smooth upgrade experience.

We have one minor change to share in this release:

• URL Checks: The url check security setting is now enabled by default.

  In GeoServer 2.22.5 and 2.23.2 this setting was available for use, but was turned off by default. If you are not yet in a position to upgrade to 2.24.0 you may wish to enable the recommended setting.

Security Considerations

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

• CVE-2023-43795 WPS Server Side Request Forgery
• CVE-2023-41339 Unsecured WMS dynamic styling sld=url parameter affords blind unauthenticated SSRF
• CVE-2023-51445 Stored Cross-Site Scripting (XSS) vulnerability in REST Resources API (Moderate).

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

IAU authority support and EPSG assumption removal

The new gs-iau extension module provides support for planetary CRSs, sourced from the International Astronomical Union. This allows users to manage GIS data over the Moon, Mars, or even the Sun, with well known, officially supported codes.

In addition to that, many bug fixes occurred in the management of CRSs and their text representations (plain codes, URL, URIs) so that the EPSG authority is no longer assumed to be the only possibility, in a variety of places, such as, for example, GML output. The code base has seen this assumption for twenty long years already, and while we made a good effort to eliminate the assumption, it could be still lurking in some places. Please test and let us know.

To learn more about this extension please visit the user-guide documentation. Thanks to Andrea Aime (GeoSolutions) for working on this activity.

• GSIP-219 - Multiple CRS authority support, planetary CRS
• GEOS-11075 IAU authority : planetary CRS support
• GEOS-11001 Support other CRS authorities in WFS
• GEOS-11002 Support other CRS authorities in WMS
• GEOS-11056 Support other CRS authorities in WCS
• GEOS-11064 Support other CRS authorities in WPS
• GEOS-11066 Support other CRS authorities in importer
• GEOS-11076 SRSList should show authorities other than EPSG, if available
• GEOS-10970 CatalogBuilder cannot handle CRS in authorities other than EPSG
• GEOS-10971 XStreamPersister cannot save CRS references using authorities other than EPSG
• GEOS-10972 Resource page CRS editors would not work with authorities other than EPSG

GeoServer Printing Extension Updates

The printing extension has seen big changes - with a host of new functionality developed by GeoSolutions over the years. With this update the printing module can now be used out-of-the-box by GeoNode and MapStore (no more customization required).

This update covers the release of MapFish Print 2.3.0 (and restores website user-guide).

GeoServer documentation has been updated with configuration options covering the new functionality.

• Max number of columns configuration for multi column legends
• Simple colored box icon in legends
• Explicit support of GeoServer CQL_FILTER parameter (also with layers merge support): wiki
• Legend fitting
• Don’t break legend items
• Reorder legends block in columns
• Images content
• Dynamic images page
• Multipage legends
• Custom intervals in ScalebarBlock
• Clustering Support wiki
• HTML rendering in text blocks
• Extra Pages
• Group Rendering in attribute blocks
• Skip rendering of pages
• Automatic X-Forwarded-For
• Parsing of Base64 encoded images

Thanks to GeoSolutions for adding functionality to mapfish-print for the GeoNode project. Shout out to Tobia Di Pisa and Giovanni Allegra for integration testing. Jody Garnett (GeoCat) was responsible for updating the mapfish print-lib for Java 11 and gathering up the functionality from different branches and forks. And integrating the updated configuration instructions with the GeoServer User Guide.

• GEOS-11159 Update mapfish-print-lib 2.3.0

New Security > URL Checks page

The previous 2.23 series added a new Check URL facility under the Security menu, but it was turned off by default, for backwards compatibility reasons. This functionality allows administrators to manage OGC Service use of external resources.

This has been included in GeoServer 2.22.x and 2.23.x series for backwards compatibility.

Backwards compatibility note:: This functionality is turned ON by default from GeoServer 2.24.0 onwards.

For information and examples on how to use the URL Check page, visit user guide documentation.

• GSIP 218 - Control remote HTTP requests sent by GeoTools \ GeoServer
• GEOS-10949 Control remote resources accessed by GeoServer
• GEOS-11048 Improve URL checking

Project Updates

Updated Security Policy

This release follows a revised security policy. Our existing “responsible disclosure policy” has been renamed, the practice is now called “coordinated vulnerability disclosure.” Last year we enabled GitHub private vulnerability reporting, we will now use these facilities to issue CVE numbers.

Coordinated vulnerability disclosure

Disclosure policy:

1. The reported vulnerability has been verified by working with the geoserver-security list
2. GitHub security advisory is used to reserve a CVE number
3. A fix or documentation clarification is accepted and backported to both the “stable” and “maintenance” branches
4. A fix is included for the “stable” and “maintenance” downloads (released as scheduled, or issued via emergency update)
5. The CVE vulnerability is published with mitigation and patch instructions

This represents a balance between transparency and participation that does not overwhelm participants. Those seeking greater visibility are encouraged to volunteer with the geoserver-security list; or work with one of the commercial support providers who participate on behalf of their customers.

This change has already resulted in improved interaction with security researchers.

Thanks to Jody Garnett (GeoCat) for this proposal on behalf of GeoCat Live customers.

• GSIP 220
• SECURITY.md

Developer updates

Internal refactor to remove “org.opengis” package usage

The GeoTools project moved away from using the org.opengis package after complaints from OGC GeoAPI working group representatives, using the same package name. Interfaces have been moved to the org.geotool.api package, along with some general clean up.

While this does not affect GeoServer users directly, it’s of consequence for those that have installations with custom, home grown plugins that might have to be migrated as a consequence. For those, the GeoTools project offers a migration guide, along with a refactoring script that might perform the migration for you, or else, get you close to a working point. GeoServer itself has been migrated using these scripts, with minimal manual intervention.

For more details, and access to the migration script, please see the GeoTools 30 upgrade guide.

Thanks to Jody Garnett (GeoCat), Andrea Aime (GeoSolutions), and Ian Turton (ASTUN Technologies) for all the hard work on this activity. We would also like to thank the Open Source Geospatial Foundation for setting up a cross-project activity and financial support to address this requested change.

• GEOS-11070 Upgrading to GeoTools 30.x series, refactor to org.geotools.api interfaces

Community modules updates

While not strictly part of this release, it’s interesting to know about some community module advances that can be found only in the the 2.24.x series.

Two extensions are no longer actively supported and are now available as community modules:

• GEOS-10960 Downgrade imagemap module to community
• GEOS-10961 Downgrade xslt extension to community

The following community modules have been removed (due to lack of interest):

• GEOS-10962 Remove wms-eo community module
• GEOS-10963 Remove SAML community module
• GEOS-10966 Remove importer-fgdb community module
• GEOS-10967 Remove teradata community module
• GEOS-10977 Remove wmts-styles community module
• GEOS-10978 Remove nsg-wmts community module
• GEOS-10984 Remove ows-simulate community module

OGC API community modules continues to improve

The OGC API community module keeps improving. In particular, thanks to the GeoNovum sponsorship, GeoSolutions made the OGC API Features module pass the OGC CITE compliance tests, for the “core” and “CRS by reference” conformance classes. Along with this work, other significant changes occurred:

• Made the API version number appear in the service path, easing future upgrades
• Support for configurable links, required to get INSPIRE download service compliance.

In addition to that, the new “search” experimental conformance class allows to POST complex searches against collections, as a JSON document, in a way similar to the STAC API.

Those interested in this work are encouraged to contact Andrea Aime (GeoSolutions).

• GEOS-10924 Support JSON-FG draft encoding in OGC API - Features
• GEOS-11045 Implement proposal “OGC API - Features - Part n: Query by IDs”
• GEOS-10882 Add an option to remove trailing slash match in OGC APIs
• GEOS-10887 Add angle brackets to OGC API CRS Header
• GEOS-10892 Allow configuring custom links for OGC API “collections” and single collection resources
• GEOS-10895 Make OGC API CITE compliant even if the trailing slash is disabled: landing page exception
• GEOS-11058 Support other CRS authorities in OGC APIs
• GEOS-10909 Don’t link from OGC API Features to WFS 2.0 DescribeFeatureType output, if WFS is disabled
• GEOS-10954 Split ogcapi community module package into single functionality packages

DataDir Catalogue loader

For folks working with very large catalogues some improvement from cloud native geoserver are now available to reduce startup time.

Thanks to Gabriel Roldan for folding this improvement into a community module for the rest of the GeoServer community to enjoy.

• GEOS-11049 Community module “datadir catalog loader”

GeoServer Access Control List Project

The GeoServer Access Control List project is an independent application service that manages access rules, and a GeoServer plugin that requests authorization limits on a per-request basis.

Gabriel Roldan is the contact point for anyone interested in this work.

• GSIP 217 - GeoServer ACL project

The vector mosaic and FlatGeoBuf modules sport significant performance improvements

FlatGeoBuf is a “performant binary encoding for geographic data”, a single file format that also manages to be cloud native and include a spatial index. GeoServer provides access to this format thought the WFS FlatGeobuf output format, which not only can write the format, but also read it as a standard data store.

The Vector Mosaic datastore supports creation of mosaics made of single file vector data, useful in situations where the access to data is targeted to sub-pages of a larger data set (e.g., data for a single time, or a single customer, or a single data collect, out of a very large uniform set of vectors) and the database storage for it has become either too slow, or too expensive.

These two modules make a great combo for those in need to handle very large vector datasets, by storing the FlatGeoBuf on cheap storage.

In particular, the FlatGeoBuf module saw speed improvements that made it the new “fastest vector format” for cases where one needs to display a large data set, all at once, on screen (PostGIS remains the king of the hill for anything that needs sophisticated filtering instead).

For reference, we have timed rendering 4 million tiny polygons out of a precision farming collect, using a 7 classes quantile based SLDs. Here is a tiny excerpt of the map:

And here are the timings to render the full set of polygons, putting them all on screen, at the same time, with a single GetMap request:

• PostGIS, 113 seconds
• Shapefile, 41 seconds
• Flatgeobuf, 36 seconds

The tuning is not complete, more optimizations are possible. Interested? Andrea Aime is the contact point for this work.

Release notes

(Including the changes made in 2.24-RC, the release candidate)

Improvement:

• GEOS-11114 Improve extensibility in Pre-Authentication scenarios
• GEOS-11130 Sort parent role dropdown in Add a new role
• GEOS-11142 Add mime type mapping for yaml files
• GEOS-11148 Update response headers for the Resources REST API
• GEOS-11149 Update response headers for the Style Publisher
• GEOS-10926 Community Module Proxy-Base-Ext
• GEOS-10934 CSW does not show title/abstract on welcome page
• GEOS-10973 DWITHIN delegation to mongoDB
• GEOS-10999 Make GeoServer KML module rely on HSQLDB instead of H2
• GEOS-11005 Make sure H2 dependencies are included in the packages of optional modules that still need it
• GEOS-11059 Map preview should not assume EPSG authority
• GEOS-11081 Add option to disable GetFeatureInfo transforming raster layers
• GEOS-11087 Fix IsolatedCatalogFacade unnecessary performance overhead
• GEOS-11090 Use Catalog streaming API in WorkspacePage
• GEOS-11099 ElasticSearch DataStore Documentation Update for RESPONSE_BUFFER_LIMIT
• GEOS-11100 Add opacity parameter to the layer definitions in WPS-Download download maps
• GEOS-11102 Allow configuration of the CSV date format
• GEOS-11116 GetMap/GetFeatureInfo with groups and view params can with mismatched layers/params

Bug:

• GEOS-11138 Jetty unable to start cvc-elt.1.a / org.xml.sax.SAXParseException
• GEOS-11140 WPS download can leak image references in the RasterCleaner
• GEOS-11145 The GUI “wait spinner” is not visible any longer
• GEOS-8162 CSV Data store does not support relative store paths
• GEOS-10452 Use of Active Directory authorisation seems broken since 2.15.2 (LDAP still works)
• GEOS-10874 Log4J: Windows binary zip release file with log4j-1.2.14.jar
• GEOS-10875 Disk Quota JDBC password shown in plaintext
• GEOS-10899 Features template escapes twice HTML produced outputs
• GEOS-10903 WMS filtering with Filter 2.0 fails
• GEOS-10921 Double escaping of HTML with enabled features-templating
• GEOS-10922 Features templating exception on text/plain format
• GEOS-10928 Draft JSON-FG Implementation for OGC API - Features
• GEOS-10936 YSLD and OGC API modules are incompatible
• GEOS-10937 JSON-FG reprojected output should respect authority axis order
• GEOS-10958 Update Spotbugs to 4.7.3
• GEOS-10981 Slow CSW GetRecords requests with JDBC Configuration
• GEOS-10985 Backup Restore of GeoServer catalog is broken with GeoServer 2.23.0 and StAXSource
• GEOS-10993 Disabled resources can cause incorrect CSW GetRecords response
• GEOS-11015 geopackage wfs output builds up tmp files over time
• GEOS-11016 Docker nightly builds use outdated GeoServer war
• GEOS-11033 WCS DescribeCoverage ReferencedEnvelope with null crs
• GEOS-11060 charts and mssql extension zips are missing the extension

Task:

• GEOS-11134 Feedback on download bundles: README, RUNNING, GPL html files
• GEOS-11141 production consideration for logging configuration hardening
• GEOS-11091 Upgrade spring-security to 5.7.10
• GEOS-11094 Bump org.hsqldb:hsqldb:2.7.1 to 2.7.2
• GEOS-11103 Upgrade Hazelcast version to 5.3.x
• GEOS-10248 WPSInitializer NPE failure during GeoServer reload
• GEOS-10904 Bump jettison from 1.5.3 to 1.5.4
• GEOS-10907 Update spring.version from 5.3.25 to 5.3.26
• GEOS-10941 Update ErrorProne to 2.18
• GEOS-10987 Bump xalan:xalan and xalan:serializer from 2.7.2 to 2.7.3
• GEOS-10988 Update spring.version from 5.3.26 to 5.3.27 and spring-integration.version from 5.5.17 to 5.5.18
• GEOS-11010 Upgrade guava from 30.1 to 32.0.0
• GEOS-11011 Upgrade postgresql from 42.4.3 to 42.6.0
• GEOS-11012 Upgrade commons-collections4 from 4.2 to 4.4
• GEOS-11018 Upgrade commons-lang3 from 3.8.1 to 3.12.0
• GEOS-11019 Upgrade commons-io from 2.8.0 to 2.12.0
• GEOS-11020 Add test scope to mockito-core dependency
• GEOS-11062 Upgrade httpclient from 4.5.13 to 4.5.14
• GEOS-11063 Upgrade httpcore from 4.4.10 to 4.4.16
• GEOS-11067 Upgrade wiremock to 2.35.0
• GEOS-11080 Remove ASCII grid output format from WCS
• GEOS-11084 Update text field css styling to look visually distinct
• GEOS-11092 acme-ldap.jar is compiled with Java 8

For the complete list see 2.24.0 release notes.

About GeoServer 2.24 Series

Additional information on GeoServer 2.24 series:

• GeoServer 2.24 User Manual
• Control remote HTTP requests sent by GeoTools/GeoServer
• Multiple CRS authority support, planetary CRS
• Extensive GeoServer Printing improvements
• Upgraded security policy

Release notes: ( 2.24.0 | 2.24-RC )