ensure that the visible layers for each map is correctly considered
when determining what symbols are overall visible
AKA make multiple map filtering work nicely alongside map themes
- Use an orderered list instead of a set, so that the first element
is really the preferred one
- Do not trust the project CRS if the project has no layers: it is
better to rely on the preferred CRS of the source instead
- Takes into account storageCrs in /collection response to get the
default crs in priority
- Append &crs=... to /items requests when the crs is not OGC:CRS84
- Make sure geometry axis order is flipped to easting/northing or
long/lat when reading geometries from a CRS with inverted axis order
- Report the list of available CRS in the dialog box where one can
select one
- Resolve "#/crs"
illustrating the most costly queries logged
Brings this helpful visualisation technique from the startup profiler
over to the db query log, so that you can easily identify the
slowest queries when a whole bunch of queries are recorded.
Implement required methods in vtpk provider metadata so that
VTPK files are shown in the browser panel as valid vector tile
layer sources.
Allows for easy addition of vtpk sources to projects, and easy
fixing of broken vtpk layer paths
This adds the API framework for storing additional, semi-structured
properties inside QgsField objects. The intention is that strong
field-type specific properties can be stored.
Eg for a geometry field type coming from the postgres provider
the metadata can be used to store the associated CRS and WKB types
so that clients can be aware of the correct format required for
geometries stored in that field. Instead of cluttering the QgsField
API with specific getters/setters for properties like crs(), wkbType(),
etc which only apply for a certain field type, the metadata map
approach helps us keep the API nice and slim.
The API has been designed to follow the approach used by various
Qt objects (such as QTextFormat) where a preset set of keys
are exposed as an enum, but additional ones can be used for
custom property storage. This allows for a more structured
use of properties with conventions which apply across different
providers (as opposed to a free-form string key approach).
Refs #49380
This adds a QgsRubberband in the 2D map canvas similar to the one used
to display the Frustum.
The option can be enabled in the General section of the 3D
configuration widget.
Adds drop support for layers in the multiple layer selection widgets to more efficiently select the desired elements. Especially useful in big project of with duplicated layer names.
