Changelog for QGIS 4.4

Release date: 15 November, 2026

QGIS (https://qgis.org) is the world's most popular (open source) desktop Geographical Information System (GIS). It is used by people around the world to view, edit, analyse, and share spatial data. It can produce professional-grade cartography products and supports hundreds of spatial data formats. QGIS is a member project of OSGEO, the Open Source Geospatial Foundation that is democratising access to spatial platforms (https://osgeo.org).

We are pleased to announce the new major release of QGIS 4.4, which builds on the solid foundation of the Major Version 4.0 update that transitioned the core of QGIS onto the modern Qt6 framework. This release is the Long Term Release (LTR) Candidate - the final LTR release will happen after 4 bug-fix rounds to stabilise this release and make it ready for a further year of stable support by the QGIS Community.

For a whirlwind tour of all the new functionalities introduced in this release, you can view the highlight reel video on YouTube.

QGIS is a community effort, and we would like to extend a big thank-you to the developers, documenters, testers, and the many folks out there who volunteer their time and effort (or fund others to do so) to make these releases possible. From the QGIS community, we hope you enjoy this release!

If you wish to donate time, money, or otherwise contribute towards making QGIS more awesome, please wander along to QGIS.ORG and lend a hand!

QGIS is supported by donors and sustaining members. A current list of donors who have made financial contributions, large or small, to the project can be seen on our list of donors. If you would like to become an official project sustaining member, please visit our sustaining member page for more details. Sponsoring QGIS helps us to fund our regular developer meetings, maintain project infrastructure, and fund bug-fixing efforts. A complete list of current sponsors is provided below - our very big thank you to all of our sponsors!

QGIS is free software, and you are under no obligation to pay anything to use it - in fact, we want to encourage people far and wide to use it regardless of their financial or social status - we believe that empowering people with spatial decision-making tools will result in a better society for all of humanity.


QGIS Server


Feature: Expose JSON-FG and time to QGIS server OAPIF

Expose JSON-FG and JSON-FG-PLUS (and RFC7946) as profiles for OGCAPI for features.

Also expose "time" dimension as in the specifications:
https://docs.ogc.org/is/21-045r1/21-045r1.html#time
https://docs.ogc.org/is/23-058r2/23-058r2.html#_primary_temporal_information

This work is the result of a collective funding effort from:
QGIS Anwendergruppe Deutschland e.V. (QGIS-DE e.V.)
Gis3W
QTIBIA
Oslandia

This feature was developed by Alessandro Pasotti

Original PR: #66762


Feature: QEP 414 - Various enhancements including feature schema

In support of the QGIS Server OAPIF JSON-FG and FlatGeobuf format implementations from QEP 414 new changes to the OGC API include:

  • schema (including x-ogc-role , format and type for main widgets)
  • references (from RelationReference and ValueRelation)
  • profiles (for references)
  • full crs support in requests and responses (includes storageCrs and storageCrsCoordinateEpoch if available)
  • extra geometry columns support (Postgres), exposed as WKT (transformed to the requested CRS)
  • codelist for enums and ValueMap
  • new conformance classes

This feature was funded by Geogirafe user group / OPENGIS.ch

This feature was developed by Alessandro Pasotti

Original PR: #66495


Feature: Support "default" value for Time dimension in WMS GetCapabilities

default parameter is part of the Dimension GetCapabilities tag. It serves to indicate default value that will be used if a GetMap request does not specify a value. As with vector layers you can choose the default display to be either the minimum or maximum value, a reference value to be set, or "all values" which is the current situation where no default value is written.
default
Implementation detail
We reuse WmsDimensionInfo for group because we can imagine later having other dimension configuration for group and to stay consistent with vector layer. At the moment, it's possible to have only a "TIME" dimension for groups.

This feature was funded by Ressources Naturelles Canada

This feature was developed by Julien Cabieces

Original PR: #67343