Changelog for QGIS 3.16¶

Feature: Ability to export temporal animation frames¶

Allows exporting of temporal animation frames to successive images, for later stitching together in an external application. Users have precise control over the image size and map extent.

This feature was developed by Nyall Dawson

Feature: Go-To locator¶

We have added a new goto locator filter.

The goto indicator takes in the following strings:

• A pair of x and y coordinates (separated by a comma or space).
• An OSM, Leaflet, or OpenLayers formatted URL.
• A Google maps URL.

The logic of the XY string is as follows:

• If the canvas CRS isn’t WGS84:
  • If the coordinate fits within WGS84 bounds, add a WGS84 result (this is weighted to have higher priority than the canvas CRS result below).
  • If the coordinate fits within the canvas CRS bounds, add a canvas CRS result.
• If the canvas CRS is WGS84:
  • If the coordinate fits within the WGS84 bounds, add a WGS84 result.

This feature was developed by Mathieu Pellerin

Feature: Expose option to offset simple line dash patterns by a preset amount¶

Allows for tweaking the positioning of dashes/spaces in the line, so that the dashes/spaces can be placed at nicer positions to account for corners in the line (also can be used potentially to “align” adjacent dash pattern borders).

The offset can be set in various units, including map units, and can also be data defined.

This feature was funded by Kanton Solothurn

This feature was developed by Nyall Dawson

Feature: Add options to dynamically tweak dash pattern in simple line symbol layers¶

Options have been added to allow the tweaking of dash patterns to allow more control for improving the rendered quality of line symbols. These options include:

• Align dash pattern to line length: If checked, the dash pattern lengths will be subtly adjusted in order to ensure that when a line is rendered it will end with a complete dash element, instead of a gap element or partial dash element.
• Tweak dash pattern at sharp corners: If checked, this option dynamically adjusts the dash pattern placement so that sharp corners are represented by a full dash element coming into and out of the sharp corner. It’s designed to better represent the underlying geometry while rendering dashed lines, especially for jagged lines.

The following images illustrate the “Align dash pattern to line length” change in action, with yellow lines indicating the true start and end position of the line features being symbolised.

Before:

After:

This feature was funded by Kanton Solothurn

This feature was developed by Nyall Dawson

Feature: Manage 3D symbols through style manager¶

Support has been added for managing 3D symbols through the QGIS style manager, including support for importing and exporting libraries of 3d symbols, and completes the recent work in fully abstracting out 3D symbols and their widget handlers.

Unfortunately, there are no thumbnails generated for 3D symbols in the library, and a generic icon is used for all 3D symbols for the time being. Generating thumbnails is no trivial matter, so it has been deferred for the time being.

This feature addresses the issue raised in 31479.

This feature was developed by Nyall Dawson

Feature: Control anchor point for line labels¶

A new option is exposed which allows users to control whether the anchor point for the labeling of line features is a hint or a strict requirement. The resulting behavior modifications include the following:

• Strict: Labels are placed exactly on the label anchor only, and no other fallback placements are permitted.
• Hint: The label anchor is treated as a hint for the preferred label placement, but other placements close to the anchor point are permitted.

This feature was developed by Nyall Dawson

Feature: Render axis for stacked bar diagram¶

This adds support for rendering the axis on stacked bar diagrams if an axis has been set. The implementation is based on the axis rendering for the histogram diagram.

Negative values are not handled properly by stacked bar diagrams with or without the axis being displayed.

Addresses Issue 34915

This feature was developed by Dan Minor

Feature: In-memory mesh datasets with persistence¶

This feature introduces the ability to create in-memory dataset groups for mesh layers. These dataset groups are temporary and are not kept once the project is closed.

A new option has been added to the mesh calculator which allows the creation of in-memory dataset groups.

This feature also introduces the ability to remove or save these memory dataset groups to a file with the specified driver.

This feature was developed by Vincent Cloarec

Feature: Multi identify for mesh layer¶

The identify tool has been adapted when used on mesh layers and now displays the dataset value corresponding to the current time of the temporal controller for all dataset groups. The active dataset groups (scalar and eventually vector) are first displayed, then the other dataset groups. There is also other information displayed, including:

• Source where the dataset is stored
• Time step of the dataset that is displayed (can be different than the time of the temporal controller). Displays nothing if the dataset group is not temporal
• Centroid of the corresponding face
• Coordinate of the snapped vertex (if one is snapped)
• Center of the snapped edge (if one is snapped)

When the map canvas does not have temporal navigation enabled, the identify results contain only information about the active dataset groups which have static datasets defined in the mesh properties dialog.

This feature was developed by Vincent Cloarec

Feature: Virtual dataset groups for mesh layer¶

The ability to use “virtual” data set groups has been introduced for mesh layers. This replaces the “memory” dataset group used in 37389.

With the mesh calculator, users may choose to create those “virtual” dataset groups that will be added to the layer. Values are not stored in memory but each dataset is rather calculated when needed with the formula entered in the mesh calculator.

Those virtual dataset groups are saved within the project and be removed or saved to file for persistence.

Persistent and virtual dataset groups are distinguished in the source tab of the mesh layer properties by changes in the color of the background for each item, indicated as follows:

Persistent: yellow

Virtual: purple

This feature was developed by Vincent Cloarec

Feature: Add export to QgsMesh method¶

A method has been added to export a triangulation to a QgsMesh instance, with the possibility to construct mesh layer with triangulation from existing points and lines. This is the first step to allow the ability to obtain a QgsMesh from other map layers.

The Triangulation and DualEdgeTriangulation classes were also renamed and refactored to make them more consistent with QGIS code.

• Add a method to export the triangulation to a QgsMesh instance.

This feature was developed by Vincent Cloarec

Feature: TIN Mesh creation¶

TIN mesh layers can be created from vector layer data (vertices and/ or break lines). The resulting mesh is constructed with a constrained Delaunay triangulation. This mesh layer can be created using the python API or through an algorithm in the processing tool box.

This feature was developed by Vincent Cloarec

Feature: Gamma correction filter for raster layers¶

Add gamma correction filter pipe for raster layers in addition to the existing brightness, contrast, hue, and saturation filters. Users can adjust the gamma value from the layer properties dialog, using styling panel and/or new buttons on the Raster toolbar. Default gamma value is 1.0 and it can be adjusted within the range 0.1 to 10.

Addresses Issue 13512

Also adds a rendering test for brightness and contrast filter which has no test at all and fixes some deprecation warnings in the Python test for QgsRasterLayer.

This feature was developed by Alexander Bruy

Feature: Allow 3D material texture files to be embedded in style/project¶

Some minor API and code cleanups were performed, as well as introducing the use of QgsImageCache for 3D texture files in order to allow them to be embedded within projects.

This feature was developed by Nyall Dawson

Feature: Directional lighting support for QGIS 3D¶

Added directional lights to QGIS 3D

• Now the user can add directional lights to the 3D views.
• I added a tab widget under the lights section of the 3D configuration dialog.
• The user can specify the direction of the light, its color and intensity.
• This is just a duplication of the already existing point lights implementation with some changes.
• Later it may be useful to add a way to visualize the light direction by displaying a mesh that is positioned at camera’s view point like an arrow that displays how the sun lights the scene for example.

This feature was developed by Nedjima Belgacem

Feature: Texturing support for vector layer¶

Texturing support has been added for QGIS 3D with the following new functionalities:

• Users can now select an image to be displayed on the surfaces of buildings as diffuse map from the symbol properties.
• The user can also change the scale of textures from the symbol properties.

Some visual issues may appear when using textures. These issues relate to the normals of surfaces that you may be able to fix by checking “add back faces” and playing around with the invert normals and culling mode in the symbol properties.

This feature was developed by Nedjima Belgacem

Feature: Enable embedded and remote 3D models for 3D point symbols¶

Users can now utilise and embed remote 3D models for 3D point symbols.

This feature was developed by Mathieu Pellerin

Feature: Add option to show light source origins¶

A feature which allows users to toggle a visible sphere at light source origins in a 3D scene.

This allows for the easier repositioning and placement of light sources relative to the scene contents.

Addresses Issue #37726.

This feature was developed by Nyall Dawson

Feature: Improvements for material handling¶

Further improvements for material handling were introduced, and a Gooch shading model was added. This improves the QgsAbstractMaterialSettings API, by:

• Adding icon support for registered material types (for use in the material selector combo box).
• Adds support for handling different rendering techniques to QgsAbstractMaterialSettings. Now material classes can indicate which rendering techniques they support (e.g. Triangles, Lines, InstancedPoints, etc.), and the material is only offered when it’s compatible with the required technique.
• The technique handling in the gooch material widget was improved to avoid showing settings that have no effect in a particular context (e.g. hiding all but the ambient color choice for simple 2D line symbols).
• A new material, “Gooch”, was added. This material gives a CAD style 3D render, where the shading is not dependent on appropriate lighting setup in a scene and where the 3D details are always visible, regardless of the lighting choice.

This feature was developed by Nyall Dawson

Feature: Expose control over text format and alignment for individual cells in manual text tables¶

Adds control over setting the text format (e.g. bold/italic/buffer/shadow etc) and text alignment (horizontal and vertical) for the contents of individual cells in a manual text table.

This feature was funded by City of Canning

This feature was developed by Nyall Dawson

Feature: Use QgsTextRenderer to render attribute table text¶

Allows for the full range of text formatting options in layout attribute tables, including buffers, shadows, word spacing etc.

This feature was funded by City of Canning

This feature was developed by Nyall Dawson

Feature: Use QgsTextRenderer for drawing map grid text in layouts¶

Allows for grid annotations which use buffers, shadows, background shapes, etc.

This feature was developed by Nyall Dawson

Feature: Expose option to control PDF image compression method when exporting layouts to PDF¶

Options are for Lossy compression, which is the default JPEG compression used, and Lossless compression (which creates bigger files in most cases, but is much more suitable for professional printing outputs or for post-production in other products such as Illustrator etc)

The bad news is that this option is only available in builds based on Qt 5.13 or later.

This feature was developed by Nyall Dawson

Feature: Add automatic clipping settings for atlas maps¶

This feature allows users to enable map clipping for layout map items so that the maps are clipped to the boundary of the current atlas area feature.

Options exist for:

• Enabling or disabling the clipping on a per-map basis
• Specifying the clipping type:
  • “Clip During Render Only”: applies a painter based clip, so that portions of vector features which sit outside the atlas feature become invisible
  • “Clip Feature Before Render”: applies the clip before rendering features, so borders of features which fall partially outside the atlas feature will still be visible on the boundary of the atlas feature
  • “Render Intersecting Features Unchanged”: just renders all features which intersect the current atlas feature, but without clipping their geometry
• Controlling whether labels should be forced placed inside the atlas feature, or whether they may be placed outside the feature
• Restricting the clip to a subset of the layers in the project, so that only some are clipped

This feature was funded by City of Canning

This feature was developed by Nyall Dawson

Feature: Add API to QgsMapSettings for specifying clipping regions to apply while rendering maps¶

This is currently API only functionality, but functionality has been added which provide the backend capabilities to specify clipping regions which may be used during map render operations.

Although primarily introduced in order to provide functionality which allows the automatic clipping of map elements to the current atlas feature geometry in print layouts, the API has been deliberately implemented in a manner that’s very flexible to allow various use cases which require the clipping of regions during map render operations.

For non-vector layers, the clipping is applied through a QPainter clipping path. For vector layers, the API exposes various options in how the clipping should be applied:

1. As an “intersects” style test only: All vector features which intersect the path are rendered, without actually clipping the feature’s geometry
2. By modifying the feature’s geometry and clipping the geometry to the region: Any stroke or outline settings for the symbol will be rendered along the boundary of the clipping region, even if the feature actually partially falls outside this region.

or

1. Using a painter clip path: Features are clipped to the region, but only at painter time. Boundaries of the feature which fall outside the clip region will not be visible.

This feature was funded by City of Canning

This feature was developed by Nyall Dawson

Feature: Layout legend maximum marker size¶

Adds the possibility to enter the maximum marker size (in mm) to the layout legend widget.

In some cases, such as when point layers use a symbol size which is based on map units, the point markers on the layout legend can get quite big. This feature adds a setting to the layout legend widget which allows the restriction of the maximum marker symbol size while the automatic legend update is still active.

This feature was developed by mhugent

Feature: Allow cells in manual text tables to have expression based contents¶

Allows individual cells from a manual text table to take their contents from a preset expression. Expressions have access to the full layout item expression context, allowing cells to calculate and display metadata style values or aggregate based calculations.

This feature was funded by City of Canning

This feature was developed by Nyall Dawson

Feature: Clip layout maps to shape¶

New functionality was introduced which allows users to clip a map item to a shape or polygon item from their layout, allowing for non-rectangular maps within the layout.

This feature was developed by Nyall Dawson

Feature: Support for rotated ticks/annotation¶

Tick marks and annotations on a map frame in the print composer can now be rotated, allowing them to align with a rotated map frame as described in issue 36904. It works for both rotated maps and reprojected grids.

The following options have been added:

• Ticks:
  • Rotate ticks (if unchecked, ticks get drawn as before, not taking angle into account)
  • Rotated ticks alignment (whether ticks should have a constant length, or be aligned orthogonaly)
  • Skip low angled ticks (an angle threshold below which ticks aren’t drawn, so you can skip ticks for grid lines that are, for example, too close to being parallel with the map edge)
• Annotations:
  • Parallel to Tick (Next To/ Horizontal / Vertical Ascending / Vertical Descending)
  • Draw low angled (if checked, skipped ticks above will still get an annotation)

This feature was funded by Kanton Solothurn

This feature was developed by Olivier Dalang, OPENGIS.ch

Feature: Add page offset expression for Y positions¶

A layout_pageoffsets expression was added for print layouts which returns an array of Y coordinates for the top of each page in the layout. this allows users to dynamically position items on pages in a context where page sizes may change.

For example, to set an item at 2.5mm from the top of page 2 (for the data-defined position Y of a map item) : @layout_pageoffsets[1] + 2.5

This constitutes a workaround for Issue 37567.

This feature was funded by BikePlan

This feature was developed by Olivier Dalang, OPENGIS.ch

Feature: Add “main_angle” function to return the estimated main angle of a geometry¶

Returns the angle of the oriented minimum bounding box which covers the geometry value.

Useful for data defined overrides in the symbology of label expressions, e.g. to rotate labels to match the overall angle of a polygon, and similar for line pattern fill.

This feature was funded by Kanton Solothurn

This feature was developed by Nyall Dawson

Feature: Port refFunctions to core¶

Various overlay operations have been added to the expression engine. This covers the functionality of the refFunctions plugin.

The following new expression functions are implemented : overlay_intersects(layer[,expression][,filter][,limit][,cache]) overlay_contains(layer[,expression][,filter][,limit][,cache]) overlay_crosses(layer[,expression][,filter][,limit][,cache]) overlay_equals(layer[,expression][,filter][,limit][,cache]) overlay_touches(layer[,expression][,filter][,limit][,cache]) overlay_disjoint(layer[,expression][,filter][,limit][,cache]) overlay_within(layer[,expression][,filter][,limit][,cache]) overlay_nearest(layer[,expression][,filter][,limit][,max_distance][,cache])

in all instances, the spatial operator is evaluated against the other layer. If an expression is provided, it returns an array of results. If no expression is provided, it returns a boolean indicating whether or not there is a match for at least one feature. Features can optionally be filtered by an expression, and optionally be limited to a certain count.

The overlay_nearest function has an additional max_distance filter.

This feature was developed by Olivier Dalang, OPENGIS.ch

Feature: Add option to calculate bearing based on travel direction¶

For devices which report faulty bearing measurements, this option can be used to instead calculate the GPS bearing based on the previous two recorded locations.

This feature was developed by Nyall Dawson

Feature: Digitizing and splitting curved features¶

New functionality was introduced that adds the possibility to switch between linear or circular strings when digitizing or splitting vector layer features.

The user can use the keyboard shortcut Ctrl+Shift+G to switch between linear/circular.

For splitting features, new overloading methods have been added to the API. When splitting, curves are preserved. For this, the curve is segmentized before splitting, and all the split features are “de-segmentized” after splitting.

A toolbar button was added to enable switching between linear/circular:

This feature was developed by Vincent Cloarec

Feature: Rescale raster algorithm for Processing¶

Adds a rescale raster algorithm to change raster value range, whilst preserving the shape of the raster’s histogram. Useful for when rasters from different sources should be compared or processed together and their pixel values should be in the same range. By default, the algorithm preserves the NODATA value of the input raster but there is an option to override it.

The following image displays a histogram of a DEM (value range is 85-243) And the next image displays a histogram of same DEM rescaled to the range 100-1000

Addresses Issue 26099.

This feature was developed by Alexander Bruy

Feature: Show related features in identify results tree¶

Users will now be able to see related (child) features in the results window when using the identify tool. Under each identified parent feature, new groups will show containing any related child features, displaying their attributes, actions, and allowing the user to directly open the feature form for the child feature.

This feature addresses issue 18634.

This feature was developed by Nyall Dawson

Feature: Filter expressions in relation reference widget¶

An option has been added for static filter expression to be used in the relation reference widget.

This feature was developed by Ivan Ivanov

Feature: Add project load profile times to debugging tools dock¶

Modification of the QgsRuntimeProfiler class which performs the following functions: 1. Make the profiling thread-safe, so that it’s possible to record times across multiple threads 2. Allows different profiling “groups”

The new groups API is used here to expose a breakdown of project load times in the debugging dock, alongside the existing QGIS startup profiling. It’s possible now to get a breakdown of the various stages of project load, in order to identify the causes of slow project load times.

TODO: In the majority of cases, performance problems will be caused by one or more layers, so it would be nice to further break down the individual layer load times. For example, for an individual WFS layer, we may see the time taken for the initial “server capabilities” or other queries. Add a group with profile times for map rendering, so you can see exactly which layers in your project are causing slow map redraw times.

In its current form, only the overall load time of each individual layer is displayed.

This feature was developed by Nyall Dawson

Feature: New Cell statistics algorithm¶

We added a Cell statistics raster analysis algorithm. It performs cell-wise statistics on a stack of raster layers while accounting for NoData. The functions available in the current implementation are:

• Sum
• Mean
• Median
• Standard Deviation
• Variance
• Maximum
• Minimum
• Majority (most frequent value)
• Minority (least frequent value)
• Range (max - min)
• Variety (count of unique values)

This feature was developed by Clemens Raffler

Feature: New Equal to frequency algorithm¶

We have added some new raster algorithms that operate on a local cell-by-cell basis in a raster stack. The Equal to frequency algorithm evaluates on a cell-by-cell basis the frequency (number of times) the values of an input stack of rasters are equal to the value of a value raster.

This feature was developed by Clemens Raffler

Feature: New Greater than frequency algorithm¶

We have added some new raster algorithms that operate on a local cell-by-cell basis in a raster stack. The Greater than frequency algorithm evaluates on a cell-by-cell basis the frequency (number of times) the values of an input stack of rasters are greater than the value of a value raster.

This feature was developed by Clemens Raffler

Feature: New Less than frequency algorithm¶

We have added some new raster algorithms that operate on a local cell-by-cell basis in a raster stack. The Equal to frequency algorithm evaluates on a cell-by-cell basis the frequency (number of times) the values of an input stack of rasters are less than the value of a value raster.

This feature was developed by Clemens Raffler

Feature: New Lowest position in raster stack algorithm¶

We added some raster value position analysis tools with this new QGIS version: The Lowest position in raster stack algorithm evaluates on a cell-by-cell basis the position of the raster with the lowest value in a stack of rasters. Position counts start with 1 and range to the total number input rasters. The order of the input rasters is relevant for the algorithm.

This feature was developed by Clemens Raffler

Feature: New Highest position in raster stack algorithm¶

We added some raster value position analysis tools with this new QGIS version: The Highest position in raster stack algorithm evaluates on a cell-by-cell basis the position of the raster with the highest value in a stack of rasters. Position counts start with 1 and range to the total number input rasters. The order of the input rasters is relevant for the algorithm.

This feature was developed by Clemens Raffler

Feature: New “Highest/Lowest position in raster stack” algorithms¶

Two new algorithms were added which add functionality ported from utilities commonly utilised with the ArcGIS Spatial Analyst extension:

• `Highest position in raster stack <https://pro.arcgis.com/en/pro-app/tool-reference/spatial-analyst/highest-position.htm>`__
• `Lowest position in raster stack <https://pro.arcgis.com/en/pro-app/tool-reference/spatial-analyst/lowest-position.htm>`__

The highest/lowest position algorithm evaluates the position of the raster with the highest/lowest value in a stack of rasters on a cell-by-cell basis. Position counts start with 1 and range to the total number input rasters. The order of the input rasters is relevant for the algorithm.

This feature was developed by Clemens Raffler

Feature: Add modeler algorithm to create directories¶

This algorithm allows models to create new file directories. Useful for models which have to output results to certain dynamically created paths (e.g. a folder containing the current date).

This feature was developed by Nyall Dawson

Feature: Add modeler algorithm to set a project expression variable¶

Allows a model to set Project-level expression variables during execution. Especially useful with the new Export Print Layout algorithms to allow models which dynamically set variables used in a layout prior to export.

This functionality was ported from https://gis.stackexchange.com/questions/359386

This feature was developed by Nyall Dawson

Feature: Add processing algorithms to export a print layout as PDF/image¶

Models are able to export print layouts from the current project. One use case for this is allowing users to create an in-project model which exports a particular set of layouts from the project to certain folders, so that they can easily re-export the current project in a single operation instead of having to manually open multiple layouts and export one-by-one.

Additionally, with the new capabilities to have expression based output files inside models, you can automatically export the layouts to a folder with the current date tag and include this in the exported file names!

This feature was developed by Nyall Dawson

Feature: Add a save features to file algorithm¶

There is now a native processing algorithm to save vector features to a file dataset within a model. It comes with a pair of advanced features to pass dataset and layer options on to GDAL.

This feature was developed by Mathieu Pellerin

Feature: Export layout atlas as PDF algorithm¶

A new QGIS processing algorithm was added which allows the export of a map atlas to PDF. This is the PDF counterpart to the recent export atlas layout to image algorithm.

This feature was developed by Mathieu Pellerin

Feature: New “Flatten Relationship” algorithm¶

This algorithm flattens all relationships for a vector layer, exporting a single layer containing one master feature per related feature. This master feature contains all the attributes for the related features.

It’s designed as a quick way to de-normalize a relation from a project, e.g. to allow exporting to CSV.

This feature was funded by SMEC/SJ

This feature was developed by Nyall Dawson

Feature: Export atlas layout as image algorithm¶

A new native processing algorithm was added to export layout atlases as images.

This is useful in models where remote datasets are processed with the goal of being used as atlas coverage layers.

This feature was developed by Mathieu Pellerin

Feature: Load processing results to layer group¶

Users can now optionally set a group name which ensures that the resulting output layers added to the project when using the Open output file after running algorithm option are grouped together. This allows all outputs from several processing algorithms to be grouped so that they may be easily located in the layer tree and be removed, exported, or have their visibility toggled easily.

This feature was developed by Germán Carrillo

Feature: Add zonal statistics algorithm which creates new output¶

Previously, when calculating zonal statistics, the algorithm always updated the original data source, adding additional fields. A new zonal statistics algorithm has been added which creates a new output instead. This functionality is an implementation of the 29504 feature request.

This feature was developed by Matthias Kuhn

Feature: Add geometry processing parameter¶

Added a new QgisProcessingParameterGeometry for passing geometries as a parameter to processing alogrithms.

This provides a way to pass simple geometries to algorithms without requiring an input layer.

The immediates use case are:

• Algorithms that might need to manipulate geometries in an atomic way.
• Delegation from parent algorithms.
• Use with headless qgis processing in stand-alone processing tools.

Features:

• The parameter is compatible with string parameters as it may pass Well-Known-Text as the value.
• The current widget interaction is minimalistic as it only uses the input text widget for entering the value as WKT.

This feature was developed by David Marteau

Feature: Add an interface to determine whether it is safe for the application to exit¶

An interface for plugins and scripts to register custom logic to prevent the QGIS application from exiting was added. This allows plugins to determine whether it is safe for the application to exit. This has made it possible to allow plugins to determine whether there are unsaved changes which should be saved or discarded before allowing QGIS to exit, functionality which has already been implemented in the console script editor, preventing data loss by prompting users when there are unsaved changes rather than silently shutting down the application.

This feature was developed by Nyall Dawson

Feature: List available GDAL vector drivers¶

A Vector Drivers tab is now available within the QGIS GDAL Settings window, which lists all the available GDAL vector drivers and allows users to toggle their active state. Where several drivers may be used to open data of a specific type, users may now modify these settings to ensure that the intended driver is used when importing specific vector data types. For example, the FileGDB and OpenFileGDB drivers are both capable of being used to import .gdb files, but if the data file has a version of 9.x, the FileGDB won’t be able to open it. In this instance, a user may disable the FileGDB driver and ensure that the data is loaded using the OpenFileGDB driver instead.

This functionality directly addresses the limitations outlined in Issue 18738.

This feature was developed by Alexander Bruy

Feature: Detect GRASS installation folder on MacOS¶

MacOS previously had a platform-specific custom parameter setting Grass7Utils.GRASS_FOLDER. This caused crashes for many users with multiple QGIS installations or hat had some invalid folder settings. The parameter has been removed and a GISBASE environment variable has been introduced instead, which is commonly used in GRASS scripts as the “root” installation directory, emulating the behavior used for GRASS detection in Windows environments. If GISBASE is not present (default), a search is performed for grass folders in QgsApplication.prefixPath() (when packaged in bundle format). If not found, the standalone GRASS instance is searched for. The new behaviour for GRASS is in-line with te methodology used for the GDAL and SAGA processing tools.

This resolves Issue 38595.

This feature was developed by Lutra Consulting (Peter Petrik)

Feature: Expose fields in the Browser¶

First part of QEP https://github.com/qgis/QGIS-Enhancement-Proposals/issues/171

Exposes field columns in the browser for providers that implement connections API:

• PG
• GPKG
• Spatialite
• MSSQL

The following operations are supported on fields:

• add new field
• delete field

This feature was developed by Alessandro Pasotti

Feature: ArcGIS Vector Tile Service connections¶

An option to create connections for ArcGIS Vector Tile Services was added to allow users to easily load vector tile layers from ArcGIS Server vector tile services. It also added support for authentication, configuration, and custom referer string to vector tile connections.

This change adds explicit UI options for adding and configuring connections to ESRI vector tile services. While these services use the standard vector tile framework for data retrieval, they can be directly added by creating a connection using the VectorTileService API endpoint on the ArcGIS server.

After a user adds a layer from a VectorTileService, the server’s default styling and labeling for the layer is automatically loaded.

This feature was developed by Nyall Dawson

Feature: Trust layer metadata propagation¶

The trust flag at the project level is only used to read the vector layer extent from xml, not from the provider.

This flag was not available at the vector layer and data provider level. A new QgsMapLayer reading flag to propagate the trust layer metadata for the project’s read flag and a new provider flag to trust the datasource config.

Trusting the datasource config allows the provider to use estimated metadata, ensures the primary key is unique and that the detectable geometry type and SRID are the same as the requested.

This feature was developed by rldhont

Feature: Add support for virtual columns in Oracle¶

Support for virtual (generated) Oracle columns has been added and is defined this way:

sql CREATE TABLE QGIS.GENERATED_COLUMNS ( "pk" INTEGER PRIMARY KEY, "generated_field" GENERATED ALWAYS AS ('test:' || "pk") VIRTUAL);

Note: It’s not possible to define a generated column on an SDO_GEOMETRY field in Oracle.

For now, when creating a new feature, the generated field is editable and should not be. A new API method needs to be added to retrieve readonly field from the provider as discussed in Issue 35995.

This feature was developed by Julien Cabieces

Feature: Add advanced options for data imports¶

New functionality has been introduced which allows advanced parameters to be specified when importing layers using the OGR data provider, opening a vast range of new possibilities, especially when working around expected dataset issues.

This feature was developed by Even Rouault

Feature: QGIS Server WFS3 API Sorting¶

Adds sorting functionality to the QGIS Server WFS3 API

This feature was developed by Alessandro Pasotti

Feature: QGIS Server landing page plugin¶

A Landing Page Plugin for QGIS Server was created, which is a C++ port of https://github.com/elpaso/qgis-server-landing-page-plugin

This feature was developed by Alessandro Pasotti

Feature: Environment variable to disable GetPrint and to not load layouts¶

A new QGIS_SERVER_DISABLE_GETPRINT environment variable was added to QGIS Server which prevents the loading of layouts when projects are read and disables the WMS GetPrint request, improving the read time of projects.

This feature was funded by Ifremer

This feature was developed by 3Liz

Feature: Environment variable to trust layer metadata with server settings¶

Trust layer metadata can be defined at the project level. A new project reading flag was added which allows the forcing of trust layer metadata.

For QGIS server, the trust layer metadata option can be overridden with QGIS_SERVER_TRUST_LAYER_METADATA environment variable.

This feature was funded by Ifremer

This feature was developed by 3Liz