settings widget to allow users to tweak the obstacle behavior
Previously these settings were stuck inside the disabled label settings
widget, which meant that to edit them you had to temporarily enable simple
labels, tweak the setting, and then set back to obstacle mode... woot.
* [FEATURE] Static particle traces for rendering mesh vector dataset
This PR permits to display directly in QGIS static particle traces for vector datasets in mesh layer without any plugin.
The user can choose in the mesh layer properties window :
- the color
- the size of the traces (line width)
- the count of particles
- the maximum length of the particle's tail
* [FEATURE] API for rendering frames for mesh vector dataset animation (particles)
Adds a renderer to generate frames that represent particle traces in a vector field of a mesh layer. The renderer cannot be chosen in the current GUI, however crayfish plugin can use API to generate avi/gif files with nice animations representing the movement of (random) particles in the mesh layer vector field.
placement rules should be followed when solving the pal labeling engine
solution.
For new projects it defaults to version 2, but when loading an older project
version 1 is used.
This allows changes to be made to the label placement problem solving without
affecting the placement of labels in existing projects.
which are unsupported by proj 6
E.g. some candidate operations between EPSG:3035 and EPSG:5514
Since these can NEVER (as of now) be instantiated by proj, even if
the grid shift files are present, it's misleading to present them
as options to users.
Refs #30569
* [FEATURE] Mesh streamlines
fix#29534
The vector field data set in a mesh layer can currently be only rendered with arrows. This PR adds a new feature to render vector field in mesh layers with streamlines.
The streamlines are seeded from start points. The seeding points can start from the vertices of the mesh, from a used grid or randomly. Streamlines could be coloured or width can be selected.
Fixes#32973 or at least improve it significantly
Currently with PROJ 6 transformCoords() will raise an exception as soon
as a single point fails to transform. With PROJ < 6, this (generally)
did not occur. Exceptions were raised only (mostly) on failures on
single point.
Imitate that
comparisons to be made when resolving primary keys in the Oracle and
Postgres providers
qt's built in qMapLessThanKey for QVariantList is broken and does a
case-insensitive operation, so we replace it with a working version instead...
