[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grass-dev
Subject:    [GRASS-dev] Temporal data (was QGIS GRASS Plugin Upgrade Crowdfunding)
From:       Radim Blazek <radim.blazek () gmail ! com>
Date:       2015-03-30 7:47:45
Message-ID: CAEMrtYqxTTZ0aXgB3QqR1WnwXi=0RVQ0O0Nwp4H=EafqawH+vw () mail ! gmail ! com
[Download RAW message or body]

Hi again.

On Tue, Mar 24, 2015 at 10:04 AM, Sören Gebbert
<soerengebbert@googlemail.com> wrote:
>> Are there functions in time series implementation which need to be
>> called directly from the plugin or everything may be done just calling
>> t.rast.* modules?
>
> Most of the temporal functionality is available through the temporal
> modules. However some important algorithms (temporal re-sampling) are
> available only in the Python framework. This is needed for time series
> animation creation. Using the framework directly will speed things up,
> because the module calls, the parsing and interpretation of the module
> outputs can be avoided.

I am getting convinced that the temporal data visualization support
should be added to QGIS core. A single time navigation toolbar
(from/to, start/stop, previous/next) and temporal support in data
providers (QgsVectorDataProvider::getFeatures,
QgsRasterDataProvider::block). That would allow simultaneous animation
of temporal data from various sources in different formats (time frame
defined by band, layer or attribute).

There are already 3 plugins for temporal data management [1][2][3],
writing another one seems misconception and wasting of resources.

[1] https://plugins.qgis.org/plugins/timemanager/
[2] https://plugins.qgis.org/plugins/multiview/
[3] https://plugins.qgis.org/plugins/temporalprofiletool/

Radim
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
[prev in list] [next in list] [prev in thread] [next in thread]