The existing concave hull algorithm is quite restrictive as it
forces operation on an entire layer, which makes it useless eg
to create concave hulls from service area outputs.
Rename the existing one to "concave hull (by layer)", and make
sure all the documentation explains this so its more predictable
for users.
It doesn't make sense to force a single cost for all input points, so
make this parameter dynamic so that the cost can be eg taken from
an input layer field
Fixes#62004
Based on tickets/stackexchange posts/mailing list activity, this
seems to be a highly in demand tool which is fragile and error
prone when run via the SAGA Processing Plugin.
Port to a native tool to avoid this situation, and give a nice
optimised out-of-the-box tool.
Note that this is functionally a 1:1 clone of the SAGA tool. I've
verified that the outputs match SAGAs outputs, but any bugs
present in the SAGA implementation will also be present here.
This algorithm extracts point features corresponding to the minimum
and maximum pixel values contained within polygon zones.
The output will contain one point feature for the minimum and one
for the maximum raster value for every individual zonal feature
from a polygon layer.
This algorithm extracts extrema (minimum and maximum) values
from a given band of the raster layer.
The output is a vector layer containing point features for
the selected extrema, at the center of the associated pixel.
If multiple pixels in the raster share the minimum or maximum
value, then only one of these pixels will be included in the output.
The algorithm uses raster iterator to remain efficient on huge
rasters, and does not require reading the entire raster to
memory
The inputs we use for these run tests have open options, and now
that we are respecting these and passing them to the GDAL command
we can't run these tests on the earlier GDAL versions which
didn't support open options.
The commands generated by the corresponding algorithms are already
well tested and still run on the earlier GDAL releases, it's just
the actual run test which will be skipped.
We now pass on the FORCE_SRS_DETECTION=YES open option which we
were previously dropping, so the results for these commands is
slightly different
Also drop test for older GEOS versions, it's covered by a test
for more recent versions and we have extensive test covering
the GDAL command line for this tool anyway.
