being redrawn/updated in the background
Gives immediate visual feedback to users that the current appearance
of those items are outdated and to wait while they update.
from a elevation profile dock
(Slightly hacky approach is required to allow the gui based item widget
access to the docks which live in app, without creating an interface
api for a single use case)
* QgsShadingRendering and pipe to render global elevation map
* gdal utils with datatype and resampling method enum
* raster layer elevation map
* optimize raster elevation map with rotation
* handle no data value in the map elevation raster pipe
* mesh layer and some little fixes
* fix nodata and hillshading z factor
* render shading on layout
* activate/deactivate the shading from ui
* shading only for layer that have elevation
* apply Z scale and offset of layer elevation properties
* ui settings
* allow elevation from point cloud even edl is deactivate for pointcloud
* fix ui
* sipify
* Shading renderer widget in styling panel
* icone for shading renderer settings widget
* two methods to combin elevation
* rewording
* remove check box at the bottom of canvas
* use band of elevation properties
* fix styling pannel
* render shading in layout
* keep EDL point cloud shading individually
* add shading rendering tests
* add missing code for local EDL for point cloud
* shading inactive by default
* rework raster layer resampling
* improve nodata in elevation map
* don't allow elevation map with != size to be combined
* remove EDL from point cloud
* renaming
* sipify
* colorize tests
* renaming
* RGB32
* renaming leftover
* some ui fixes
* fix border for EDL alg
* fix EDL closed next to nodata value
* fix first shading when activated
* renaming and typo
* fixes for doc, doxygen, indentation and spelling
* remove leftover member
* fix clang-tidy
* fix edl tests
* fix dll export
* minor fixes
* adapt images of tests
* fix narrowing
* fix indentation
* sipify
* WIP
* minor ui changes
Adds an option to allow for identify on mouse move
without clicking on the canvas.
This option behaves almost like the default identify
option, the only difference is that the used doesn't
need to click to trigger the identify action.
A 300ms timer takes care of triggering the actual identify
to avoid performance issues when moving the mouse.
* add Select within distance icon
* add select within distance to Vector -> research Tools Menu
* rework image according to review
* align image to grid
to configure a set of automatic font name replacements to use
when loading projects or styles
Allows users/administrators to configure a list of alternative fonts
to automatically match when a font referenced by a project/style is
not available on the current system.
This enhancement exposes any WMTS "time" dimensions for use in the
temporal framework, including allowing these layers to be animated
and controlled via the temporal controller.
There's some complexity involved here, because the WMTS specification
does NOT dictate how a time dimension should be exposed by services.
So different WMTS services are all handling this in different ways,
and we need to try to be as tolerant as possible.
Specifically, WMTS dimension values are just free-form strings, so
I've encountered a range of datetime formats -- e.g. "2021", "20210203",
"2021-02-03", "2021-02-03T12:13:14Z", and even WMS(T) style time
period designations ("2021-01-03T12:13:14/2021-01-05T12:15:11/P10M")!
These different formats all need special handling in order to correctly
interpret them as a date time value, and to be able to re-encode
an arbitrary datetime value back to the format string required
by the service. It's highly likely that we'll encounter additional
format strings when this feature is rolled out, and we'll need to
handle each individually.
When we do detect a time dimension on a WMTS layer, we no longer
expose this in the same way as other non-time dimensions. The browser
panel does not show the dimension values, and adding the layer
via Data Source Manager no longer prompts the user to pick from
the available time values. Instead, these layers are indicated with
a new "time capable raster layer" icon, and are added to a project
WITHOUT the user picking a specific time value.
Just like a WMS(T) layer, when a time-dimension enabled WMTS layer
is added to the project, it will default to the "automatic" temporal
mode, meaning that the layer will follow the temporal controller's
current time range by default. A user can then opt to show a specific
static time value for the layer through the layer's Temporal properties
page, by unchecking "Dynamic Temporal Control" and picking a specific
available time range from the "Predefined date" option. (Basically,
the user interaction and experience with a WMTS time enabled layer
is identical to with a WMS(T) layer).
Fixes#48364
using a fill symbol below the elevation surface
This can be easier to interpret in some cases, and helps match expected
symbology conventions in certain disciplines.
for an existing line feature
When active, users can click any line feature on the map to generate
a profile curve along that line. If multiple features are present
at the clicked point then a menu will popup allowing users to
select from these (i.e., same behaviour as the identify tool uses)
This provider has been marked deprecated and hidden from the UI
for a number of QGIS releases. No maintainers have stepped up
to take over maintainance of this provider, and accordingly it
is now subject for removal.
* make QgsMapToolCapture capable of capturing point/line/polygons
This moves part of the code from QgsMapToolDigitizeFeature to QgsMapToolCapture so the tool can actually capture point, line and polygons. It's mainly the 'cadCanvasReleaseEvent` which has been transfered.
* use a current CaptureTechnique in QgsMapToolCapture
QgisApp has been adapted to switch between the different techniques
* add point/line/polygon specific handlers for capture map tool
* convert add part map tool to use QgsMapToolCapture capabilities
* fix use of deprecated methods
* also create a virtual handler for QgsMapToolDigitizeFeature::featureDigitized
* more dox
* use const abstract geom in virtual handlers
* add new class QgsMapToolCaptureLayerGeometry to handle layer specific operation in capture map tool
such as avoiding intersections
* allow to add linear geometries on curved geometry layers
* make actions exclusive
* add settings registry to app
* add a registry for shape map tools
* abstract class for shape map tools
* adapt QgsMapToolCapture to correctly support shape map tools
* clean up of QgisApp
* new class QgsMapToolsDigitizingTechniqueManager to handle actions in app related to capture map tools
* clean up QgisInterface
* sipify
* refactoring of existing shape tools
* refactor add ring to fully support capture map tool
* add missing folder to Doxygen
* fix layout
* fix erasing at iterator pos
* fix unused warning
* fix more dox
* fix cpp check warning
* fix unused warning
* fix annotation map tool does not support shape + set tool name
* correctly handle case when the capture is not done on a vector layer (annotation, mesh, …)
* enable shapes in annotation map tool
* correctly undo and clean
* adapt existing shape tests
the deletion test with circular vertices has been dropped since the capture map tool behaves differently
* fix warning
* refactor fill ring to support shape digitizing
* fix win build
* fix more tests
* avoid detach warnings
* fix app test + clean up
* harmonize new settings with existing ones
* fix categories
* support adding multi lines as a part
* fix adding curve part to multi line
* also handle points
* code a bit clearer
* cast not always valid
* allow adding curved polygon to multipolygon
* add test for QgsGeometry::addPart with curved parts on non-curved geoms (lines and polygons)
* fix with Python < 3.9
* better dox for deprecated interface actions methods
* remove files leftover
* remove leftover circular string curve point tool
* add default Z/M values when calling QgsGeometry::coerceToType
* Apply suggestions from code review
Co-authored-by: Nyall Dawson <nyall.dawson@gmail.com>
* fixes from review
* move layer specific part to specific tool
* fix typo
* fix leak
* fix dox
* fix segmentization
* call map tool implementation of addCurve when adding trace curve to avoid point duplication
* call sub-class implementation
* fix since 3.24 -> 3.26
* fix test
* add test to avoid extra curves when using tracing
* fix headers
Co-authored-by: Nyall Dawson <nyall.dawson@gmail.com>
[mesh] UX fixes:
* move mesh elements click->move->click instead press-> drag->release
* allow to select by drawing a polygon and select an existing polygon in the same map tool like for vector layer)
