#3223: r.info displays wrong timestamp after t.rast.series with a where clause
------------------------+-------------------------
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.4.0
Component: Default | Version: svn-trunk
Keywords: r.info | CPU: Unspecified
Platform: Linux |
------------------------+-------------------------
If I run t.rast.series using a where clause, r.info of the resulting map
shows the timestamp of the whole time series and not that of the temporal
selection performed with where.
The selection of maps is fine given that I get the right list of maps when
using the same where clause in t.rast.list, and the values of resulting
maps using the whole time series or just a selection, differ as expected.
#3223: r.info displays wrong timestamp after t.rast.series with a where clause
--------------------------+-------------------------
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.4.1
Component: Default | Version: svn-trunk
Resolution: | Keywords: r.info
CPU: Unspecified | Platform: Linux
--------------------------+-------------------------
Comment (by veroandreo):
Replying to [comment:2 huhabla]:
> Fixed in grass trunk revision r72479. Please test.
After testing, I backported to release branch 74 in r72493 and to release
branch 72 in r72499 (this last one without test_t.sereis_bug_3223.sh)
#3223: r.info displays wrong timestamp after t.rast.series with a where clause
--------------------------+-------------------------
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.4.1
Component: Default | Version: svn-trunk
Resolution: fixed | Keywords: r.info
CPU: Unspecified | Platform: Linux
--------------------------+-------------------------
Changes (by veroandreo):
* status: new => closed
* resolution: => fixed
Comment:
Replying to [comment:5 neteler]:
> Please close the ticket if issue is solved.
I had left it open because there's an open question (see comment 3).
However, since the issue is fixed, I close it now. Re-open if needed.