Changelog for QGIS 3.8¶

Feature: Force Cartesian Measurements when Measuring Distances/Areas¶

In 3.8, we added an option to the measurement tool which forces Cartesian measurements for distance or area measurements. Previously, the measurement tools always used ellipsoidal/geodesic area and distance calculations, but there’s occasions when this is not desirable and users require pure Cartesian calculations instead.

This feature was funded by Oslandia

This feature was developed by Loïc Bartoletti (Oslandia)

Feature: Save to Template Button¶

While QGIS has offered support for Project Templates for many years, we enhanced this in 3.8 and made it much simpler for users to create new templates. Now, users can create a new template from their current project by selecting “Save To -> Templates” from the “Project” menu.

This feature was developed by Matthias Kuhn (OPENGIS.ch)

Feature: Improved “Zoom to Native Resolution” behavior¶

We’ve improved the “Zoom to Native” action, so it now works correctly with tiled (e.g. WMTS/XYZ/ArcGIS MapServer) layers, by zooming to the closest native tile resolution. Additionally, we tweaked tile rendering so that pixel-perfect rendering occurs when the map is viewed at a native tile resolution. The result: super-crisp map renders when using tiled layer sources!

Feature: Drag and Drop Layers to Map Layer widgets¶

To improve the usability of large QGIS projects, we now support direct drag and drop of layers from the project table of contents to any widget which asks for a map layer selection (e.g. Processing algorithms). For complex projects, locating a layer in the table of contents and dragging it is much easier then picking it from the flat map layer widget combo box!

Additionally, for Processing algorithms, layers can be dragged direct from the Browser panel to input layer choices.

This feature was developed by Nyall Dawson (North Road)

Feature: Multi-character strings for font markers¶

While QGIS has long offered support for rendering points using font-based character markers, we’ve enhanced this functionality in 3.8 and now offer the ability to render multi-character strings! And since we’re always aiming to make the QGIS application interface as user-friendly and pleasant to use as possible, we also took the opportunity to tweak the UI for font markers and squash a number of frustrating GUI issues which previous versions suffered from.

This feature was developed by Mathieu Pellerin

Feature: Point Displacement label distance factor¶

Another addition to the new symbology features added in 3.8 is a brand new label distance factor control for Point Displacement markers. This option allows displaced marker labels to be placed at a distance based on the actual marker diagonal size instead of a fixed distance.

This feature was developed by henrik

Feature: Hash Line symbol type¶

QGIS loves cartography, and we know you love making pretty maps! So we’ve added a brand-new line symbology option for “Hashed Lines”. This line symbol type is designed to replicate the ArcGIS Hash Line symbol layer type, and allows for a repeating line segment to be drawn over the length of a feature (with a line-sub symbol used to render each individual segment).

All options available for the existing Marker Line symbol layer are also available for hash lines, - e.g. first/last vertex, mid points, regular intervals, data-defined intervals, etc. The hash line length and angle can also have data defined overrides, which are evaluated per-line segment, allowing for the hash line to change size and angle over the length of a single rendered feature.

This feature was funded by anonymous

This feature was developed by Nyall Dawson (North Road)

Feature: Average line angles for marker and hashed line symbology¶

In previous QGIS versions, when a marker line was rendered using interval or center point place placement, the symbol angles were determined by taking the exact line orientation at the position of the symbol. This often leads to undesirable rendering effects, where little “jaggies” or corners in lines which occur right at the position of the symbol cause the marker to be oriented at a very different angle to what the eye expects to see.

We want your maps to be as beautiful as possible, so in QGIS 3.8 the marker angle is instead calculated by averaging the line over a specified distance either side of the symbol. E.g. averaging the line angle over 4mm means we take the points along the line 2mm from either side of the symbol placement, and use these instead to calculate the line angle for that symbol. This has the effect of smoothing (or removing!) any tiny local deviations from the overall line direction, resulting in much nicer visual orientation of marker or hash lines.

Like all symbol settings, the average angle smoothing distance can be set using mm/pixels/map units/etc, and supports data-defined values. Closed rings also correctly consider wrapping around these average angles from the start/end vertex.

This option is available for both the marker line symbol and the new hash line symbol types.

This feature was funded by anonymous

This feature was developed by Nyall Dawson (North Road)

Feature: Offset settings for point pattern fill symbol layers¶

To round out the new symbology options we’ve added in 3.8, the Point Pattern Fill symbol type has a new setting allowing for offsetting the markers in the pattern by a preset (or data-defined!) amount. This opens the door for many styling possibilities which were not possible in earlier versions, and further increases our compatibility with converted ArcGIS symbol and layer styles.

This feature was developed by Mathieu Pellerin

Feature: Live Effects Blur Radius is now hi-dpi friendly¶

QGIS 3.8 brings a highly-desired fix to layer effects’ blurring radius (aka strength). In earlier QGIS versions, these blur settings did not take into account the DPI of the map render — resulting in inaccurate effects rendering when exporting canvases/layouts at high resolutions. In 3.8, this was fixed and high-resolution map exports now match the results shown on the map canvas and are completely resolution-independent.

This feature was developed by Mathieu Pellerin

Feature: Geometry generators for labeling¶

This is a huge one! During the developer’s meeting in A Coruña, Matthias Kuhn took the opportunity to implement a frequently-asked-for feature in our labeling engine: Geometry Generator support.

Just like Geometry Generators for symbols, we now allow label paths and positions to be calculated using dynamically-evaluated geometry expressions. You can take advantage of the rich support for geometry processing which QGIS’ expression engine exposes, and use this to do ALL sorts of pre-processing to your feature geometries before they are labelled. Want to place labels around the start or end point of linestring geometries? What about dynamically smoothing and simplifying the path used for labeling river features, based on the current map scale? How about buffering polygon objects inward by a percentage of their area, and then labeling around the perimeter of this shrunken area? Now, it’s ALL possible, thanks to the power of labeling geometry generators!

This feature was funded by QGIS user group switzerland

This feature was developed by Matthias Kuhn (OPENGIS.ch)

Feature: Label Map Tools now use click-click behavior¶

Like the other QGIS digitizing and map tools, the “Move Label” and “Rotate Label” tools now use the standard left-click-to-start edit, left-click-to-end behavior. Consistency is good!

Feature: Wide lines and polygon edge highlighting¶

Like all recent QGIS releases, in version 3.8 we’ve significantly boosted QGIS’ 3D rendering capabilities. New 3D rendering features include:

• Configurable line width (in screen units) for “simple” 3D lines (in previous versions they were always 1px wide)

• Optional highlighting of edges of 3D polygons

This feature was funded by Andreas Neumann

This feature was developed by Martin Dobias (Lutra Consulting)

Feature: Export 3d animations¶

Another exciting change we’ve introduced in QGIS 3.8 is the ability to export your 3D animations! These are exported as a series of png/jpg/… images, which can be easily merged into .avi or other standard video files (using external tools).

This feature was funded by Northumberland National Park Authority

This feature was developed by Peter Petrik (Lutra Consulting)

Feature: Terrain from online sources¶

With this new version 3.8 feature, you can now directly fetch terrains for your 3D scenes from online sources (e.g. tiles hosted on AWS). No more sourcing and preparing rasters with DEM, just enable this option and see beautiful 3D scenes out-of-the-box!

This feature was funded by Crowdfunding: More QGIS 3D

This feature was developed by Martin Dobias (Lutra Consulting)

Feature: Configuration of field of view angle of camera¶

In QGIS 3.8, the field of view of the camera through which 3D scenes are rendered has gained a new configurable field of view settings.

This feature was developed by Mathieu Pellerin

Feature: Distribute spacing between items evenly¶

To make it easy to create your perfect QGIS Print Layout, we added new tools for automatically re-positioning items so that horizontal or vertical space between them is equal. This addition nicely rounds out the existing options for aligning items, bringing more of the power of a dedicated DTP application directly inside the QGIS Print Layout Designer!

This feature was developed by Matteo Nastasi

Feature: North Arrow Creation¶

We’ve listened to user feedback which indicated that the previous approach for creating north arrows within print layouts was too difficult, and consequently have added a new button in the Print Layout Designer for direct north arrow creation. This button is a shortcut to adding a picture item, setting it to a north arrow picture, and linking it with a map. The end result is identical, but it’s much easier for new users to understand if we expose it as an explicit “North Arrow” item!

Even experienced users will likely appreciate the improved workflow, including automatically linking the picture rotation to a sensible default map choice (if a map is selected, it’s used. If not, the topmost map item under the newly drawn north arrow is used. If there’s none, the layout’s ‘reference map’ (or biggest map) is used as a fallback).

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Order by support for expression aggregate and concatenation functions¶

Since certain aggregate and concatenation expressions require results in a certain order, we now allow control over the order features are added to the aggregate during expression evaluation.

E.g. concatenate("Station",concatenator:=',', order_by:="Station") will give a comma-separated list of station names in alphabetical order, rather than layer feature order.

This feature was funded by SMEC/SJ

This feature was developed by Nyall Dawson (North Road)

Feature: Simplified variant of “attribute” function¶

This improvement brings a second variant for the existing “attribute” function. The “attribute” function in previous QGIS releases required both a target feature and attribute name to be specified. The new version is much simpler, automatically using the current feature and only requiring an attribute name.

E.g.

Previous behavior:

attribute($currentfeature, 'name' ) -> returns value stored in ‘name’ attribute for the current feature

Improved behavior:

attribute( 'name' ) -> returns the value stored in ‘name’ attribute for the current feature

It’s just a faster shorthand version!

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Retrieve vertices from the end of geometeries¶

We added negative index support to the point_n(), angle_at_vertex(), and distance_to_vertex() functions, allowing for retrieval of vertices counting backward from the end of a geometry.

This feature was developed by Mathieu Pellerin

Feature: New expression functions¶

As always, a new QGIS release brings a bunch of new functions for use within QGIS’ expression engine. These new functions add increased flexibility and power to the expression engine, and everywhere it’s used throughout QGIS. This round, we’ve added a set of new functions which make it super-easy to operate on file names and paths.

New expression functions developed by Nyall Dawson of North Road:

• base_file_name: Returns the base name of the file without the directory or file suffix.

• file_exists: Returns true if a file exists

• file_name: Returns the file name from a full path

• file_path: Returns the directory/path from a full file path

• file_size: Returns a file size

• file_suffix: Returns a files suffix/extension

• is_directory: Returns true if a file path is a directory

• is_file: Returns true if a file path is a file

New expressions functions developed by Mathieu Pellerin of iMHere Asia:

• array_all: Returns true if an array contains the all values of a given array.

• concatenate_unique: Returns all unique strings from a field or expression joined by a delimiter.

Feature: New aggregation method: concatenate_unique¶

We added a new function concatenate_unique() to the expression engine (and Processing’s “aggregate” algorithm) to support concatenating only unique values from a list or set of features.

This feature was developed by Mathieu Pellerin

Feature: Floating widget for advanced input next to cursor¶

To make the existing Advanced Digitizing tools easier to use, we added an option to show the current distance/angle/x/y values as a floating display next to the mouse cursor.

This feature was funded by Kanton Schaffhausen

This feature was developed by Olivier Dalang and OPENGIS.ch

Feature: Chained add vertex at the endpoint¶

In QGIS 3.0, we added the ability to extend an existing line feature by clicking a “+” indicator at the start or end of line features when using the node tool. Version 3.8 extends this functionality by allowing addition of more than one vertex using the “+” button.

This feature was funded by Kanton Schaffhausen

This feature was developed by Olivier Dalang and OPENGIS.ch

Feature: Improvements in the vertex editor¶

For this release we improved the vertex editor so it will now properly link the selected vertices on the canvas with the vertices for manual coordinate editing in the table.

This feature was funded by QGIS User Group Switzerland

This feature was developed by Denis Rouzaud, OPENGIS.ch

Feature: Allow browsing feature list¶

Feature: HTML Form Widget¶

Thanks to the generous sponsorship by A.R.P.A Piemonte (one of the italian regional environmental agencies) we developed a new form widget with HTML body and access to feature values and expressions.

This feature was funded by A.R.P.A. Piemonte

This feature was developed by Alessandro Pasotti

Feature: Form widgets custom background color¶

Thanks to the generous sponsorship by A.R.P.A Piemonte (one of the italian regional environmental agencies) we finally freed you from the boredom of gray backgrounds.

This feature was funded by A.R.P.A. Piemonte

This feature was developed by Alessandro Pasotti

Feature: Browse through features in the attribute table form view¶

We’ve added the possibility to browse through the attributes of features in a layer. This makes workflows for asset management a lot easier! You can:

1. Define a filter

2. Browse through all matching features

3. Review and adjust

You can also pan and zoom to the geometry of the feature or highlight the current feature as you browse.

(This replaces the previous ItemBrowser plugin with equivalent inbuilt functionality.)

This feature was funded by regioDATA

This feature was developed by Denis Rouzaud, OPENGIS.ch

Feature: Add “Save layer styles into GeoPackage” option for Package Layers algorithm¶

QGIS loves GeoPackage, so it’s likely no surprise that every new QGIS version brings improvements to GeoPackage handling! In 3.8, we enhanced the “Package Layers” Processing algorithm so that it now allows embedding the current layer styles directly into the packaged layers!

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Overlap Analysis¶

This new Processing algorithm calculates the area and percentage cover by which features from an input layer are overlapped by features from a selection of overlay layers. New attributes are added to the output layer reporting the total area of overlap and percentage of the input feature overlapped by each of the selected overlay layers.

This is quite a common GIS task request, yet is full of traps for inexperienced users, and the amount of manual data work usually done by users to calculate these figures can often lead to mistakes and inaccurate results. We want to make spatial analysis as easy and foolproof as possible, so we’ve added Overlap Analysis as an inbuilt tool which allows this task to be done in a single step without risk of human error.

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Allow rounding values in Extract Layer Extent¶

We’ve added a parameter to the Processing algorithm ‘Extract Layer Extent’ to round the extent bounding box coordinates to a certain interval. While rounding, the bounding box will only ever be enlarged, to ensure it will always cover the input data set. (I.e. the x and y minimum coordinates are rounded down, and x and y maximum coordinates are rounded up).

This feature was developed by Raymond Nijssen

Feature: New options for autofilling batch Processing¶

In QGIS 3.8 we moved the existing “double click column header” to fill values down functionality to a new “Auto fill” button in the Processing Batch dialog, making this feature much more user-discoverable (we suspect many users had no idea this handy shortcut even existed!). In addition, we’ve added TONS of new functionality to easily auto-populate the batch table. These include:

• File or layer parameters can now be batch populated by searching for files in a directory with a matching filename pattern (including recursive searches!). Ever needed to auto convert 100s of Shapefiles from a set of folders? Now it’s easy to do!

• An option to add calculated values from a QGIS expression, allowing complex range-based values to be added to the dialog (e.g. values from 100-1000, increasing by 50)

• A “Calculate by Expression” option allows for updating existing batch table cells using the results of a QGIS expression. These expressions can freely utilise other parameter values from the input batch rows, making it easy to craft the exact output file name you desire based on the other columns values in a batch row.

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Generate raster XYZ tiles¶

We’ve added a brand-new algorithm to generate raster “XYZ” tiles using the current QGIS project. Tile images can be saved as individual images in directory structure, or as a single file in the “MBTiles” format.

This feature was funded by Hansestadt Herford, SWK mbH, Datenbankgesellschaft mbH

This feature was developed by Lutra Consulting

Feature: Resurrection of the OTB provider¶

QGIS 3.8 brings back the OTB Processing provider, which was removed in the QGIS 3.0 update. The provider was updated to use all the new goodies which are available in Processing in QGIS 3, and is once again available out-of-the-box for all your imagery analysis requirements!

(Note that OTB is a third party dependency which must be manually installed by users. Instructions on installing OTB are available `here <https://gitlab.orfeo-toolbox.org/orfeotoolbox/qgis-otb-plugin#open-processing-settings>`__)

This feature was developed by Rashad Kanavath

Feature: Expression variables for a model¶

We’ve added a new “Model Variables” dock panel to the model editor, allowing you to create and set custom expression variables for use in your Processing models. These variables are available anywhere expressions are evaluated within the model, so you can use them as input parameter values for child algorithms, within data-defined dynamic parameters, etc.

The prime use case here is for models which use a constant value throughout multiple steps within the model (e.g. @target_resolution: a target raster resolution, @max_simplification: a simplification value for input features coming from different sources, etc). Previously, you’d need to hunt down and replace these values in multiple places when you wanted to tweak them. By replacing them with variables in your model you only have a single place you need to edit these values when you want to adjust them!

Model variables are stored within an individual Processing model itself, and are not exposed outside of the model designer dialog.

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Improved modeler UI¶

We’ve added numerous usability improvements to the Processing Graphical Modeler, including

• The addition of helpful tooltips when hovering over model components

• Algorithms and inputs connected to model components are highlighted as you hover the mouse over different parts of the model, making it much easier to visualise the model flow and connections inside complex models

• Input parameter types are now shown in the title of the parameter definition dialog

• The data type for numeric parameters may now be specified, allowing for integer-only inputs for models

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Flagging algorithms with known issues¶

By default, we now hide 3rd party algorithms with known issues from the Processing toolbox, helping you avoid frustration (or misleading results) when running these algorithms. A new setting in the Processing options screen allows these algorithms to be shown, but they will be highlighted in the toolbox with a warning icon. Use at your own risk!

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Raster Boolean logical OR/AND algorithms¶

In version 3.8 we’ve added new algorithms which calculate the boolean OR or AND for a set of input rasters. For AND, if all of the input rasters have a non-zero value for a pixel, that pixel will be set to 1 in the output raster, otherwise it will be set to 0. For OR, if ANY of the input rasters have a non-zero value for a pixel, that pixel will be set to 1 in the output raster, else 0.

A reference layer parameter allows you to specify an existing raster layer to use as a reference when creating the output raster. The output raster will have the same extent, CRS, and pixel dimensions as this layer.

By default, a nodata pixel in ANY of the input layers will result in a nodata pixel in the output raster. If you check the ‘Treat nodata values as false’ option, then nodata inputs will be treated the same as a 0 input value.

These new algorithms make for much simpler raster boolean logic calculation, without the complexity of using the raster calculator. They are also dynamically scalable to any number of input rasters (unlike the raster calculator), so are much more flexible when used within your Processing models.

This feature was funded by SMEC/SJ

This feature was developed by Nyall Dawson (North Road)

Feature: New input parameter types for Print Layouts and Print Layout Items¶

By adding new parameter types for Print Layouts and Print Layout items, we’ve opened up QGIS 3.8 to a whole new world of Processing algorithms which operate on print layouts. These new parameter types allow for creation of Processing algorithms and graphical models which prompt users to select a print layout and/or an item on the layout when run.

This feature was funded by SMEC/SJ

This feature was developed by Nyall Dawson (North Road)

Feature: New parameter type for Map Scales¶

We’ve added a new parameter type specifically for map scales, QgsProcessingParameterScale. Scale values are evaluated using self.parameterAsDouble, which return the map scale denominator (matching the standard in other parts of the QGIS API).

Scale parameters are displayed to users using the standard QgsScaleWidget, which includes the combo box of predefined scales and a shortcut button to match the current map scale. The addition of this new parameter type allows you to create Processing algorithms and models which require a scale choice at run time.

This feature was funded by SMEC/SJ

This feature was developed by Nyall Dawson (North Road)

Feature: Improved “point” parameter handling¶

We improved the workflow for algorithms with a “point” input parameter. When picking the point coordinate from a map you can now take advantage of QGIS snapping tools, allowing you to exactly match the point parameter to a feature’s boundary.

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: New “Print Layout Map Extent to Layer” algorithm¶

Taking advantage of the new facilities for accessing Print Layouts in Processing, we added a new algorithm which creates a polygon layer containing the extent of a print layout map item. The output layer also includes handy attributes specifying the map size (in layout units), scale and rotation.

If you’ve ever wanted to create an advanced overview indicator, and the inbuilt layout tools haven’t sufficed — this new algorithm is for you!

This feature was funded by SMEC/SJ

This feature was developed by Nyall Dawson (North Road)

Feature: Add X/Y fields to layer¶

This new algorithm is a handy shortcut for adding X and Y (or latitude/longitude) fields to a point layer. You can even calculate the X/Y values using a different coordinate reference system from the layer (e.g. creating latitude/longitude fields for a layer in a projected CRS).

This feature was funded by SMEC/SJ

This feature was developed by Nyall Dawson (North Road)

Feature: “Join attributes by nearest” algorithm¶

You can now perform K-nearest neighbour joins from the Processing toolbox!

QGIS 3.8 brings a new algorithm which takes an input vector layer and creates a new vector layer with additional attributes in its attribute table. The additional attributes and their values are taken from a second vector layer, where features are joined by finding the closest features from each layer.

By default only the single nearest feature is joined, but optionally the join can use the n-nearest neighboring features instead. If a maximum distance is specified, then only features which are closer than this distance will be matched.

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Grass r.geomorphon algorithm¶

The upstream GRASS team has been hard at work creating a new GRASS module for terrain analysis — “r.geomorphon”. In 3.8 we expose their efforts via a new Processing tool, which calculates geomorphons (terrain forms) and associated geometry using a machine learning approach.

Feature: GDAL pansharpening algorithm¶

Another third party tool which we’ve added to the Processing toolbox in QGIS 3.8 is the GDAL pansharpening tool. Now it’s easy to take advantage of this fast, powerful tool in your Processing analysis scripts and models.

This feature was developed by Alexander Bruy

Feature: New fields prefix parameter for overlay algorithms¶

We’ve added overlay layer fields prefix parameter for the following algorithms:

• intersection algorithm

• line intersection algorithm

• symmetrical difference algorithm

• union algorithm

This can come in very handy to avoid arbitrary colliding field renaming when merging layers.

This feature was developed by Mathieu Pellerin

Feature: Direct access to sheets from XLSX/ODS files¶

QGIS 3.8 brings even more power to the browser panel, and now displays all sheets from spreadsheet files (e.g. Microsoft Excel and LibreOffice calc files) in the browser file tree.

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: QGIS projects inside geopackage files¶

Did we already say that QGIS loves GeoPackage? Need any more proof of this? Well, in QGIS 3.8, we’ve added to ability to store QGIS projects directly inside GeoPackage files! Now you can create a totally self-contained GeoPackage which embeds a QGIS Project AND all the data used by the project. (Let’s see Shapefiles match that one!)

This feature was funded by QCooperative

This feature was developed by Alessandro Pasotti

Feature: Much Improved Coordinate Transform Handling¶

Thanks to underlying work from the tireless PROJ and GDAL teams, QGIS now sports many huge improvements in geodetic and transformation capabilities! Highlights include:

• The PROJ CRS database is now used to populate QGIS’ CRS selection lists, removing the custom database we used in previous releases. This means that ALL responsibility for CRS definitions and updating these sit were they belong, upstream in the PROJ library – and consequently you can expect to see QGIS CRS definitions being a closer match to the official definitions, and newer CRS definitions will be added much faster than in previous releases.. This change also means we’ll be an exact match for projection handling as all other open-source geospatial tools which have completed the port to the latest PROJ version, such as GDAL 3.0.

• We now rely entirely on PROJ’s wonderful logic for generating the best coordinate operation to transform between CRS pairs. This means (amongst other stuff), we correctly support complex things like operations which require a “pivot datum”, e.g. transformation to and from the GDA2020 coordinate systems.

• Instead of the older approach QGIS used for datum transformations (carrying around our own table of when grid shift files can be used), we now use PROJ to determine these. This considerably changes the user interface shown when a user has opted into selecting manually a transform to use when multiple transforms exist, and we now show a simplified list of available (and non-available) pathways.

• We also use PROJ’s database to populate lists of available ellipsoids for use in distance and area calculations. This has cleaned up the ellipsoid choices considerably, and added many additional ellipsoid definitions as a result.

• The UX for notifying users about issues in coordinate transforms is greatly improved, e.g. users are now alerted when a more accurate transform is possible, but not usable on their system (due to missing .GSB grid shift files). Wherever possible, we present users with direct download links to obtain these required/desired grid shift files. The intention here is to ensure users are informed when transforms can be improved, instead of silently falling back to less accurate options.

• Users also now have the option of placing grid shift files in a “proj” folder under their QGIS user profile. This change means users can install grid shift files and make them available in QGIS without requiring administrative rights.

• We’ve also completed a project which began back in the lead-up to 3.0, which ensures that project-specific transformation pathway settings are correctly respected EVERYWHERE a coordinate transform is performed. This also means we’re ready for the next stage in handling 4d temporal based coordinate transforms (when these start to land in 2020 and beyond).

A lot of this is only possible thanks to improvements in the underlying PROJ and GDAL libraries, which landed as a result of the GDAL “barn raising” effort. On the QGIS side, it was ONLY possible thanks to funding from the Australian ICSM.

This feature was funded by ICSM

This feature was developed by Nyall Dawson (North Road)

Feature: postgres provider: add support for generated identity columns¶

This feature was developed by jef-n

Feature: String List support for compatible layers¶

QGIS 3.8 now fully supports disk-based layers with String List fields, allowing you to take advantage of QGIS’ flexible handling of list field types with these formats.

This feature was developed by Mathieu Pellerin

Feature: Much Improved ArcGIS MapServer Handling¶

We rebuilt the ArcGIS MapServer provider, adding significant improvements over previous versions:

• Tiled layers are now loaded progressively, with immediate feedback

• We significantly optimised the provider, resulting in much faster map redraws

• MapServer layers now correctly respect authentication settings and HTTP referrer settings.

• “Nested” services are correctly shown in the QGIS browser panel

• ImageServer services can be added using the provider

End result: MapServer layers are now silky smooth in QGIS!

This feature was developed by Nyall Dawson (North Road) & Mathieu Pellerin (iMHere Asia)

Feature: SQL Server: handle v2 geometries, including curved and Z/M geometries¶

SQL Server users rejoice: QGIS now fully supports curved geometry types (and other “version 2” geometry fields)!

In past QGIS versions, the SQL Server provider would only handle version 1 type geometries, and could only show straight feature types. In 3.8, we’ve added full support for version 2 geometries. This change also allows full support for Z or M enabled geometry types! Additionally, we fixed several known issues with geography field types.

This feature was developed by Tamas Szekeres

Feature: WMS: Define one filter for several layers¶

Sometimes, you need to define the same filter for every selected layer when making a WMS request (e.g. when accessing user-specific data). In previous QGIS versions we had to define the filter using the format:

&FILTER=layer1:"column1" = 'value1';layer2:"column1" = 'value1';layer3:"column1" = 'value1'

With QGIS 3.8, we’ve simplified this, and now allow the filter format:

&FILTER=layer1,layer2,layer3:"column1" = 'value1'

This feature was funded by VEOLIA

This feature was developed by Julien Cabieces (Oslandia)

Feature: Support for curves in DXF export¶

You can now export curved geometry layers to DXF format without segmentizing the features — no more loss of curves!

This feature was funded by Kanton Schaffhausen

This feature was developed by Jürgen Fischer in collaboration with Matthias Kuhn

Feature: Allow configuring size for GetLegendGraphics¶

This feature was developed by David Signer, OPENGIS.ch

Feature: Support for plugin dependencies¶

In QGIS 3.8, we’ve introduced a long-sought-after feature for QGIS plugin developers: the ability to specify dependencies for your plugins.

To add a plugin dependancy, you can use the new metadata “plugin_dependencies”. The format is a comma-separated list of PIP-like plugin names (with optional version). E.g:

plugin_dependencies=GeoCoding,IPyConsole==1.9

The example above will require:

• Any version of GeoCoding

• Version 1.9 of IPyConsole

When a plugin is installed, the metadata is parsed and a user will be prompted with a dialog listing the dependencies. The user can then decide what to do with the dependencies:

• Install

• Upgrade/downgrade

• Do nothing

This feature was funded by GISCE TI

This feature was developed by Alessandro Pasotti

Feature: REGEXP SQL syntax support for spatialite provider and python connections¶

We’ve enabled REGEX to be used with the spatialite provider. (This comes in handy when setting filters!). We’ve also added support for this syntax via any python connections made through Qgis.utils’s “spatialite_connection” API - allowing you to use REGEXP in your SQL queries from within DB Manager.

This feature was developed by Mathieu Pellerin

Feature: Nearest Neighbour search in QgsSpatialIndex¶

We added API to allow accurate nearest neighbor search based on QgsGeometry to QgsGeometry searches via QgsSpatialIndex. In previous QGIS versions only point to geometry nearest neighbour searches were possible. But with this change, you can safely and accurately use QgsSpatialIndex to determine the nearest neighbours between any types of geometries.

This feature was funded by North Road

This feature was developed by Nyall Dawson (North Road)

Feature: Bug fixes by Alessandro Pasotti¶

This feature was funded by QGIS.ORG donors and sponsors

This feature was developed by Alessandro Pasotti

Feature: Bug fixes by Alexander Bruy¶

This feature was funded by QGIS.ORG donors and sponsors

This feature was developed by Alexander Bruy

Feature: Bug fixes by Victor Olaya¶

This feature was funded by QGIS.ORG donors and sponsors

This feature was developed by Victor Olaya

Feature: Bug fixes by Even Rouault¶

This feature was funded by QGIS.ORG donors and sponsors

This feature was developed by Even Rouault

Feature: Bug fixes by Denis Rouzaud¶

This feature was funded by QGIS.ORG donors and sponsors

This feature was developed by Denis Rouzaud

Feature: Bug fixes by Peter Petrik¶

This feature was funded by QGIS.ORG donors and sponsors

This feature was developed by Peter Petrik

Feature: Bug fixes by Loïc Bartoletti¶

This feature was funded by QGIS.ORG donors and sponsors

This feature was developed by Loïc Bartoletti