Opened 3 years ago

Last modified 8 months ago

#3160 new enhancement

g.gui.animation: enhance display of stvds that contain time periods with no-data

Reported by: veroandreo Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: wxGUI Version: svn-trunk
Keywords: g.gui.animation, stvds Cc:
CPU: Unspecified Platform: Unspecified

Description

For vector time series with no-data time periods, the animation is sub-optimal as it is currently. For example, I have weekly vector maps (points) that represent the occurrence of disease cases. These cases appear only in certain weeks of the year (summer weeks). I registered my weekly vectors of disease cases as a STVDS to make use of time information.

However, none of the solutions provided in G7:g.gui.animation is optimal to display this kind of data (STVDS). The options available are: 1) to display time periods of no-data (periods of no cases occurrences) and 2) to NOT display time periods of no-data.

If I choose to display time periods of no-data (no disease cases), I get black screens when there are no cases (which is most of the year). That makes the animation a bit ugly.

On the other hand, if I choose to NOT display those time periods in which there are no cases, I get the last disease cases that appeared frozen there for most of the year, i.e: the last vector map with data remains frozen until new vector maps with cases are reached. At least for this particular case, that behavior is not correct nor desirable. It would mean that there's always someone reporting a disease case in that place, which is not true in the data.

So, during those parts of the year with no data (no disease cases occurrence), I would expect to only see the background raster I choose, i.e.: no frozen last vector map, only the raster I had added as background.

I know passing a list of vectors instead of a STVDS solves the issue of periods with no data, but I loose time info which was the whole point.

Thanks a lot :)

Change History (8)

comment:1 Changed 3 years ago by neteler

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:2 Changed 3 years ago by martinl

Milestone: 7.2.17.2.2

comment:3 Changed 2 years ago by martinl

Milestone: 7.2.27.4.0

All enhancement tickets should be assigned to 7.4 milestone.

comment:4 Changed 22 months ago by neteler

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:5 Changed 17 months ago by neteler

Milestone: 7.4.17.4.2

comment:6 Changed 14 months ago by martinl

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:7 Changed 10 months ago by martinl

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:8 Changed 8 months ago by martinl

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.