mirror of
https://github.com/qgis/QGIS.git
synced 2025-02-26 00:02:08 -05:00
d98defec1a
This exposes some basic temporal capabilities for vector layers: - static time range for layer (to match raster layer possibilities), this sets a single static time range which applies to the whole layer. ALL features from the layer will be shown whenever the canvas time overlaps the layer time range - "Single field with datetime": Allows selection of a single date or datetime field from the layer. Features will be shown whenever this field value is within the canvas time range - "Separate Fields for Start and End Date/Time": Allows selection of start and end date/datetime fields from the layer. Features will be shown whenever the time interval calculated from these fields overlaps the canvas time range Some known limitations/inefficiencies: - currently only date/datetime fields can be used. This was done to simplify the format handling and avoid the need to worry about string fields with different datetime formats. In future we should allow selection of string fields and allow users to enter a custom datetime format string - unlike the Time Manager plugin approach, the approach taken here is to rely completely on QGIS expressions and feature requests to do the filtering (Time Manager uses layer filter strings and attempts to set a native SQL filter syntax so that filtering is done on the backend). This is intentional, because it provides a unified filter approach regardless of the provider used (i.e. we don't need to worry about the different SQL syntaxes used natively by the different providers). The beauty of feature request expression compilation **should** mean that the QGIS expressions are magically turned into native backend queries, BUUUUUUUUUUUT... because we lack QGIS expression support for date time literals, we currently rely on the "to_datetime" expression function and coerce everything through strings. None of the expression compilers handle this function, so currently ALL filtering is done on the QGIS side. We need to add functions for optimised datetime literal creation, and then ensure that the different compilers correctly map these literals across to the backend filter syntax to allow all the filtering work to be done on the database side... So currently, performance is much worse with large layers compared to Time Manager. But, the advantage is that we can use the native temporal framework and have vector layers animated alongside mesh and raster layers!
49 lines
1.6 KiB
Plaintext
49 lines
1.6 KiB
Plaintext
/************************************************************************
|
|
* This file has been generated automatically from *
|
|
* *
|
|
* src/gui/raster/qgsrasterlayerproperties.h *
|
|
* *
|
|
* Do not edit manually ! Edit header and run scripts/sipify.pl again *
|
|
************************************************************************/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
class QgsRasterLayerProperties : QgsOptionsDialogBase
|
|
{
|
|
%Docstring
|
|
Property sheet for a raster map layer
|
|
|
|
.. versionadded:: 3.12
|
|
%End
|
|
|
|
%TypeHeaderCode
|
|
#include "qgsrasterlayerproperties.h"
|
|
%End
|
|
public:
|
|
|
|
|
|
QgsRasterLayerProperties( QgsMapLayer *lyr, QgsMapCanvas *canvas, QWidget *parent = 0, Qt::WindowFlags = QgsGuiUtils::ModalDialogFlags );
|
|
%Docstring
|
|
Constructor
|
|
|
|
:param lyr: Map layer for which properties will be displayed
|
|
:param canvas: the QgsMapCanvas instance
|
|
:param parent: the parent of this widget
|
|
:param fl: windows flag
|
|
%End
|
|
|
|
protected slots:
|
|
|
|
};
|
|
/************************************************************************
|
|
* This file has been generated automatically from *
|
|
* *
|
|
* src/gui/raster/qgsrasterlayerproperties.h *
|
|
* *
|
|
* Do not edit manually ! Edit header and run scripts/sipify.pl again *
|
|
************************************************************************/
|