of the matching GDAL command, and we can trust that GDAL will generate contours correctly
Avoids fragility in the test when underlying GDAL contour algorithm/logic changes
Paraphrasing Phil Thomson's advice on https://www.riverbankcomputing.com/pipermail/pyqt/2017-July/039450.html:
"
/Factory/ is used when the instance returned is guaranteed to be new to Python.
In this case it isn't because it has already been seen when being returned by by the python function
creating the provider subclass.
(However for a different sub-class implemented in C++ then it would be the first time it was seen
by Python so the /Factory/ on create() would be correct.)
You might try using /TransferBack/ on createProvider() instead - that might be the best compromise.
prefer something like "admin_name" over "type_name".
By penalising results with "type", "class", "cat" in their names
we are less likely to accidentally select a category field as the
friendly identifier when a better one exists.
Also add tests for this logic.
for "early" raster resampling
Notably, this adds the "Average" resampling as an option for
early resampling methods. (A nice side effect is that we also
get mode, cubic spline, Lanczos, ... for free!)
Fixes#40746
like the user has made a selection, but they've only selected one
of the projection category headings and so when they click OK they
see no change.
Now instead we disable the OK button in this dialog whenever the
user has a non-crs list item selected.
setting a cache image, and prefer any cached image with
parameters which exactly match the current cache parameters
This allows us to properly handle the case where:
- one map job is canceled, but some layers did finish rendering
- while the canceling is occuring on a different thread, we start
a new map render using the same cache and set new extent/map to pixel
for it
- the canceled job cleans up and stores the cache images for
the layers which DID finish rendering -- in this case we need
to explicitly state the previous extent/map to pixel when storing
the cache image, as they won't match the cache's current parameters
QgsCoordinateReferenceSystemRegistry
This was the last bit of untested, direct sql database access relating
to custom projections. Now everything is nice and central and protected
by unit tests.
