* [FEATURE] Allow customization of the items show is browser. User can select in Interface Customization dialog to hide some of the items in the browser panel
Funded by Limerick City and County Council
Takes an input layer, existing field and a new name for the field, and
outputs a new layer with the selected field renamed.
While this result could also be achieved with the Refactor Fields
algorithm, Refactor Fields isn't particularly model friendly. It
relies on a constant, fixed table structure, and can't adapt to
input tables with different field structures.
In constrast, this simple Rename Field algorithm adapts nicely for
model use, because it operates on a single field only and leaves
all the other fields untouched.
operation is in progress
This causes the status bar coordinates widget to show nonsense coordinates
during the pan operation. The cursor world position ISN'T changing during
a pan operation, it stuck to a fixed location!
to take attributes from matching feature with largest area of overlap only
This allows for easy polygon->polygon joins, where you expect there to be
only a single matching feature and don't want to include features which
are just touching or have just tiny sliver polygon overlaps.
Sponsored by SMEC/SJ
Allows for creation of tables with contents manually entered by users
(i.e. spreadsheet style), so that users can create completely custom
tables.
Supports control custom cell contents, foreground and background colors.
Fixes a regression bug accidentally introduced with 40134d6473fcdbd8b6f53c3ea3db01e2dd606419 (PR #8968) and backported with a887b7d34bfa44a8400bcaa986ede96e15a760c9 (PR #9231): when there are multiple output parameters processAlgorithm incorrectly generates multiple saga_cmd commands, instead of a single command containing the output parameters.
Fixes#33658
So far we used a fixed vertical range for 3D bounding boxes with range [0, 500]
This of course would not work well if Z values are outside of this range
(e.g. tiles may not show at all or get pruned prematurely)
The approach now is to start with an estimate of the vertical range based
on few features from the source vector layer and then once our tile is completely
loaded, update the 3D bounding box to better represent the actual 3D extent.
QGIS Server throw an exception if the project has bad layers, but the user can defined restricted layers which are unpublished layers.
So restricted layers can be bad layers server side, it is not necessary an error.
This code verified that the bad layers are not restricted. If the project contains unrestricted bad layers, the server throw an exception.
