* [processing] qgis regular points test
* [processing] qgis shape buffer variable tests
* [processing] qgis create grid lines test
* [processing] qgis convert geometry test
* [processing] qgis extract by location test
* [processing] qgis add field test
* [processing] trying to fix travis failing
* [processing] trying to fix travis failing/2
* trying to fix travis failing/3
* [processing] Add new default option "ProjectCrs" to ParameterCrs
* [processing] RegularPoints tests shouldn't rely on iface
* [processing] Fix regular points test
* [processing] RandmPointsExtent new CRS parameter
* [processing] qgis random point in extent test
* [processing] qgis random point in extent test/2
* [processing] remove qgis random point in extent test
* no output random points in extent test
* remove useless output
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.
Tagged as feature to not forget mention in changelog and documentation
Intended as a registry for the various processing components,
including providers, algorithms and various parameters and outputs.
Currently handles only registration of providers, as a step toward
removing processing's algList (this requires first porting
the algorithm class to c++)
A QgsProcessingRegistry instance is attached to QgsApplication,
and is retrieved by QgsApplication::processingRegistry()
Nothing particularly exciting here yet, but this commit
moves the definition of the provider base class to a c++
QgsProcessingProvider abstract base class.
As part of this some existing python methods were renamed
to make their use clearer and to fit with the QGIS c++
api conventions:
- getName was renamed to id
- getDescription was renamed to name
- getIcon was renamed to icon
These API breaks are documented
These variables take a lot of time to calculate and cause lots of
lengthy hangs in processing. (Eg add some moderately large rasters
to a project, then try to run any processing algorithm and QGIS
will freeze).
The layer extent can already be used in expressions via the
layer_property function, which only evalutes the extent if required
and only for layers it is used for.
The band stats for raster layers should be moved to a
band_statistic function in core which behaves the same way.
