Returns a map containing all attributes from a feature, with field
names as map keys. We've got featureful, robust support for working
with maps in expressions now, so this allows rapid conversion
of all feature attributes to a map to use with these handy
functions.
symbols to the left OR symbols to the right of legend text), and
alignment for group/subgroup/item text
Allows creation of right-to-left locale friendly legends. Additionally,
we default to this right-to-left style alignment when creating new
legends under a RTL based locale.
Allows for rendering a marker symbol in the background of labels
(complementing the existing shapes/SVG choices). This allows use
of QGIS marker symbology as a background symbol behind labels (e.g.
for highway shield labels)
Refs #29391 : Added new 'else if' branch that handles OGC HTTP URL srsName style, so that epsgNr can be extracted from srsName. This doesn't fix the core issue mentionend in the Bug report #29391 though
Added branch to handle OGC HTTP URI srsName Style. Also adjusted exisiting variable names to account for the extra branch
item is selected (i.e. HTML items, attribute tables) are saved
on a multiframe level, instead of an individual frame level.
In this case we prefer to make the multiframe's scope the main, editable
one. That's because most expressions are evaluated on the multiframe
subclass level, not on a frame-by-frame basis.
Ideally both would be editable, but for now let's go with the most
useful one.
This is a revival of Server: if there is a primary key, use the pk value(s) as gml id instead of the feature id. #6279
In WFS and in WMS GetFeatureInfo (format GML), there is a 'fid' Attribute with a feature identification. Currently, we are using the QGIS feature id there. However, the postgres provider uses an id/value map for some data types (e.g. bigint in 2.18). Therefore, the feature id depends on the fetching order and might not be stable between different requests. So clients cannot use the fid for feature identification.
This PR fixes that such that primary key values are preferred for the fid. If the data provider does not report any PK columns, there is a fallback to the QGIS feature id.
Larger values may speed up the rendering and provide better labelling (fewer gaps without labels)
at the expense of using more memory.
Ported from XYZ Tiles plugin - originally contributed by @nurenda
GDAL 3.1 will bring read-write supprot for single-layer ZIP compressed shape
files (.shz), or multi-layer ones (.shp.zip). Do the few tweaking in QGIS so
that it is handled properly.
Related GDAL PR: https://github.com/OSGeo/gdal/pull/1676
