16308 Commits

Author SHA1 Message Date
Alessandro Pasotti
09345b5130 Add QgsExpressionStoreDialog 2019-12-16 17:29:30 +01:00
Alessandro Pasotti
2ab794bcc5 Add tests and utility methods 2019-12-16 17:29:30 +01:00
Alessandro Pasotti
e8d76e2a92 Stored expressions initial implementation 2019-12-16 17:29:30 +01:00
Matthias Kuhn
b42a31ec2f
Merge pull request #32472 from troopa81/feature_selectionwidget_in_featureselectiondialog
Selection widget in feature selection dialog
2019-12-16 11:32:25 +01:00
Julien Cabieces
a8f46ac655 update sip 2019-12-16 09:55:30 +01:00
Borys Jurgiel
dbdc397fd8 [DB Manager] Fix broken geometry type of GeoPackage based SQL Layers. Fixes #33232 2019-12-16 10:08:44 +10:00
Alessandro Pasotti
7464290ae3
Merge pull request #33379 from elpaso/widget-dependencies-move-to-formatter
Move layerDependencies to formatter
2019-12-14 09:00:08 +01:00
Nyall Dawson
db2ac240de Add some references hashes seen on azure builds 2019-12-14 08:20:15 +10:00
Alexander Bruy
fba3ab99a0
Merge pull request #33368 from alexbruy/processing-updates
Processing updates
2019-12-13 21:59:08 +02:00
Nyall Dawson
a1ac77877f Add a method to determine if the coordinate operation string returned
by QgsCoordinateTransformContext.calculateCoordinateOperation corresponds
to the reverse of what's actually required.

Gross API, but it's the best we can do until proj has a method to
invert a coordinate operation so that we can return the proper
inverse operation proj string from calculateCoordinateOperation
(without resorting to fragile proj string parsing/mangling)
2019-12-14 05:33:59 +10:00
Nyall Dawson
ef19797997 Add method to retrieve the details of the coordinate operation which is
actually being used by a QgsCoordinateTransform object
2019-12-14 05:33:59 +10:00
Nyall Dawson
82a84ffd0d Don't try to normalize proj coordinate operations constructed directly
from the proj string via the transform context

This isn't possible -- only proj coordinate operations constructed
from a src/dest CRS pair can be normalized, not those constructed
from a proj string.

It was redundant in any case, since we always normalize the available
operations before giving users a choice of them.

So just add some big bold warnings to the dox in case anyone is
manually manipulating and adding custom operations, that these
also MUST be pre-normalized

Refs #33121, conversation in https://github.com/OSGeo/PROJ/issues/1794
2019-12-14 05:33:59 +10:00
Julien Cabieces
80a362375c gather protected instructions 2019-12-13 18:00:16 +01:00
Julien Cabieces
d224a7ce99 [FEATURE][needs-docs] Add feature filtering and selection actions in feature selection
dialog
2019-12-13 17:33:40 +01:00
Matthias Kuhn
c2cde01cc8
Merge pull request #33378 from havatv/patch-4
Fix the label of the output parameter of the TPI algorithm
2019-12-13 15:39:33 +01:00
Alessandro Pasotti
a977343944 Test for relationreference field formatter deps 2019-12-13 13:36:06 +01:00
Peter Petrik
229245ce65 fix building on macos due to missing include of spatialite 2019-12-13 12:56:07 +01:00
Alexander Bruy
ddb93602ef address comments 2019-12-13 13:41:27 +02:00
Alessandro Pasotti
4ad62aa6ff Move layerDependencies to formatter
... from the widget
2019-12-13 11:54:25 +01:00
Håvard Tveite
512eb4d2b8
Fix the label of the output parameter of the TPI algorithm 2019-12-13 11:09:45 +01:00
Even Rouault
2c652040cd
Fix compilation error in qgsdxfexport.cpp
I'm not sure which of QT 5.9.0 or gcc 5.5.0 is not happy, but with both
of them, I get:
```
/opt/qt59/include/QtCore/qflags.h: In instantiation of ‘QFlags<T>& QFlags<T>::setFlag(Enum, bool) [with Enum = QgsDxfExport::DxfPolylineFlag]’:
/home/even/qgis/QGIS/src/core/dxf/qgsdxfexport.cpp:1102:68:   required from here
/opt/qt59/include/QtCore/qflags.h:153:46: error: no match for ‘operator~’ (operand type is ‘QgsDxfExport::DxfPolylineFlag’)
         return on ? (*this |= f) : (*this &= ~f);
```
2019-12-13 10:33:14 +01:00
Peter Petrik
6febf38e10 [mesh] support active flag capability of MDAL. mesh layers for datasets that does not support active flags should not take less memory and load faster 2019-12-12 08:37:55 +01:00
Alexander Bruy
0219d0019e
Merge pull request #33290 from alexbruy/port-algorithms
[processing] port some algorithms to C++
2019-12-12 08:21:57 +02:00
Nyall Dawson
187b8f3325 When saving a user crs, if a WKT representation of the CRS is available,
then store and save that

Proj string representations of CRSes are lossy, so we should always prefer
WKT when it's available
2019-12-12 14:44:50 +10:00
Nyall Dawson
898205e7d8 Fix dox 2019-12-12 07:44:11 +10:00
Nyall Dawson
b1bbc8511b [labeling] Move settings related to removing labels (e.g. max no
of labels, min size for labels) to a new class QgsLabelThinningSettings

This new class is designed to contain settings related to how the label
engine removes candidate label positions and reduces the number of
displayed labels.
2019-12-12 07:44:11 +10:00
Nyall Dawson
d3da0e0281 Also move labeling gui files to dedicated subdirectory 2019-12-11 14:05:44 +10:00
Nyall Dawson
a8adb2d6c2 Code shuffle: move all labeling related code into src/core/labeling
So that these files are all grouped together, making it easier to locate
all the components of the labeling engine and hopefully making things
easier to navigate
2019-12-11 14:05:44 +10:00
Denis Rouzaud
c5766dc83b
Merge pull request #33262 from 3nids/log_impr
Classification methods: save/read parameters, improve negative value handling in log method
2019-12-10 23:20:58 +01:00
Alexander Bruy
243cd6ce8b use setValue() instead of setLayer() to handle different value types
(strings, variants, layers)
2019-12-11 04:49:14 +10:00
Alexander Bruy
dcdcb334ef use active layer only if there is no default value 2019-12-11 04:49:14 +10:00
Alexander Bruy
f37a75923f [processing] use active layer in the widget wrapper only for
non-optional parameters otherwise use default value
2019-12-11 04:49:14 +10:00
Alexander Bruy
8fb28c8657 update menu entries 2019-12-10 10:33:32 +02:00
Nyall Dawson
f9a3d0589a Remove last use of pal::RTree 2019-12-10 18:28:11 +10:00
Alexander Bruy
3910d7774b use deprecated flag instead of hidden 2019-12-10 08:42:33 +02:00
Nyall Dawson
7381a2574e [processing] Add another hash to grass imagery tests
This one seems to come up occasionally on Travis
2019-12-10 10:53:08 +10:00
Markus Neteler
f497cf4f41 v.to.rast: fix va -> val 2019-12-10 08:17:48 +10:00
Alexander Bruy
d40a036c03 [processing] port random extract to C++
Also fix unreported bug caused incomplete results when same FID
was used multiple times
2019-12-09 13:28:32 +02:00
Alexander Bruy
cc5b6e74f4 [processing] port zonal statistics to C++ 2019-12-09 13:28:32 +02:00
Alexander Bruy
4622661f59 [processing] port truncate table to C++ 2019-12-09 13:28:32 +02:00
Alexander Bruy
c974125fd9 [processing][needs-docs] replace set raster style and set vector style
Python algorithms with generics set layer style C++ algorithm
2019-12-09 13:28:32 +02:00
Alexander Bruy
b85fe90955 [processing] port raster layer statistics to C++ 2019-12-09 13:28:32 +02:00
Alexander Bruy
2ff85f92df [processing] port pole of inaccessibility to C++ 2019-12-09 13:28:32 +02:00
Alexander Bruy
2caf9e6ac3 [processing] port points from polygons algorithm to C++ 2019-12-09 13:28:32 +02:00
Alexander Bruy
df3e801f31 [processing] port nearest neighbour analysis algorithm to C++ and add
test
2019-12-09 13:28:32 +02:00
Alexander Bruy
eec0ac07f8 [processing] port geometry by expression to C++ 2019-12-09 13:28:32 +02:00
Alexander Bruy
c2d1649e60 [processing] port extract specific vertices algorithm to C++ 2019-12-09 13:28:32 +02:00
Alexander Bruy
4bbb07f48f rename processing qgis test to allow running only subset of tests 2019-12-09 13:28:32 +02:00
Alexander Bruy
e0136ff65c [processing] port extract layer extent to C++ 2019-12-09 13:28:32 +02:00
Alexander Bruy
9615306f44 [processing] port sum line length algorithm to C++ 2019-12-09 13:28:32 +02:00