Skip to content
Permalink
Browse files

Explicitly mention in docs that presence of destination CRS does

not affect filter expressions or virtual field values
  • Loading branch information
nyalldawson committed Jun 8, 2017
1 parent e437812 commit 482ed3f25a4bc467b7159f87e921c362f3b10585
Showing with 18 additions and 0 deletions.
  1. +9 −0 python/core/qgsfeaturerequest.sip
  2. +9 −0 src/core/qgsfeaturerequest.h
@@ -568,6 +568,15 @@ Set a subset of attributes by names that will be fetched
set on the request is expected to be in the same CRS as the destination
CRS.

The feature geometry transformation to the destination CRS is performed
after all filter expressions are tested and any virtual fields are
calculated. Accordingly, any geometric expressions used in
filterExpression() will be performed in the original
source CRS. This ensures consistent results are returned regardless of the
destination CRS. Similarly, virtual field values will be calculated using the
original geometry in the source CRS, so these values are not affected by
any destination CRS transform present in the feature request.

.. seealso:: destinationCrs()
.. versionadded:: 3.0
:rtype: QgsFeatureRequest
@@ -522,6 +522,15 @@ class CORE_EXPORT QgsFeatureRequest
* set on the request is expected to be in the same CRS as the destination
* CRS.
*
* The feature geometry transformation to the destination CRS is performed
* after all filter expressions are tested and any virtual fields are
* calculated. Accordingly, any geometric expressions used in
* filterExpression() will be performed in the original
* source CRS. This ensures consistent results are returned regardless of the
* destination CRS. Similarly, virtual field values will be calculated using the
* original geometry in the source CRS, so these values are not affected by
* any destination CRS transform present in the feature request.
*
* \see destinationCrs()
* \since QGIS 3.0
*/

0 comments on commit 482ed3f

Please sign in to comment.
You can’t perform that action at this time.