accept numeric, file and table field inputs in modeler
This allows a non-string parameter to be reused as a string
parameter in contexts where it makes sense.
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.
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.
This algorithm allows you to extract specific nodes from geometries.
Eg you can extract the first or last node in the geometry.
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.
Adds supports for "layerid" when present.
Drop special handling for "table=" portions found in URI,
making the code more generic.
Includes testcase.
Fixes#15698 - import geodatabase to postgis via processing
Now it uses the standard QgsVectorLayer.uniqueValues() method
where possible so that provider side optimisations are used
Also add test, and optimise request when using selected
features only
Method was iterating over ever feature in a layer, including
geometries and all attributes for EVERY attribute requested
Add test and refactor so only one optimised iteration (eg no
geometry, only required attributes) is used
segments shorter than a certain threshold or sharp corners
with an angle exceeding a threshold
Expose the angle threshold to processing smooth algorithm
Also:
- optimise QgsGeometry::smooth for new geometry classes
- Fix smooth does not work with geometries containing Z/M
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.
Visvaligam in particular usually results in more cartographically
pleasing simplification over the standard distance based methods.
