RSS Entry of QGIS Project's latest versionhttps://changelog.qgis.org/id/qgis/version/3.0.0/2024-03-28T15:12:00.189069+00:00These are the entries from the latest version of QGIS project.support for output geometry types in modelshttps://changelog.qgis.org/id/entry/692<p><p>Model child algorithm inputs are now filtered to only those which generate applicable geometry types for the input to another child algorithm</p></p><p><img src="/media/"/></p>save and restore color ramp used for singleband pseudocolor renderinghttps://changelog.qgis.org/id/entry/727<p></p><p><img src="/media/"/></p>remove TauDEM provider from core Processinghttps://changelog.qgis.org/id/entry/811<p><p>We have removed the TauDEM provider from processing.</p></p><p><img src="/media/images/entries/c48a25965a147b866502d10771bea3e831a4d28e.jpeg"/></p>remove TauDEM provider from core Processinghttps://changelog.qgis.org/id/entry/774<p><p>TauDEM is quite specific set of tools and it requires installation of
some additional tools. So we decide to turn it into separate provider,
reducing core codebase size and maintenance efforts.</p></p><p><img src="/media/"/></p>raster auto-stretching when updating canvashttps://changelog.qgis.org/id/entry/755<p><p>see <a href="https://lists.osgeo.org/pipermail/qgis-developer/2016-September/044393.html">https://lists.osgeo.org/pipermail/qgis-developer/2016-September/044393.html</a></p>
<ul>
<li>follow up to raster pseudocolor updated extent auto classification</li>
</ul></p><p><img src="/media/"/></p>pole of inaccessibility algorithmhttps://changelog.qgis.org/id/entry/732<p><pre><code>Implements a processing algorithm to
calculate the pole of inaccessibility for a surface, which is the
most distant internal point from the boundary of the surface. This function
uses the 'polylabel' algorithm (Vladimir Agafonkin, 2016), which is an iterative
approach guaranteed to find the true pole of inaccessibility within a specified
tolerance. More precise tolerances require more iterations and will take longer
to calculate.
</code></pre></p><p><img src="/media/"/></p>new global expression variable @qgis_localehttps://changelog.qgis.org/id/entry/771<p><p>Returns current locale used by QGIS. By default this is current system locale. If user enabled locale override in QGIS settings overriden locale will be returned.</p></p><p><img src="/media/images/entries/23e0bd2bc2cd560dad2d2a873e7d9ab98c532fb0.png"/></p>item_variables expression function inside compositionshttps://changelog.qgis.org/id/entry/772<p><p>This adds a new item_variables expression function when expressions are used inside a composition context.</p>
<p>The function takes a single argument, the id for an item inside the composition, and returns a map of variable name to value for that item.
This allows you to do things like insert text in a label fetching properties of another item in the composition, eg</p>
<p>Insert scale of map into a label:</p>
<p><code>map_get( item_variables( 'map'),'map_scale')</code></p>
<p>Insert x coordinate of map center into a label:</p>
<p><code>x(map_get( item_variables( 'map'),'map_extent_center'))</code></p></p><p><img src="/media/"/></p>improved Extract nodes algorithmhttps://changelog.qgis.org/id/entry/688<p><p>Extract nodes algorithm now saves node
index, distance along line and angle at node</p></p><p><img src="/media/"/></p>expose zonal statistics from Zonal statistics plugin in toolboxhttps://changelog.qgis.org/id/entry/712<p></p><p><img src="/media/"/></p>dxf export: support reprojectionhttps://changelog.qgis.org/id/entry/700<p></p><p><img src="/media/"/></p>conditional visibility for tabs and groupboxeshttps://changelog.qgis.org/id/entry/696<p><p>This adds a new configuration option to conditionally show or hide tabs and groupboxes in drag and drop designer forms.
Configuration is done via a double click in the designer tree in the fields configuration interface.
An expression can be entered to control the visibility. The expression will be re-evaluated everytime values in the form change and the tab or groupbox shown/hidden accordingly.</p></p><p><img src="/media/"/></p>allow installing plugins from local ZIP packageshttps://changelog.qgis.org/id/entry/783<p><p>It is now more easy to install plugins manually without having to unzip them in the user profile directory by hand. </p></p><p><img src="/media/images/entries/b0311613cf73564f4dc104772abfab551c391dad.jpg"/></p>algorithm to fix invalid geometries using native makeValid() implementationhttps://changelog.qgis.org/id/entry/785<p></p><p><img src="/media/"/></p>added ‘invalid feature handling’ optionhttps://changelog.qgis.org/id/entry/769<p></p><p><img src="/media/"/></p>add search to Get Scripts and Models dialoghttps://changelog.qgis.org/id/entry/674<p></p><p><img src="/media/"/></p>add search bar to the Configure Shortcuts dialoghttps://changelog.qgis.org/id/entry/764<p><p>Supports search by action name and by shortcut</p></p><p><img src="/media/images/entries/5f9439417546fff26fe410b5a860a7680b07c53e.png"/></p>add import into spatialite algorithmhttps://changelog.qgis.org/id/entry/721<p></p><p><img src="/media/"/></p>add a spatialite execute SQL algorithmhttps://changelog.qgis.org/id/entry/713<p></p><p><img src="/media/"/></p>Vertex tool: support for advanced digitizing panelhttps://changelog.qgis.org/id/entry/827<p><p>The advanced digitizing panel now works also with the vertex tool - it is possible to enter coordinates
of new or existing vertices in the panel just like in other digitizing map tools.</p></p><p><img src="/media/images/entries/297f18356a626066332b4c28e13ce4c94bb70166.gif"/></p>Vertex tool: mid-point markers to add verticeshttps://changelog.qgis.org/id/entry/825<p><p>The improved vertex tool now also displays extra markers on the mid-point of line segments of features.
Clicking such marker results in addition of a new vertex. The existing way of adding vertices by double-clicking
segments has been kept.</p></p><p><img src="/media/images/entries/b47f105d5ea3ecf5176a8296cc386c65bce21da7.gif"/></p>Vertex tool: continue linehttps://changelog.qgis.org/id/entry/826<p><p>When editing linestring geometries with the vertex tool, moving the mouse towards the first or the last
vertex will display an extra marker just next to the endpoint. Clicking the marker will add a vertex
at the end of the geometry.</p></p><p><img src="/media/images/entries/b355e0701d6b395d25a965cc7d31b9f8acce49d7.gif"/></p>Unique and not-null constraint handlinghttps://changelog.qgis.org/id/entry/724<p><p>Automatic detection of provider-side unique and not-null constraints implemented for postgres, spatialite, ogr provider</p>
<p>Client side unique and not-null constraints can be set within QGIS.</p>
<p>Unique constraints are enforced in attribute form</p></p><p><img src="/media/"/></p>Unified data source manager dialoghttps://changelog.qgis.org/id/entry/818<p><p>A single unified dialog to handle data source management and layers loading.</p></p><p><img src="/media/images/entries/3d6a40ee709ca4f18d8532291f3cbc97997f1932.gif"/></p>Trigger layer refresh or layer actions from PostgreSQL NOTIFY signal https://changelog.qgis.org/id/entry/823<p><p>Following the live layer effects, this allows to trigger actions or layer refresh in QGIS only when the database notifies QGIS it should do something.
It will require less ressources than refreshing on interval, and you can even code a chat application in QGIS with that :)</p>
<p>See <a href="https://vimeo.com/236604742">https://vimeo.com/236604742</a> </p>
<p><a href="http://oslandia.com/en/2017/10/07/refresh-your-maps-from-postgresql/">http://oslandia.com/en/2017/10/07/refresh-your-maps-from-postgresql/</a></p></p><p><img src="/media/"/></p>Transparency support for paletted rendererhttps://changelog.qgis.org/id/entry/753<p><p>In QGIS 3.0, it is now possible to change the transparency value for unique values for the paletted renderer. </p></p><p><img src="/media/images/entries/603b73fbf8ad7db9cdb43689641eb70326c11bbf.png"/></p>Tracing with offsethttps://changelog.qgis.org/id/entry/820<p><p>You can now use the trace digitising tool with an offset as shown in the accompanying image.</p></p><p><img src="/media/images/entries/974604dc8908668c2d727e12975707560cffb493.gif"/></p>Toggle visibility of opened panels in main windowhttps://changelog.qgis.org/id/entry/754<p><p>Accessible via:
- View menu > Toggle Panels Visibility
- <strong>Ctrl+Tab</strong> keyboard shortcut</p></p><p><img src="/media/images/entries/68249b50c2813f4b204cb0305587b2850e7cd61e.gif"/></p>Task managerhttps://changelog.qgis.org/id/entry/745<p><p>Introduces a framework for creating background tasks, which are interacted with through a centralised manager</p>
<pre><code>Adds new classes:
- QgsTask. An interface for long-running background tasks
- QgsTaskManager. Handles groups of tasks - also available as a QgsApplication member for tracking application wide tasks
Add simple python method QgsTask.fromFunction for creation of tasks from a function without having to create a QgsTask subclass
Support for dependent tasks
Cancelling a task on which others depend leads to all these other
tasks getting cancelled as well.
Add handling of dependent layers to task manager
If a task has dependent layers which are about to be removed,
the task will automatically be cancelled
</code></pre>
<p>QgsTasks can have subtasks</p>
<pre><code>Now, a QgsTask can have subtask QgsTasks set by calling
QgsTask::addSubTask. Sub tasks can have their own set of
dependent tasks.
Subtasks are not visible to users, and users only see the overall
progress and status of the parent task.
This allows creation of tasks which are themselves built off
many smaller component tasks. The task manager will still handle
firing up and scheduling the subtasks, so eg subtasks can run
in parallel (if their dependancies allow this).
Subtasks can themselves have subtasks.
This change is designed to allow the processing concept of
algorithms and modeller algorithms to be translatable
directly to the task manager architecture.
</code></pre></p><p><img src="/media/"/></p>Support setting of color and transparency on multiple items for raster renderershttps://changelog.qgis.org/id/entry/749<p><p>It is now possible to change the color and transparency for multiple values at the same time for the singleband pseudocolor and the paletted renderers. Simply select values within the values' list and right click to have a pop-up menu appear.</p></p><p><img src="/media/images/entries/dc60a3f5fdc3a6568e8f3b9bf635066fcde9926d.png"/></p>Support for Z/M geometries in gpkg, spatialite and memory layer providerhttps://changelog.qgis.org/id/entry/806<p><p>Support for Z dimension and M values was added to QGIS' gpkg, spatialite and memory layer provider.
the option to add Z and M dimensions has also been added to the "create new layer" dialogs</p></p><p><img src="/media/images/entries/63c518b689c749b106944c9d48826abba90887f0.jpg"/></p>Support for HStore in PostGIS data providerhttps://changelog.qgis.org/id/entry/662<p></p><p><img src="/media/"/></p>Support all GDAL writable raster formats for 'Save as' dialog on raster layershttps://changelog.qgis.org/id/entry/665<p></p><p><img src="/media/"/></p>Style management re-work and upgradehttps://changelog.qgis.org/id/entry/734<p><p>Style management has received a major upgrade. The improvements include:
- A new favorite grouping system was added, which the symbols list widget defaults to
- The selected tag / smartgroup in the symbols list widget now persists when switching layers (and across sessions)
- The symbols list widget will update the tag / smartgroup combo box when users add / rename / remove categories
- Users can now directly tag, as well as add to favorites, symbols while saving those to the style database
- To streamline style management, groups have been removed and fully replaced by tags
- Tags have been integrated into the import/export user interface</p></p><p><img src="/media/images/entries/bb43cc8a048018b0f54463674ebf2d11bb0abc21.png"/></p>Standalone QGIS Browser application removedhttps://changelog.qgis.org/id/entry/835<p><p>We have removed the standalone QGIS Browser application that shipped with QGIS 2.x. This application had poor user uptake and represented a maintenance overhead that we do not wish to continue with in the 3.0 code base.</p></p><p><img src="/media/"/></p>SplitWithLineshttps://changelog.qgis.org/id/entry/740<p><p>Rename algorithm SplitLinesWithLines to SplitWithLines
Accept polygon as input, too
Use only selected lines to split with (if processing is set to use selection only)
Issue log message if trying to split multi geometries
Update help</p></p><p><img src="/media/"/></p>Sort by expression algorithmhttps://changelog.qgis.org/id/entry/830<p></p><p><img src="/media/"/></p>Snap geometries to layer algorithmhttps://changelog.qgis.org/id/entry/729<p><p>Port the Geometry Snapper plugin to processing</p>
<p>Snap geometries algorithm allows snapping
to other layer types, supports point/line layers</p>
<p>Snap to layer algorithm accepts a mode parameter. With a new option to prefer to snap to closest point on geometry.
The old behaviour was to prefer to snap to nodes, even if a node
was further from the input geometry than a segment. The new option
allows you to snap geometries to the closest point, regardless
of whether it's a node or segment.</p></p><p><img src="/media/"/></p>Smarter default edit widgets with plugins to pick themhttps://changelog.qgis.org/id/entry/689<p><p>Now the widgets can give a score on how well they could handle the type of a field. Leading to better default widgets.</p>
<p>Additionally, plugins can be added to choose a widget type in function of external information. One of them uses a table in PostgreSQL, allowing to specify the widget type and configuration to use for each field.</p>
<p>Automatically pick RelationReference widgets for foreign keys.</p></p><p><img src="/media/"/></p>Show field values in autocompleter in form filter modehttps://changelog.qgis.org/id/entry/756<p><pre><code>The autocompleter is nicely updated in the background so that
the gui remains nice and responsive, even if there's millions
of records in the associated table.
It's now used as a search widget for text fields, so can be seen
in the browser window if you set the filter to a text field, or
if you launch the form based select/filter by selecting a layer
and pressing F3.
</code></pre></p><p><img src="/media/"/></p>Show an alpha slider in color button drop down menuhttps://changelog.qgis.org/id/entry/748<p><p>Allows quick tweaks to the color alpha</p></p><p><img src="/media/images/entries/669437f416c6ef5c18dd87ecdfc52772e0b597c7.png"/></p>Removed otb and lidartools providers from processinghttps://changelog.qgis.org/id/entry/782<p><p>The new logic will be to develop plugin providers that will be able to follow the external software lifecycle. </p></p><p><img src="/media/"/></p>Remove zonal stats pluginhttps://changelog.qgis.org/id/entry/717<p><p>This is now fully exposed via processing, which is the logical
place for this feature to reside.</p></p><p><img src="/media/"/></p>Remove trusted status from Plugin Managerhttps://changelog.qgis.org/id/entry/670<p><p>https://github.com/qgis/QGIS/pull/5272</p></p><p><img src="/media/"/></p>Remove orphaned oracle raster pluginhttps://changelog.qgis.org/id/entry/760<p></p><p><img src="/media/"/></p>Remove dxf2shp converter pluginhttps://changelog.qgis.org/id/entry/716<p><p>This functionality is available in OGR and there is no longer a need for a dedicated QGIS plugin to do this task</p></p><p><img src="/media/"/></p>Raster unique values count for processinghttps://changelog.qgis.org/id/entry/667<p><p>http://imhere-asia.com/blog/post/qgis-raster-layer-unique-values-count</p></p><p><img src="/media/"/></p>Raster stretch toolbar actions support for pseudocolor rendererhttps://changelog.qgis.org/id/entry/761<p></p><p><img src="/media/"/></p>Raster analysis algorithms added to Processinghttps://changelog.qgis.org/id/entry/706<p><p>The following algorithms were added to Processing from the Raster Analysis plugin:</p>
<ul>
<li>Aspect</li>
<li>Slope</li>
<li>Ruggedness</li>
<li>Hillshade</li>
<li>Relief</li>
</ul>
<p>Now these algorithms can be used in scripts, models and for batch processing.</p></p><p><img src="/media/images/entries/f5980f4840b9c822e5a228ec03da59168cd9c5e9.png"/></p>Range vertex selection in node toolhttps://changelog.qgis.org/id/entry/669<p><p>That feature makes it possible to select a <strong>range of vertices</strong> from one feature.</p>
<p>It can be activated by pressing <strong>Shift+R</strong> - afterwards one needs to click start and final point within a feature - this will selected all vertices between the two.</p>
<p>The range selection can be cancelled anytime by right-click or by pressing Esc key.</p>
<p>For closed curves (polygons), it is possible to switch to the "longer" way around the ring by holding <strong>Ctrl</strong> while clicking the final point.</p></p><p><img src="/media/images/entries/b44524fe2864249a334cb7d21fd1a0c1d885ff15.gif"/></p>QGIS Server overhaulhttps://changelog.qgis.org/id/entry/663<p><p>As you may know, QGIS is jumping to a new major version (yes!). Doing so was made necessary because of the need to switch to python 3, QT5, but also because we needed to break the QGIS API in several places. (http://blog.qgis.org/2016/02/10/qgis-3-0-plans/) </p>
<p>A year ago, a tiny troll from switzerland rang a bell about the strong need for love server code base required. Indeed, the API was locked by some old methods of QGIS server. In short, QGIS server was reparsing the qgs project file in his own way, and created dependencies to part of QGIS we needed to drop.</p>
<p>As outsourcing the server code base was not an option, so we had to refactor it. The involved parties decided to get engaged in a code sprint in the city of Lyon, France dedicated to sharing their vision, planning the work and finally making all the following happen:</p>
<p>Higher level refactoring</p>
<p>All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, GetPrint etc..) have been rewritten. Some like WMS were entirely rewritten. Kudos to the devs!</p>
<p>New features</p>
<ul>
<li>
<p>Multi-thread rendering like in the desktop</p>
</li>
<li>
<p>A new option to trust layer metadata and thus speed up project loading</p>
</li>
<li>
<p>WFS 1.1 support https://github.com/qgis/QGIS/pull/5297 </p>
</li>
<li>
<p>Full Python bindings for the server API</p>
</li>
<li>
<p>Server Services as plugins like providers</p>
</li>
</ul>
<p>Deep, complex and unrewarding tasks</p>
<ul>
<li>
<p>Remove all singleton calls</p>
</li>
<li>
<p>Cut all the dependencies to the old QGIS project file parser</p>
</li>
<li>
<p>Minimize dependencies to GUI library. Since fonts are necessary to render maps, totally removing them was not feasable. </p>
</li>
</ul>
<p>Infrastructure tasks</p>
<ul>
<li>
<p>Build a OGC compliancy platform and integrate it to a continuous integration platform. Conformity reports are now pushed to tests.qgis.org </p>
</li>
<li>
<p>Add unit tests ... and again more unit tests</p>
</li>
<li>
<p>Stress QGIS server against security leaks (SQL injections and other malicious attacks)</p>
</li>
<li>
<p>Start profiling and bench marking performances. This work still need some love - and funding - to be achieved</p>
</li>
</ul>
<p>A presentation was given at FOSS4G-EU in July. </p></p><p><img src="/media/"/></p>Processing algorithms enhancementshttps://changelog.qgis.org/id/entry/839<p><p>Processing algorithms have been reviewed and documented. Clicking the Help button will open the QGIS website and show the algorithm description with enhanced documentation and pictures. </p></p><p><img src="/media/images/entries/ca710bbcb3e67a83217d5894ccccfcb5103b1bf4.png"/></p>Possibility to segmentize feature info geometry in serverhttps://changelog.qgis.org/id/entry/683<p><p>Many web clients can't display circular arcs in geometries. To allow such clients to still display a feature's geometry (e.g. for highlighting the feature), a new per project QGIS server option was introduced (Menu "Project" -> "Project Properties" -> "QGIS Server") to segmentize the geometry before sending it to the client in a GetFeatureInfo response.</p></p><p><img src="/media/images/entries/c6e36e36b5dc6fb0f5534ef11cb773781db4bf8c.png"/></p>Port heatmap plugin to processing algorithmhttps://changelog.qgis.org/id/entry/746<p></p><p><img src="/media/"/></p>Point cluster rendererhttps://changelog.qgis.org/id/entry/637<p><p>New symbol renderer that groups nearby points into a single rendered marker symbol. Optionally, a label displays the number of features that have been aggregated into the single symbol.</p>
<p>Additionally, some improvements have been made to the point displacement renderer, specifically: </p>
<ul>
<li>points are now assigned to the group which is "nearest" them, rather then just assigning them first group within the search distance. In some cases this was assigning features to a more distant cluster, resulting in less predictable cluster patterns</li>
<li>individual points are now correctly shown in their own selection state</li>
<li>lots of code cleanup + documentation too.</li>
</ul>
<p>For developers: QgsPointDisplacementRenderer has been split into a new pure virtual QgsPointDistanceRenderer base class which handles the detection of clusters and grouping of points. The new cluster renderer reuses this base class to avoid code duplication.</p>
<p>See the crowd <a href="https://north-road.com/qgis-cluster-renderer-crowdfunding/">funding programme</a> for more details.</p></p><p><img src="/media/images/entries/a9a26b2c7154f918f8b218c2e01f3b38f599436a.png"/></p>Plugins can provide a custom help in Expression windowhttps://changelog.qgis.org/id/entry/829<p><p>Plugins which are providing expressions can add a custom help made with HTML strings.</p></p><p><img src="/media/images/entries/ef610ef1efd507e9bf0ee905d8f8d24a40c753e5.png"/></p>Pan to current feature in attribute tablehttps://changelog.qgis.org/id/entry/672<p></p><p><img src="/media/images/entries/2f488f086cb64fb0394d1848b4a41f28f80a2adf.gif"/></p>Overhaul of the Vertex toolhttps://changelog.qgis.org/id/entry/824<p><p>The Node tool (now renamed to Vertex tool) has undergone a complete rework to make it more flexible.
Some of the more important changes are:</p>
<ol>
<li>Instead of requiring users to first select a feature and then edit its vertices in the second step,
the tool now capable of working with multiple features at the same time. It is therefore easy to
select vertices from several features and move or delete them at once. If there is a need to constrain
selection of vertices to just specific feature(s), it is possible to select the features with selection
tool first - the vertex tool will only work with vertices from selected feature(s) in such cases.</li>
<li>Instead of working just with the currently selected layer, the tool is now able to work with all
layers that are in editing mode at the same time. Moving of features that logically belong together
but are located in different layers has got much easier. Still, the current layer is respected
if there are multiple choices when picking vertices.</li>
<li>Features and their vertices get highlighted as the user moves the mouse pointer over them, giving
better visual feedback.</li>
<li>In QGIS 2.x the vertices would be moved by clicking a vertex, dragging it with the left mouse button
still pressed and finally dropping them by releasing the mouse button. This behavior has been changed
to "click-click" approach where user first clicks a vertex to pick it, then drag it without having
any mouse buttons pressed and drop it by clicking again on the final destination. The arguments
for this change were the following:</li>
<li>it is easier to precisely place nodes (not having to apply force to the mouse button all the time)</li>
<li>one does not move nodes inadvertently</li>
<li>it is possible to cancel the operation</li>
<li>it allows to pan the map by pressing space bar while the node is being moved</li>
</ol>
<p>See https://github.com/qgis/QGIS-Enhancement-Proposals/issues/69 for more information.</p></p><p><img src="/media/images/entries/c2761555d13be6b8a1893da2bd3240dd6343c9a6.gif"/></p>Optimised points along geometry algorithmhttps://changelog.qgis.org/id/entry/687<p><p>Supports also polygon geometries, handles null geometries,
and records the original line angle along with the distance
for each point.</p></p><p><img src="/media/images/entries/9b24dc337e4896a8be9b0e651e32b3dc9cb11593.png"/></p>Open layers in a single grouphttps://changelog.qgis.org/id/entry/828<p><p>If you try to open many sublayers, you can now open them all within a same group in the legend.</p></p><p><img src="/media/images/entries/a64155774fee81370dfb5a786cf7386bffb7a089.png"/></p>Offline editing: Add flag to only copy selected featureshttps://changelog.qgis.org/id/entry/699<p><pre><code>This extends the offline editing possibilities to only work on subset of
large layers
</code></pre></p><p><img src="/media/"/></p>OSM Downloader tool removedhttps://changelog.qgis.org/id/entry/836<p><p>We have removed the OSM downloader tool that was provided in 2.x releases of QGIS. We encourage you to rather use the QuickOSM plugin which is in the process of being ported to QGIS 3.0.</p></p><p><img src="/media/"/></p>New zipped project file format .qgz https://changelog.qgis.org/id/entry/813<p><p>A long time ago on the developper's mailing list, we discussed of a container storing the xml file and other ressources.
This is now possible, though it remains optional.
The auxiliary storage feature takes advantage of that by storing the associated .qgd sqlite database.
We hope that in next versions land support for embedding other resources like SVG, color ramps, datasources, images, etc...</p></p><p><img src="/media/images/entries/b954811defffce51a7375ae24c640e0d1dcf88da.png"/></p>New universal 'basic stats for field' algorithmhttps://changelog.qgis.org/id/entry/743<p><p>Replaces the existing 'Basic Stats for Numeric Fields' and
'Basic Stats for String Fields' algorithms and adds support
for date/time/datetime fields.</p>
<pre><code>Having a single unified algorithm allows more flexible models
where a field type may not be known in advance.
</code></pre></p><p><img src="/media/"/></p>New unified 'add layer' dialoghttps://changelog.qgis.org/id/entry/635<p><p>You can now use a single dialog to add a huge variety of data formats to QGIS.</p></p><p><img src="/media/images/entries/d81a5fba0df198b53ef60293ade556125499e5e8.png"/></p>New raster unique values report algorithmhttps://changelog.qgis.org/id/entry/797<p><p>A new algorithm was added to processing which returns the count and area of each unique value within a given raster layer. </p></p><p><img src="/media/images/entries/096af77b050265c85d7ee203c2ab4d974b8be126.jpg"/></p>New input type for expressionshttps://changelog.qgis.org/id/entry/731<p><p>This adds a new input type for expression inputs. Expression
inputs can be linked to a parent layer so that the builder
shows the correct fields and layer variables.</p>
<pre><code>It's designed to be used when an algorithm specifically requires an expression,
eg Select by Expression and Extract by Expression.
</code></pre></p><p><img src="/media/"/></p>New extract by expression algorithmhttps://changelog.qgis.org/id/entry/720<p><p>Filters an input layer by expression</p></p><p><img src="/media/"/></p>New expression variables for map settingshttps://changelog.qgis.org/id/entry/773<p><pre><code>- map_crs, map_crs_definition: retrieves crs details for map
- map_units: retrieves units for map (eg 'meters','degrees')
</code></pre></p><p><img src="/media/"/></p>New expression variableshttps://changelog.qgis.org/id/entry/739<p><p>Adds '@project_crs' and '@project_crs_definition' variables for retrieving the current project CRS</p></p><p><img src="/media/"/></p>New expression functionshttps://changelog.qgis.org/id/entry/680<p><p><strong>Atlas expressions</strong></p>
<ul>
<li><strong> atlas_layerid</strong> and <strong>atlas_layername</strong>: Returns layer ID and layer name of the current layer in the atlas.</li>
</ul>
<p><strong>Aggregate expressions</strong></p>
<ul>
<li><strong>array_agg(expression, group_by, filter)</strong>: Returns an array of aggregated values from a field or expression.</li>
</ul>
<p><strong>Array expressions</strong></p>
<p>New group that contains expression functions for the creation and manipulation of arrays (also known as list data structures). The order of values within the array matters, in contrary to the 'map' data structure, where the order of key-value pairs is irrelevant and values are identified by their keys.</p>
<ul>
<li><strong>array(value1, value2, …)</strong> : Returns an array containing all the values passed as parameter.</li>
<li><strong>array_append(array, value)</strong>: Returns an array with the given value added at the end.</li>
<li><strong>array_cat(array1, array2, …)</strong>: Returns an array containing all the given arrays concatenated.</li>
<li><strong>array_contains(array, value)</strong>: Returns true if an array contains the given value.</li>
<li><strong>array_distinct(array)</strong>: Returns an array containing distinct values of the given array.</li>
<li><strong>array_find(array, value)</strong>: Returns the index (0 for the first one) of a value within an array. Returns -1 if the value is not found.</li>
<li><strong>array_first(array)</strong>: Returns the first value of an array.</li>
<li><strong>array_get(array, index)</strong>: Returns the Nth value (0 for the first one) of an array.</li>
<li><strong>array_insert(array, pos, value)</strong>: Returns an array with the given value added at the given position.</li>
<li><strong>array_intersect(array1, array2)</strong>: Returns true if any element of array1 exists in array2.</li>
<li><strong>array_last(array)</strong>: Returns the last value of an array.</li>
<li><strong>array_length(array)</strong>: Returns the number of elements of an array.</li>
<li><strong>array_prepend(array, value)</strong>: Returns an array with the given value added at the beginning.</li>
<li><strong>array_remove_all(array, value)</strong>: Returns an array with all the entries of the given value removed.</li>
<li><strong>array_remove_at(array, pos)</strong>: Returns an array with the given index removed.</li>
<li><strong>array_reverse(array)</strong>: Returns the given array with array values in reversed order.</li>
<li><strong>array_slice(array, start_pos, end_pos)</strong>: Returns a portion of the array. The slice is defined by the start_pos and end_pos arguments.</li>
<li><strong>array_to_string(array, delimiter, empty_value)</strong>: Concatenates array elements into a string separated by a delimiter using and optional string for empty values.</li>
<li><strong>regexp_matches(string, regex, empty_value)</strong>: Returns an array of all strings captured by capturing groups, in the order the groups themselves appear in the supplied regular expression against a string.</li>
<li><strong>string_to_array(string, delimiter, empty_value)</strong>: Splits string into an array using supplied delimiter and optional string for empty values.</li>
</ul>
<p><strong>Color expressions</strong></p>
<ul>
<li><strong>create_ramp(map, discrete)</strong>: Returns a gradient ramp from a map of color strings and steps.</li>
</ul>
<p><strong>Date and Time expressions</strong></p>
<ul>
<li><strong>epoch(date)</strong>: Return the interval in milliseconds between the unix epoch and a given date value.</li>
</ul>
<p><strong>General expressions</strong></p>
<ul>
<li><strong>env(name)</strong>: Gets an environment variable and returns its content as a string. If the variable is not found, NULL will be returned.</li>
<li><strong>raster_statistic(layer, band, property)</strong>: Returns statistics from a raster layer. Properties: min/max/avg/range/stdev/sum</li>
<li><strong>with_variable(name, value, node)</strong>: This function sets a variable for any expression code that will be provided as 3rd argument. This is only useful for complicated expressions, where the same calculated value needs to be used in different places.</li>
</ul>
<p><strong>Geometry expressions</strong></p>
<ul>
<li><strong>extend(geometry, start_distance, end_distance)</strong>: Extends linestrings by a specified amount at the start and end of the line</li>
<li><strong>hausdorff_distance(geometry a, geometry b, densify_fraction)</strong>: Returns the Hausdorff distance between two geometries. This is basically a measure of how similar or dissimilar 2
geometries are, with a lower distance indicating more similar geometries.</li>
<li><strong>inclination(inclination(point_a, point_b)</strong>: Returns the inclination measured from the zenith (0) to the nadir (180) on point_a to point_b.</li>
<li><strong>make_circle(center, radius, segment)</strong>: Creates a circular, segmentized, polygon.</li>
<li><strong>make_ellipse(center, semi_major_axis, semi_minor_axis, azimuth, segment)</strong>: Creates an elliptical, segmentized, polygon.</li>
<li><strong>make_regular_polygon(center, radius, number_sides, circle)</strong>: Creates a regular polygon.</li>
<li><strong>make_triangle()</strong>: help still missing</li>
<li><strong>minimal_circle(geometry, segment)</strong>: Returns the minimal enclosing circle of a geometry. It represents the minimum circle that encloses all geometries within the set.</li>
<li><strong>offset_curve(geometry, distance, segments, join, miter_limit)</strong>: Returns a geometry formed by offsetting a linestring geometry to the side. Distances are in the Spatial Reference System of this geometry.</li>
<li><strong>oriented_bbox(geom)</strong>: Returns a geometry which represents the minimal oriented bounding box of an input geometry.</li>
<li><strong>pole_of_inaccessibility(geometry, tolerance)</strong>: Calculates the approximate pole of inaccessibility for a surface, which is the most distant internal point from the boundary of the surface. This function uses the 'polylabel' algorithm (Vladimir Agafonkin, 2016), which is an iterative approach guaranteed to find the true pole of inaccessibility within a specified tolerance.</li>
<li><strong>simplify(geometry, tolerance)</strong>: Simplifies a geometry by removing nodes using a distance based threshold (ie, the Douglas Peucker algorithm). The algorithm preserves large deviations in geometries and reduces the number of vertices in nearly straight segments.</li>
<li><strong>simplify_vw(geometry, tolerance)</strong>: Simplifies a geometry by removing nodes using an area based threshold (the Visvalingam-Whyatt algorithm). The algorithm removes vertices which create small areas in geometries, e.g., narrow spikes or nearly straight segments.</li>
<li><strong>smooth(geometry, iterations, offset, min_length, max_angle)</strong>: Smooths a geometry by adding extra nodes which round off corners in the geometry.</li>
<li><strong>single_sided_buffer(geometry, distance, segments, join, miter_limit)</strong>: Returns a geometry formed by buffering out just one side of a linestring geometry. Distances are in the Spatial Reference System of this geometry.</li>
</ul>
<p><strong>Layer Property</strong></p>
<ul>
<li><strong>crs_description</strong> returns the CRS description of the layer.</li>
</ul>
<p><strong>Map Expressions</strong></p>
<p>This group contains expression functions for the creation and manipulation of 'map' data structures (also known as dictionary objects, key-value pairs, or associative arrays). One can assign values to given keys. The order of the key-value pairs in the map object is not relevant.</p>
<ul>
<li><strong>map(key1, value1, key2, value2, , …)</strong>: Returns a map containing all the keys and values passed as pair of parameters.</li>
<li><strong>map_akeys(map)</strong>: Returns all the keys of a map as an array.</li>
<li><strong>map_avals(map)</strong>: Returns all the values of a map as an array.</li>
<li><strong>map_concat(map1, map2, …)</strong>: Returns a map containing all the entries of the given maps. If two maps contain the same key, the value of the second map is taken.</li>
<li><strong>map_delete(map, key)</strong>: Returns a map with the given key and its corresponding value deleted.</li>
<li><strong>map_exist(map, key)</strong>: Returns true if the given key exists in the map.</li>
<li><strong>map_get(map, key)</strong>: Returns the value of a map, given it's key.</li>
<li><strong>map_insert(map, key, value)</strong>: Returns a map with an added key/value.</li>
</ul>
<p><strong>Map Layers</strong></p>
<p>New group that contains a list of map layers available in the current project. Returns internal map layer ids. This is used in many other expression functions that reference map layers.</p>
<p><strong>Math expressions</strong></p>
<ul>
<li><strong>inclination(point_a, point_b)</strong>: Returns the inclination measured from the zenith (0) to the nadir (180) on point_a to point_b.</li>
</ul>
<p><strong>Operators</strong></p>
<ul>
<li><strong>~:</strong> Performs a regular expression match on a string value.</li>
</ul>
<p><strong>Record and Attributes Expressions</strong></p>
<p>renamed from just "Record"</p>
<ul>
<li><strong>get_feature_by_id(layer, feature_id)</strong>: Returns the feature with an id on a layer.</li>
<li><strong>is_selected(feature, layer)</strong>: Returns if a feature is selected. If called with no parameters checks the current feature.</li>
<li><strong>num_selected(layer)</strong>: Returns the number of selected features on a given layer. By default works on the layer on which the expression is evaluated.</li>
<li><strong>represent_value(value, fieldName)</strong>: Returns the configured representation value for a field value. It depends on the configured widget type. Often, this is useful for 'Value Map' widgets.</li>
<li><strong>uuid()</strong>: Generates a Universally Unique Identifier (UUID) for each row using the Qt QUuid::createUuid method. Each UUID is 38 characters long.</li>
</ul>
<p><strong>Relations</strong></p>
<p>New group listing all available table relations in a project. Useful for relation_aggregate functions.</p>
<p><strong>Deprecated</strong></p>
<ul>
<li><strong>$scale</strong>: old variable to get current map scale. Replaced by <strong>maps_scale</strong></li>
</ul>
<p><strong>Changes</strong></p>
<ul>
<li>Change in <strong>substr()</strong> function<ul>
<li>support negative start value (e.g. substr('hello',-2) returns 'lo')</li>
<li>support negative length value (e.g. substr('hello',3,-1) returns 'll')</li>
<li>length parameter now optional, defaults to end of string
(e.g. substr('hello world',7) returns 'world')</li>
</ul>
</li>
<li><strong>strpos()</strong> now relies on a simple string within a string search</li>
<li><strong>regexp_match()</strong> now returns pos of a matching regular expression</li>
</ul></p><p><img src="/media/"/></p>New color ramp button widgethttps://changelog.qgis.org/id/entry/742<p><p>In QGIS 3.0, handling of color ramps has gotten much better via a newly introduced color ramp button widget. Improvements include:
- custom color ramp settings are remembered when projects are re-opened
- color ramp inversion is implemented within the widget, enabling this action across QGIS
- quick access to "favorite" color ramps within the widget pop-up menu
- interfacing with catalogs (cpt-city and ColorBrewer) is now much more pleasant</p></p><p><img src="/media/images/entries/547ffa26f79435ff28198820bb0d95dc495b4f13.png"/></p>New algorithm to truncate tableshttps://changelog.qgis.org/id/entry/768<p><p>Irretrievably deletes all features from a table... use with caution!</p></p><p><img src="/media/"/></p>New algorithm to orthagonalize geometrieshttps://changelog.qgis.org/id/entry/747<p><pre><code>Adds a new algorithm which tries to make angles in geometries either right angles or straight lines
</code></pre></p><p><img src="/media/"/></p>New algorithm to extract specific nodeshttps://changelog.qgis.org/id/entry/723<p><p>This algorithm allows you to extract specific nodes from geometries.
Eg you can extract the first or last node in the geometry.</p>
<pre><code>The algorithm accepts a comma separated list of node indices to
extract, eg 0 = first node, 1 = second node, etc. Negative indices
can be used to extract nodes from the end of the geometry. Eg
-1 = last node, -2 = second last node.
</code></pre></p><p><img src="/media/"/></p>New algorithm to extend lineshttps://changelog.qgis.org/id/entry/722<p><pre><code>Allows extending linestrings by a set distance at the start
and end of the line
</code></pre></p><p><img src="/media/"/></p>New algorithm to compute geometry by expressionhttps://changelog.qgis.org/id/entry/726<p><p>This algorithm updates existing geometries (or creates new
geometries) for input features by use of a QGIS expression. This
allows complex geometry modifications which can utilise all the
flexibility of the QGIS expression engine to manipulate and create
geometries for output features.</p></p><p><img src="/media/"/></p>New algorithm for translating (moving) pointshttps://changelog.qgis.org/id/entry/679<p><p>Allows geometries to be shifted by a x/y displacement</p></p><p><img src="/media/"/></p>New algorithm for single sided buffershttps://changelog.qgis.org/id/entry/681<p></p><p><img src="/media/"/></p>New 'drop geometries' algorithmhttps://changelog.qgis.org/id/entry/741<p><pre><code>
Simply removes any geometries from an input layer and returns
the features with attributes only
</code></pre></p><p><img src="/media/"/></p>Network analysis algorithmshttps://changelog.qgis.org/id/entry/752<p><p>add shortest path and service area algorithms to Processing</p>
<p>also allow calculating shortest path from a point to all points in a layer, or from all points in a layer to an end point. And creating service areas for all points in a layer.</p>
<p>Roadgraph plugin has been removed as a result.</p></p><p><img src="/media/"/></p>NEW MAP COLORING ALGORITHMS IN QGIS 3.0https://changelog.qgis.org/id/entry/668<p><p>see <a href="http://nyalldawson.net/2017/02/new-map-coloring-algorithms-in-qgis-3-0/">http://nyalldawson.net/2017/02/new-map-coloring-algorithms-in-qgis-3-0/</a></p></p><p><img src="/media/images/entries/1a507363f0c35065d8c2751e167531b96600d700.png"/></p>Move feature now benefits from Advanced Digitizinghttps://changelog.qgis.org/id/entry/678<p><p>Just move a feature using the new "click - click ergonomy" and use the advanced digitizing panel and shortcut to constraint angles, distances, exact XY.</p></p><p><img src="/media/"/></p>More non-blocking, inline editinghttps://changelog.qgis.org/id/entry/686<p><ul>
<li>map unit scaling</li>
<li>color brewer and limited random ramp editors</li>
<li>editing colors in a color list inline in the style panel</li>
<li>inline editing of colors and symbols in composer</li>
</ul>
<p>now shown inline in style panel</p></p><p><img src="/media/"/></p>More help and possibility to configure location of the QGIS help fileshttps://changelog.qgis.org/id/entry/770<p><p>More Help buttons for algorithms and dialogs are added and now pointing to the online QGIS Documentation.</p>
<p>Configuration allows to access context help stored online, in the organization network or on local computer. Also it is possible to combine different help sources.</p></p><p><img src="/media/images/entries/7c17e43c0c6738c9588f3bef149ca7f3d8a13948.png"/></p>More data definable controlshttps://changelog.qgis.org/id/entry/778<p><p>Item <strong>frame</strong> and <strong>background colors</strong>
Data defined <strong>svg colors and outline width for composer picture items</strong> (Especially useful when the picture is showing a north arrow!)
Data defined <strong>legend titles and column count</strong>
Data defined <strong>scalebar colors and line width</strong></p></p><p><img src="/media/"/></p>Migrate Photo, WebView and FileName widgets to Attachmenthttps://changelog.qgis.org/id/entry/776<p></p><p><img src="/media/images/entries/d2e949a9804de76d196af6e58996165d01350fec.jpeg"/></p>Metadata overhaulhttps://changelog.qgis.org/id/entry/653<p><p>The metadata system in QGIS has been overhauled. In QGIS 3.0 we introduce our own internal, formalised metadata schema which is separate from the QGIS project file format. We introduce new API capabilities for reading and writing metadata for layers. We have separated the display of metatadata from the editing and have added a new metadata editing tool. Metadata are currently saved in the project file. It can also be saved as an XML file alongside file based layers or in a local sqlite database for remote layers (e.g. PostGIS).</p>
<p>you can read more about the design considerations adopted in this work by referring to the QGIS Enhancement Proposal (QEP) - <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/91">QEP-92</a></p>
<p>Please note this is the first phase in the development of a complete and standards compliant metadata infrastructure for QGIS. We are seeking further funding to implement a more complete implementation for the metadata system - see <a href="https://docs.google.com/document/d/1twE8J345Sz1rk1z34672eqlEiL2mJT4bZbuF5oRTCoM/edit?usp=sharing">this document</a> for details of future planned work packages that need funding.</p>
<p>The specification for the QGIS metadata schema is <a href="https://github.com/qgis/QGIS/blob/master/resources/qgis-resource-metadata.xsd">here</a>.</p>
<p>The primary funder for this work was <a href="https://www.gfdrr.org">The WorldBank/GFDRR</a> with supporting funding provided by <a href="https://www.nina.no/english">NINA</a>.</p></p><p><img src="/media/images/entries/a26adc99ea62733e65222769095537e3be3fb29a.png"/></p>Map of CRS-extent in Project properties https://changelog.qgis.org/id/entry/807<p></p><p><img src="/media/images/entries/d56d5d68aff5b7f10999751041490769b79e619d.png"/></p>Map Composer Overhaulhttps://changelog.qgis.org/id/entry/620<p><p>This is a major rework to how compositions are managed in the code of QGIS.</p>
<p>Highlights are:</p>
<ul>
<li>
<p>A new QgsLayoutManager class which is used for storage and serializing/deserializing of compositions. A QgsLayoutManager is attached to QgsProject. This allows core code to access the compositions attached to a project. All handling of compositions has been moved from app to core, making it easy for server (and other non-app based projects. QField/roam?) to access project compositions without resorting to fragile xml parsing.</p>
</li>
<li>
<p>Composer windows are created on demand and destroyed on close. This avoids the heavy requirement of creating all composer windows and widgets for every single composer item when loading projects. <strong>It was the main reason loading projects with compositions were so slow previously</strong>. Now, composer windows are created only when the window is opened and destroyed when the window is closed. Composer item configuration widgets are also only created on demand (when an item is selected) instead of precreating all widgets.</p>
</li>
<li>
<p>A side benefit of destroying composer windows on close is that <strong>we now no longer suffer from a Qt bug</strong> which blocked use of floating docks in composer windows. Now you can float the item/composition/etc panels! Much nicer for full screen working with compositions on multi-monitor setups.</p>
</li>
<li>
<p><strong>Reworked API for working with composers through iface</strong>. Since composer windows don't exist unless they are currently open, all the iface methods for interacting with composers have been redone to make it clear that they only apply to open windows. Additionally, a simple composer interface which provides a stable API for plugins and scripts to work with composer windows has been added. Very basic for now, but in future we can extend with more hooks to allow plugins to interact with composer windows.</p>
</li>
<li>
<p>Lots of code cleanups and removal</p>
</li>
</ul>
<p>More info at <a href="https://north-road.com/qgis-layout-and-reporting-engine-campaign/">https://north-road.com/qgis-layout-and-reporting-engine-campaign/</a></p></p><p><img src="/media/images/entries/fa298be4fea348f58b9bd2f4bea30f2e7f1c2ee5.png"/></p>Locator barhttps://changelog.qgis.org/id/entry/786<p><p>The Locator bar is a fast, always ready, generic and pluggable search facility in the Left Bottom corner of QGIS.</p>
<p>Currently it is able to search for algorithms, actions and layer names, but also to select a feature in current active layer by typing an attribute value.</p>
<p>It is 'easy' extendable, so everybody can create a QgsLocatorFilter for his/her national geocoding service or other search online or database search facility.</p></p><p><img src="/media/images/entries/c5eba5f5e5a6745d1a81df88eb55f01a68fcc1ad.gif"/></p>Load/save style in database for GPKG and Spatialitehttps://changelog.qgis.org/id/entry/718<p></p><p><img src="/media/"/></p>Live layer supporthttps://changelog.qgis.org/id/entry/621<p><p>QGIS 3.0 now supports live layers. These layers get re-rendered automatically at a time interval that you determine, in a clean and flicker free way. Live layers are great for tracking continuously changing data like a fleet of cars, a flock of birds that you have telemetry data for and so on.</p></p><p><img src="/media/images/entries/5a9cd3df6f804b903fee30a08f7018887c1d8710.gif"/></p>Interpolation algorithmshttps://changelog.qgis.org/id/entry/711<p><p>expose IDW and TIN interpolation from Interpolation plugin in toolbox</p>
<p>Interpolation plugin has been removed as a result</p></p><p><img src="/media/"/></p>Improved processing modeler windowhttps://changelog.qgis.org/id/entry/767<p><p>The processing modeler window has received a lot of attention for this release. Improvements include:
- zoom controls in the window's toolbar
- customization of inputs and algorithms panels' location
- panels can now float above the processing window</p></p><p><img src="/media/images/entries/d7d74d9113516f51289380755f1862324c83feb5.png"/></p>Improved map canvas' save as imagehttps://changelog.qgis.org/id/entry/798<p><p>The map canvas' save as image function has been expanded and now offers users the possibility to tweak the scale, resolution, and extent on-the-fly. Extents can be restricted to a height-width ratio. A save as PDF function was also added to quickly export the map canvas into a resolution-independent PDF. </p></p><p><img src="/media/images/entries/a2adf1e9930f23fa739e68a6e2c55e1b553867b9.png"/></p>Improved handling of defaultshttps://changelog.qgis.org/id/entry/736<p><p>Improve handling of defaults (inc provider default clauses, literal defaults, and QGIS expression defaults) and automatically handle unique value constraints on layers</p>
<p>Any fields with unique value constraints will be guaranteed to have a value which is unique to the field.</p>
<p>This also means that after certain editing operations (e.g. copy-paste, split features etc.) attributes will now be set to their default value, if applicable.</p></p><p><img src="/media/"/></p>Improved consistency to the user interfacehttps://changelog.qgis.org/id/entry/636<p><p>This work sponsored by the QGIS grant program on "adding consistency to UI controls" is now complete and merged into master. The following tasks were done as part of this
work:</p>
<ul>
<li>All API regarding <strong>transparency/opacity/alpha</strong> was standardised to <strong>setOpacity()</strong> and <strong>opacity()</strong>. The methods take a double value between 0 (transparent) and 1 (opaque), keeping consistency with the Qt API.</li>
<li>A <strong>new widget QgsOpacityWidget</strong> was created, and is now used everywhere through the UI where opacity is set. This ensures consistent behavior and look for opacity controls everywhere.</li>
<li><strong>Rotation</strong> has been standardised in the API and UI, so now rotation is always applied clockwise. All rotation widgets have been updated so they accept values from -360 to 360.</li>
<li>2.x Projects with labeling using rotation and data defined rotation are transparently <strong>upgraded</strong> upon opening in 3.0</li>
<li>Scale APIs have been made consistent throughout the QGIS API. <strong>The confusing mix of scale denominators vs real scales has been removed</strong>, with everything now operating on scale denominators. The behaviour of all scale range calls is standardised with a common meaning for min/max scales (and explicit api documentation regarding this)</li>
<li>All scale controls now use the standard scale widgets for consistency across the UI</li>
<li>Labeling now uses the same definition for min/max scale as the rest of the UI, and existing projects are transparently upgraded on opening in 3.0.</li>
<li>Fixed most outstanding bugs relating to scale usage, including bugs breaking the rule based scale limits</li>
</ul>
<p>Thanks to the QGIS PSC and project donors for sponsoring this work and allowing it to proceed!</p></p><p><img src="/media/"/></p>Holding shift while drawing polyline/polygon constrains line angleshttps://changelog.qgis.org/id/entry/779<p></p><p><img src="/media/"/></p>Hide Deselected Layers actionhttps://changelog.qgis.org/id/entry/763<p><p>Allows you to quickly hide all deselected layers. This is very handy when you have a large project and want to quickly hide all except for a couple of layers</p></p><p><img src="/media/images/entries/a8419d6027de9351afa6f8a99700509b24cc7418.png"/></p>Grid renderer for points displacementhttps://changelog.qgis.org/id/entry/816<p><p>Grid renderer for points displacement</p></p><p><img src="/media/images/entries/0247dfa555b6a80139f399b69071a2cc9bd278b3.png"/></p>Geometry class updateshttps://changelog.qgis.org/id/entry/671<p><p>There has been a major overhaul of the geometry classes in QGIS. The old classes have been renamed (as per the table below). New geometry classes will properly preserve Z and M attributes if present.</p>
<p>References https://github.com/qgis/qgis3.0_api/issues/11</p>
<p>This finally brings back a consistent state in naming within the geometry API</p>
<h1>Renames</h1>
<p>| QGIS 2 | QGIS 3 |
|--------------------|--------------------|
| QgsPolygon | QgsPolygonXY |
| QgsMultiPoint | QgsMultiPointXY |
| QgsMultiPolyline | QgsMultiPolylineXY |
| QgsMultiPolygon | QgsMultiPolygonXY |
| QgsPolygonV2 | QgsPolygon |
| QgsMultiPointV2 | QgsMultiPoint |
| QgsMultiPolylineV2 | QgsMultiPolyline |
| QgsMultiPolygonV2 | QgsMultiPolygon |</p>
<p>See also https://github.com/qgis/QGIS/pull/5491</p></p><p><img src="/media/"/></p>GeoPackagehttps://changelog.qgis.org/id/entry/664<p><ul>
<li>processing uses pkg by default</li>
<li>save as uses pkg by default</li>
<li>create new layer uses pkg by default</li>
<li>browser drag and drop import layers</li>
</ul></p><p><img src="/media/"/></p>GeoNode integrationhttps://changelog.qgis.org/id/entry/652<p><p><a href="http://geonode.org">GeoNode</a> is an open source geospatial content management system that makes it easy to publish geospatial data on the web. QGIS 3.0 includes new functionality that will allow you to very easily add a GeoNode instance to the browser tree and add any layers from that site to your project as WMS, WFS or XYZ. There is no need to dig around trying to figure out WMS/WFS end points, QGIS will do everything for you. When using WMS and XYZ Tiled layers, the style of the published GeoNode layer will be used. </p>
<p>If the GeoNode instance uses the QGIS Server backend rather than a GeoServer backed, you can copy and paste styles from the server and apply them to your local layer so that your WFS layer renders exactly as it does on the server (as shown in the animated GIF here). </p>
<p>There are also python bindings so that you can add GeoServer layers to QGIS from your plugins. If you are interested in running your own GeoNode with QGIS Server backend please see <a href="https://github.com/kartoza/kartoza-rancher-catalogue/blob/master/README.md">this site</a> for details on how you can do that using docker and rancher.</p></p><p><img src="/media/images/entries/8f23a63a25a4ad14c8a35ccf52029aa8f8c96379.gif"/></p>Generic centroid algorithmhttps://changelog.qgis.org/id/entry/677<p><p>Reworked centroid algorithm which handles non-polygon layers</p></p><p><img src="/media/"/></p>GDALTools moved to Processinghttps://changelog.qgis.org/id/entry/759<p><p>GDALTools plugin has been removed.</p>
<p>All functions previously available through the GDALTools plugin were moved to the QGIS Processing framework, allowing to use these tools in scripts, models and execute them in batch processes. Additionaly we updated the algorithms with new parameters, introduced in latest GDAL versions and improved overall UI/UX by exposing some advanced parameters like creation options, NODATA value settings etc.</p></p><p><img src="/media/images/entries/ee1c51737225b6dac80a044f272319534fee2832.png"/></p>Field constraints can be enforced or nothttps://changelog.qgis.org/id/entry/725<p><p>Non-enforced constraints just show a warning to the user, but do not prevent committing the feature. Enforced constraints block users from committing non compliant features.
So we have soft warnings now!
Any constraints detected by the provider are always enforced.</p></p><p><img src="/media/images/entries/da468dc209eb7e7da3696ee26850af6b9017312c.png"/></p>Extract by attribute can extract for null/notnull valueshttps://changelog.qgis.org/id/entry/737<p><p>Adds support for filtering where an attribute value is null or not null</p></p><p><img src="/media/"/></p>Expose @parent variable in aggregate functionshttps://changelog.qgis.org/id/entry/719<p><p>This makes it possible to access attributes and geometry from the parent feature when in the filter of the "aggregate" expression function.
With this in place aggregates can be calculated per feature.</p>
<pre><code>E.g. max "measurement" for each point_station per polygon_research_area.
</code></pre>
<p>Or a default attribute value when digitizing features:</p>
<p><code>aggregate(layer:='countries', aggregate:='max', expression:=\"code\", filter:=intersects( $geometry, geometry(@parent) ) )</code></p></p><p><img src="/media/images/entries/7666e6f1fd7a95ec3e099c27c6bf9ef6b145c956.jpeg"/></p>Export processing models as PDF/SVGhttps://changelog.qgis.org/id/entry/765<p><p>In addition to exporting processing models as bitmap images, it is now possible to export processing models as resolution-independent PDFs and SVGs. This allows for high-resolution export of models which can be embedded into papers and books being published.</p></p><p><img src="/media/images/entries/0ad81df99f01b91d2421263ad35fdc4430c483e0.jpg"/></p>Enable tabbed floating dockshttps://changelog.qgis.org/id/entry/701<p><p>For qt > 5.6 builds, it is possible to drop several floating docks in the same floating window where they appear as tabs
<a href="https://woboq.com/blog/qdockwidget-changes-in-56.html">https://woboq.com/blog/qdockwidget-changes-in-56.html</a></p></p><p><img src="/media/images/entries/02137f3073c3f8a32bc505bd4916a8df751db79f.gif"/></p>Easy styling of discrete rastershttps://changelog.qgis.org/id/entry/841<p><p>In QGIS 3.0, the existing raster Paletted Renderer for rasters was adapted to allow for easy styling of discrete raster layers, such as landcover or boolean rasters. Now, users can select the renamed "Paletted/Unique Values" renderer and click the "Add Unique Values" button to load all unique raster values from the layer. These are automatically assigned a color using the selected color ramp.</p>
<p>The unique value calculation is performed in a background thread to keep the UI responsive for large (or remote) raster layers. Additionally, users can manually add individual new classes as desired, and edit the associated pixel value for any existing class. Deleting multiple classes at once is also supported, as well as changing the color, transparency and labels for multiple classes at once.</p>
<p>Color palettes can be loaded from a text file, with ESRI clr/GDAL/GRASS color table formats supported. Color palettes can be saved to a clr text file for sharing.</p></p><p><img src="/media/images/entries/536a7bce4d526e2d5fbeeb3189de6f60b2d79256.png"/></p>Drag'n'drop layers from layer tree view to browser dockhttps://changelog.qgis.org/id/entry/684<p><p>Makes it easy to e.g. store your temporary layers in PostGIS</p></p><p><img src="/media/"/></p>Drag qpt to QGIS to create new composer from templatehttps://changelog.qgis.org/id/entry/708<p></p><p><img src="/media/"/></p>Download a file from Processinghttps://changelog.qgis.org/id/entry/815<p><p>Download a file from Processing.
Query a remote API to get a geojson</p></p><p><img src="/media/"/></p>Detect literal default values for spatialite providerhttps://changelog.qgis.org/id/entry/730<p></p><p><img src="/media/"/></p>Data dependencies between layershttps://changelog.qgis.org/id/entry/690<p><p>This allows to declare data dependencies between layers. A data
dependency occurs when a data modification in a layer, not by direct
user manipulation may modify data of other layers.
This is the case for instance when geometry of a layer is updated by a
database trigger after modification of another layer's geometry.</p></p><p><img src="/media/"/></p>Data defined symbol layer visibilityhttps://changelog.qgis.org/id/entry/710<p><p>Adds a data defined override to control a symbol layer's
visibility. Allows users to disable drawing certain symbol layers
for matching features.</p></p><p><img src="/media/"/></p>Data definable propertieshttps://changelog.qgis.org/id/entry/777<p><p>Add support for more data definable properties to diagrams:</p>
<ul>
<li>Distance</li>
<li>Priority</li>
<li>ZIndex</li>
<li>IsObstacle</li>
<li>Show</li>
<li>AlwaysShow</li>
<li>Diagram Start Angle</li>
</ul></p><p><img src="/media/"/></p>Custom labelling toolbar is now always enabledhttps://changelog.qgis.org/id/entry/812<p><p>Thanks to the awesome <strong>auxiliary data storage</strong> and the editable joined table, the manual label customization is now always enabled. You do not need anymore to add dedicated fields in your datasource to change labels position, rotation, or any of the possible settings for labels to activate the toolbar.
<strong>No more copy of readonly datasources and so much faster labeling !</strong> </p>
<p><strong>Be warned</strong>, labels are <strong>only saved along with your project file</strong> in a .qgd sqlite database, or inside the .qgz zipped project file if you chose that format.
Don't forget to share that .qgd file if you want to share your project file. </p>
<p>And for power users, the old way of having data defined fields in your datasource is still there. Just define them in the layer's properties as before!</p></p><p><img src="/media/images/entries/546a77b230bf9b0b28bf61bb231b78cbb6bd5b5f.png"/></p>Create attribute index support for spatialite providerhttps://changelog.qgis.org/id/entry/744<p><p>Allows creation of attribute indexes for spatialite layers</p></p><p><img src="/media/"/></p>Create attribute index algorithmhttps://changelog.qgis.org/id/entry/738<p><p>Allows creation of an index on an attribute in a layer for faster
attribute based filtering</p>
<pre><code>Support depends on the underlying data provider for the layer
</code></pre></p><p><img src="/media/"/></p>Control over drawing of composer table grid horizontal & vertical lineshttps://changelog.qgis.org/id/entry/707<p><p>It is now possible to independently control horizontal and vertical line rendering of composer table items. This added flexibility expends the styling possibilities of this item directly within QGIS.</p></p><p><img src="/media/images/entries/ac1b2079c9e6c19747322d246d666df7e3c4ac0d.jpg"/></p>Control over annotation contents marginshttps://changelog.qgis.org/id/entry/780<p><p>Allows setting left/top/right/bottom margins for the contents
within an annotation.</p></p><p><img src="/media/"/></p>Color setting for map canvas north arrow decorationhttps://changelog.qgis.org/id/entry/799<p><p>Color setting has been added for all map canvas north arrow decoration. </p></p><p><img src="/media/images/entries/6a3fa6fb065a02defaa42440f301847e8fbbeb75.jpg"/></p>Change of ergonomy of the visibility of layers inside groupshttps://changelog.qgis.org/id/entry/766<p><ul>
<li>Checking/unchecking a group doesn't change the check state of its children. A node is visible if and only if it is checked and all its parents too.</li>
<li>There is no more a semi-checked state for a group</li>
<li><strong>Ctrl-clic</strong> on a unchecked group will check the group and all its descendants.</li>
<li>Clic on a unchecked layer will check the lager and all its parents.</li>
<li>Ctrl-clic on a checked group will uncheck the group and all its descendants.</li>
<li>Ctrl-clic on a checked layer will uncheck the layer and all its parents.</li>
<li>Those actions are available in contextual menu items in the tree view.</li>
<li>Invisible layers because they or their parent(s) is unchecked are greyed out.</li>
</ul></p><p><img src="/media/"/></p>Cache labeling result to avoid unnecessary redraws when refreshing canvashttps://changelog.qgis.org/id/entry/784<p><p>This change allows the labeling results to be cached to an image following a map render. If the cached label result image can be reused for the next render then it will be, avoiding the need to redraw all layers participating in the labeling problem and resolving the labeling solution.
Basically this means that <strong>canvas refreshes as a result of changes to any NON-LABELED layer are much faster</strong>. (Changing a layer which is part of the labeling solution still requires all labeled layers to be completely redrawn)</p></p><p><img src="/media/"/></p>Better support for Z/M dimensions and curved geometrieshttps://changelog.qgis.org/id/entry/694<p><p>Many more algorithms now respect Z/M values and do not discard this information, and additionally many algorithms now correctly maintain curved geometries without forced segmentization of these geometries.</p></p><p><img src="/media/"/></p>Auxilliary Storage Supporthttps://changelog.qgis.org/id/entry/666<p><p>A new tab is available in vector layer properties to manage auxiliary storage : </p>
<p>A new action <em>Store data in the project</em> is available in the data defined menu providing an easy way to manage auxiliary data for a property : </p>
<p>Auxiliary data is stored in a sqlite database and managed thanks to the OGR data provider (instead of the spatialite provider) to keep as small as possible the database file. This database file (with extension <em>.qgd</em>) is either saved just next to the project file or directly embedded within the new <em>.qgz</em> format.</p>
<p>See the original <a href="https://github.com/qgis/QGIS/pull/5086">pull request</a> and this article <a href="http://oslandia.com/en/2017/10/17/auxiliary-storage-support-in-qgis-3/">which explains more</a></p></p><p><img src="/media/images/entries/f0fded6f5276d4b7e51b11834bad3d615e2b4f2d.png"/></p>Annotations can be styled using fill symbol styleshttps://changelog.qgis.org/id/entry/781<p><p>This changes the rendering of annotation frames to use QGIS' symbology
engine, which means that all the existing fill styles can now be
used to style annotation frames.</p>
<pre><code>Also paint effects & data defined symbol parameters.
</code></pre></p><p><img src="/media/"/></p>Angle threshold for smooth algorithmhttps://changelog.qgis.org/id/entry/693<p><p>Add option to QgsGeometry::smooth to not smooth
segments shorter than a certain threshold or sharp corners
with an angle exceeding a threshold</p></p><p><img src="/media/"/></p>Allow symbol layers to be temporarily disabledhttps://changelog.qgis.org/id/entry/709<p><p>Adds a new checkbox at the bottom of each symbol layer's properties which allows you to control whether the layer is enabled or not.
Disabled layers are not drawn, but are saved and can be enabled at a later stage.
This makes it easier to tweak symbol appearance without having to totally delete a symbol layer.</p></p><p><img src="/media/images/entries/555204a38e13852e4717179a9981cb522244613a.png"/></p>Allow label font size in mm/pixelshttps://changelog.qgis.org/id/entry/715<p></p><p><img src="/media/"/></p>Allow customization of line spacing for composer legend item labelshttps://changelog.qgis.org/id/entry/751<p></p><p><img src="/media/"/></p>Allow controlling labels for individual edit widgetshttps://changelog.qgis.org/id/entry/682<p><p>In the drag and drop designer, a double click on an item will allow
controlling if the label should be shown for each item individually.</p></p><p><img src="/media/"/></p>Allow configuring link/unlink feature buttons on relation editor widgethttps://changelog.qgis.org/id/entry/702<p></p><p><img src="/media/"/></p>Allow choice of CRS for map itemshttps://changelog.qgis.org/id/entry/775<p><p>This allows the CRS for map items to differ from the canvas/project
CRS. It also allows different map items to have different CRS,
eg an overview map can be set to a different CRS to the main map.</p></p><p><img src="/media/"/></p>Added functionnality to copy/move feature to move feature map toolhttps://changelog.qgis.org/id/entry/733<p><p>This allow to duplicate feature and move them in one move from a selected feature</p></p><p><img src="/media/images/entries/eea327329365ad80c7fc3363ad0fb455fc9d4335.png"/></p>Add zoom to features and flash features shortcuts in select by form dialoghttps://changelog.qgis.org/id/entry/757<p><pre><code>Allows very quick navigation and identification of features which match the criteria
in the form
</code></pre></p><p><img src="/media/"/></p>Add support for user profileshttps://changelog.qgis.org/id/entry/639<p><p>All user settings/plugins, etc are now loaded from the app data location for each platform and no longer .qgis3/2. Settings and plugins in each profile are now isolated from each other.</p>
<p>This allows for different runtime setups depending on what the user needs, e.g test, prod, demo, etc</p>
<p>Profile menu allows for switching between profiles or creating new ones.</p></p><p><img src="/media/images/entries/82d90b2a02b84584279b5e2b75774631a0cd4a44.jpeg"/></p>Add support for fine-resolution mouse wheel zoominghttps://changelog.qgis.org/id/entry/750<p><p>Some mouse / pointer devices (notably on mac) have finer resolutions. They send mouse wheel events at a high frequency but with smaller delta values. Zooming with such devices was unusable for fast zoom actions. This has been fixed in 3.0.</p></p><p><img src="/media/"/></p>Add support for arrayshttps://changelog.qgis.org/id/entry/697<p><p>Supported by postgres, spatialite</p></p><p><img src="/media/"/></p>Add layer scoped actionshttps://changelog.qgis.org/id/entry/735<p><p>Within the attribute table, there is a new button to trigger actions
which are not based on individual features but instead on the whole layer.
Normally they will perform actions based on all features or the selection.</p></p><p><img src="/media/"/></p>Add default Z value optionhttps://changelog.qgis.org/id/entry/758<p><p>Create Geopackages/Shapefiles: Now with the option to have Z-values</p></p><p><img src="/media/images/entries/80e8c78a1b38dfde5120144fac7354e800b9daff.png"/></p>Add choice of simplification method to simplifyhttps://changelog.qgis.org/id/entry/691<p><p>This change allows users to choose which method to use when running
the simplify geometries algorithm, with choices of the existing
distance based (Douglas Peucker) algorithm, area based (Visvalingam)
algorithm and snap-to-grid.</p>
<pre><code>Visvaligam in particular usually results in more cartographically
pleasing simplification over the standard distance based methods.
</code></pre></p><p><img src="/media/"/></p>Add between/not between to numerical fields in select by formhttps://changelog.qgis.org/id/entry/762<p></p><p><img src="/media/images/entries/4bfb34794edbff35e6336c165993278e9a515644.jpeg"/></p>Add auto-discovery of relations for PostgresQLhttps://changelog.qgis.org/id/entry/703<p></p><p><img src="/media/"/></p>Add an option to show user color schemes menushttps://changelog.qgis.org/id/entry/673<p><p>This adds the ability for users to set whether a user created color scheme should show up in the color button drop-down menus.</p>
<p>It's accessed through the color picker dialog, on the lists tab. Just add a new color scheme, then from the scheme menu tick the new "show in buttons" option.</p>
<p>This is handy if you have sets of common palettes and want them to be instantly available through the color menu.</p></p><p><img src="/media/"/></p>Add Points and Inches to available symbol unitshttps://changelog.qgis.org/id/entry/714<p></p><p><img src="/media/"/></p>API to allow drag'n'drop of custom browser itemshttps://changelog.qgis.org/id/entry/675<p><p>QgsDataItem implementations may provide hasDragEnabled(), mimeUri()
and QgsCustomDropHandler implementation to deal with drop of custom items.</p></p><p><img src="/media/"/></p>3D renderers for map layershttps://changelog.qgis.org/id/entry/822<p><p>In the default configuration, map layers are rendered into 2D map images on top of the terrain.
It is however possible to make better use of the 3D world by configuring 3D renderers for some map layers.
With 3D renderers, the data can be displayed in 3D views as true 3D objects - this is currently supported
for vector layers (all geometry types - point, line or polygon). This enables much better visualization,
for example:</p>
<ul>
<li>polygons with building footprints may be extruded (possibly with data-defined height) to achieve 3D look</li>
<li>points with tree point locations can be rendered with 3D symbols of trees (simple geometric shapes or existing 3D models loaded from a supported file format)</li>
</ul>
<p>To configure 3D renderers, use layer styling dock widget or the vector layer properties dialog - there is a new tab for configuration of 3D renderers.</p></p><p><img src="/media/images/entries/311f1b52d068ccca9ef74f9ea1dcba259c7ed674.png"/></p>3D map view and terrain generationhttps://changelog.qgis.org/id/entry/821<p><p>We have a brand new native 3D map view in QGIS! The 3D map view displays 2D map (rendered from project layers) on top
terrain. By default the terrain is a flat plane, but it is possible to use raster layers with digital elevation model
as the source of height data.</p>
<p>Use menu View > New 3D Map View to add a 3D view of the project. This will create a new dock widget with 3D map canvas.
The 3D view uses the same controls like 2D map views to browse the map using mouse (drag map to move it around, mouse wheel to zoom)
or keyboard arrow keys. In addition there are camera controls specific to 3D views: it is possible to rotate and tilt camera
by one of the following ways:</p>
<ul>
<li>by dragging the mouse with middle mouse button pressed</li>
<li>by pressing Shift and dragging the mouse with left mouse button pressed</li>
<li>by pressing Shift and using up/down/left/right keys</li>
</ul></p><p><img src="/media/images/entries/86e6303419d84812266eada5327e74dbc6d507a4.jpg"/></p> New algorithm for offsetting lineshttps://changelog.qgis.org/id/entry/676<p></p><p><img src="/media/"/></p> New "preset" colors color ramp optionhttps://changelog.qgis.org/id/entry/698<p><p>Allows use of a color ramp consisting of a list of selected colors. Currently there's no way in QGIS to classify a renderer using some list of colors you've previously selected. So you can modify the colors manually after classifying, but that's a pain if you're regularly using the same color scheme.
Basically, it's like the color brewer color ramp options but allowing users to pick their own preset list of colors to use<em>
(</em>Because Cynthia Brewer isn't the only cartographic color expert!)</p></p><p><img src="/media/images/entries/ea1e2fe7215ea888b9de00329e230f6b665610a6.png"/></p>