Skip to content

v2026.03.00

Latest

Choose a tag to compare

@github-actions github-actions released this 04 Nov 11:07
· 10 commits to refs/heads/2026.03.xx since this release

Main Features

  • Multi-view Identify with External Data and Media Rendering (#12594) (thanks to Publiacqua) The Identify tool can now show several views for the same WMS or WFS layer, instead of a single feature info template. Views are configured from the layer settings and appear as tabs in the Identify panel, and each one can use any of the existing formats (TEXT, HTML, PROPERTIES, TEMPLATE) (#12595). A new External Data view type fetches related records from a different WFS source, using a CQL filter built from the attributes of the clicked feature, so users can see data that lives outside the layer they clicked on (#12596). Attributes in External Data and PROPERTIES views can be rendered as rich media: images, videos, audio, panoramas, PDF documents, links and embedded pages (#12597, #12598). The media type can be read from an attribute, also using a custom vocabulary configured for the instance (#12871), and GeoNode document layers use the same media rendering (#12837).

  • Coalesce Adjacent WMS Layers into a Single Request (#12662) (thanks to Total Energies) Adjacent WMS layers served by the same endpoint can now be drawn with one GetMap request, listing all layers and styles together, instead of one request per layer. This reduces the number of HTTP requests and tiles and lets the server compose the image, which helps a lot on maps with many thematic layers from the same WMS server. The option is off by default and can be enabled for the whole map or per layer. Identify, legend, TOC and layer settings keep working on each single layer as before. Loading events have also been batched and deduplicated on OpenLayers and CesiumJS, cutting redundant state updates and re-renders on maps with many layers (#12869).

  • Map-level Filter Widget and Dynamic Filter Enhancements (#12466) (thanks to Total Energies) The dynamic filter introduced in the previous release grows into a complete tool for maps. Maps now have a widget holder like dashboards, which hosts a map-level Filter widget able to filter any layer of the map. Filters can be collapsed to a compact view, can carry a short description shown as a tooltip, and can be set to start expanded or collapsed. The widget lists the layers it is connected to (#12649), can zoom to the filtered features of a layer (#12650), and the active filter widget is highlighted in the widget tray (#12738). The TOC now tells apart filters applied by a widget from the global layer filter (#12734).

  • GeoNode Catalog: Maps and Documents (#12511) (thanks to Total Energies) The GeoNode catalog service, added in the previous release, now also lists documents and maps, and the resource types to show can be chosen in the advanced settings of the service. Selected documents are added together as a single vector layer, with one point for each document (#12509). Adding a GeoNode map imports all its layers into the current map, keeping the original group structure and order under a new group named after the map, while background layers are left out. Datasets, documents and maps can be selected and added together in one go.

  • List Layout for the Resources Catalog (#12826) (thanks to CNR-ISMAR) The Resources Catalog gets a new List layout that shows each resource as a full-width card with its information laid out horizontally, next to the existing Grid and Table layouts (the old list layout is now called table). The metadata configuration of the cards also supports arrays, nested items, links and separators, so richer resource details can be shown without custom code.

  • Privacy Settings and Consent Management (#13038) The single cookie notice is replaced by a privacy panel shared by the home page, maps, dashboards, geostories and embedded resources. It separates necessary tools from optional functional, statistics and marketing tools, keeps optional tools off until the user agrees, and lets users accept, refuse or change their choice at any time from the footer. Projects can register their own optional integrations so they start only after consent.

  • Settings in the Context Wizard (#12889) (thanks to Municipality of Genoa) The Settings plugin can now be added and configured in the plugin step of the context creation wizard.

Main Improvements

  • Identify Parameters Configurable from the UI (#12593) (thanks to Municipality of Florence) The number of features returned by a WMS GetFeatureInfo request (still 10 by default) and the GeoServer buffer vendor parameter can now be set both from the catalog and from the layer settings. The buffer option is shown only when the server type is GeoServer.

  • Separate WFS Search Service and Editable Layer URLs (#12573) (thanks to @tha-nordiq) A WMS layer can now point to a WFS search service with a type name different from the WMS layer name. The WFS service is used by filters, attribute table and other tools, so layers where names differ between the two services now work as expected. The service URL and the type name can be edited from the layer settings (#12571).

  • Title and Name in the General Tab (#12774) (thanks to Municipality of Genoa) The General tab of layer settings now shows and lets users edit the layer name also for WFS and ArcGIS layers, not only for WMS layers.

  • Multiple Embedded Maps in One Page (#12872) (thanks to @tha-nordiq) The map container id is now configurable, a first step to host more than one MapStore map in the same page with the embedding API.

  • COG Layers Out of Experimental (#12815) Cloud Optimized GeoTIFF layers are no longer flagged as experimental and are now available by default among the catalog service types.

  • App Version Visible Only to Administrators (#13019) By default, the MapStore version shown in the About panel is now visible only to administrators, so the exact version of an installation is not exposed to every visitor.

Dependency Updates

  • Spring Framework 7 and Spring Security 7 (thanks to Halliburton): the backend moves to Spring Framework 7.0.9 and Spring Security 7.1.1, on Jakarta EE (Jakarta Servlet 6) (#12025, #13020). OpenID Connect support has been ported to Spring Security 7 (#12331) and the LDAP profile has been aligned with the new configuration (#12728).
  • Backend libraries: Jackson updated to 2.22.3 (#12867, #12943, #13046) and Log4j API to 2.26.1 (#12799).
  • Frontend libraries: react-dom updated to 16.14.0 (#12764), react-dock to 0.8.0 (#12766), react-checkbox-tree to 2.0.2 (#12756) and qrcode.react to 4.2.0 (#12758). The unused eventlistener (#12745) and react-contenteditable (#12760) dependencies have been removed, and legacy React lifecycle methods have been renamed to their UNSAFE_ versions to prepare future React upgrades (#12502).
  • Routine updates of frontend, backend and documentation dependencies, including axios 0.34.0, moment 2.31.0, simple-git 4.0.2, Babel, PostCSS, immutable, json-2-csv, webpack-dev-server, MkDocs Material and WeasyPrint.

System Updates

  • JDK 17 is now the minimum supported Java version for MapStore, GeoStore and http-proxy (#12449).
  • Tomcat 11 (11.0.25) is now the reference Servlet container (#13081).
  • Node.js 22 is now the minimum version to build the frontend, and Node.js 24 is the recommended one (#13100).
  • The standalone binary package is no longer distributed starting from this release (#12923): use the WAR or the Docker image instead.
  • The Docker image is now built and tested in CI on every change (#12963). Release workflows keep the project template aligned with the released backend version (#13044), and the backport action has been made more reliable (#12809).
  • References to the old geo-solutions.it domains have been replaced with geosolutionsgroup.com across the codebase (#12934).
  • Documentation and translations: the User Guide covers all the new features of this release, the proxy and OpenID Connect documentation have been improved (#13108, #13114), and translations have been updated for Danish, Dutch (thanks to @oskarbh7 and @tibovanheule) and Italian.

Projects and custom backend code need to be updated for this release: read the migration guide (#12406) and the reviewed developer guide (#12560) before upgrading.

Useful links related to v2026.03.00