The default units in QgsMapRenderer is Millimeters. The default units in SLD
 is Pixel but exportSld does not convert all millimeters in pixels.

We notes this bug by comparing default QGS Server rendering and rendering with
 the SLD generated by QGIS.

To resolve it, we just have to add units to the document element.

The default units in QgsMapRenderer is Millimeters. The default units in SLD
 is Pixel but exportSld does not convert all millimeters in pixels.

We notes this bug by comparing default QGS Server rendering and rendering with
 the SLD generated by QGIS.

To resolve it, we just have to add units to the document element.

(cherry picked from commit d6f66e & b36cd1f)

Signed-off-by: Werner Macho <werner.macho@gmail.com>

Since QGIS 2.8, QGIS Server rendered layers form group in reverted order.

(cherry picked from commit f0930ca)

(cherry picked from commit 6a4544f)

(cherry picked from commit 08185c9)

(cherry picked from commit 24960da)

(cherry picked from commit 968e55c)

(cherry picked from commit 0ceeb51)

(cherry picked from commit daa6510)

…13723)

(cherry picked from commit d3ee16f)

(cherry picked from commit d9c8e73)

Line breaks are not properly handled in GeoJSON results when making GetFeature requests.
Line breaks should be replaced by \\n.

(cherry picked from commit 6e1df49)

…reaks

Enhance replace, thanks to @nyalldawson
Enhance format, thanks to @jef-n

fixes #13118

(cherry picked from commit fd9f0b5)

currently, changing the entr doesn't do anything in the attribute table since no signal is emitted

should be backported to 2.12

and not QgsDefaultSearchW
also handles properly the (no selection) case

and not QgsDefaultSearchW anymore
fixes expression creation

(cherry picked from commit 08ec25b and a6a2982)

using virtual fields or other complex filters

refs #13695

(cherry-picked from dddd043)

(cherry-picked from 5a6bfbb)

(cherry-picked from ce5ed44)

(cherry-picked from ba1de8b)

final node following a delete rather than reverting to the first
node.

Improves workflow when deleting sequential nodes from end of
lines.

(cherry-picked from bcb7e44)

(cherry-picked from 353c0db)

geometry

Fix #13695

(cherry-picked from c445ac1)

are not being applied (fix #13707)

(cherry-picked from 2ac5933)

2ac5933 fixed the regression in 2.12, but there were more underlying
issues from <2.8 causing sub symbols with data defined properties
to be ignored.

Add some tests.

(refs #13707)

(cherry-picked from 9e84fca)

key is a simple (non compound) type

IN (...) is much faster than chained ...OR... clauses

Additionally, trying to filter by a large number of feature Ids
(eg > 30k ) fails when using the ...OR... approach, but works
using IN

all features and then testing the feature id when saving selected
features

For providers such as Postgres this is orders of magnitude faster.
Eg, saving 6 selected features from a 800k PostGIS table now
takes < 1 second as opposed to ~33 seconds

Fix #8334

(cherry-picked from f0d31b0)

features. Results in similar speed improvements when updating
only selected features from a large PostGIS layer

(cherry-picked from 33fe0e2)

(cherry-picked from 6772ffb)

null geometry (fix #13749)

(cherry-picked from 7439643)

(cherry-picked from fccf54b)

(cherry-picked from 18744b4)

(cherry-picked from 5c9873c)

testing label candidates against polygon obstacles

Fix #13556

(cherry-picked from b384f18)

(cherry-picked from 709b47e)

Fixes #13811
Includes testcase

(cherry-picked from 824fd7b)

(cherry-picked from dc0639c)

(cherry-picked from 26b3685)

(cherry picked from commit 0799e09)