[GRASS-dev] t.register ruins end timestamps

[Sören Gebbert]

Seems to be a bug in t.register if it still ruins the timestamp.
However, try this with the increment option:
t.register input=test maps=clip start='1987-02-26 09:12:36' -i incr="1
second"

This works only for a single map.

Question: why are you using r.timestamp to set the timestamps? It is not a
good idea to use them in conjunction with the temporal framework.

Am 01.12.2016 10:08 AM schrieb "Martin Landa" <landa.martin at gmail.com>:

> Hi,
>
> 2016-12-01 9:19 GMT+01:00 Sören Gebbert <soerengebbert at googlemail.com>:
> > Skip the interval option, it is not required if you specify a time
> interval
> > in the raster metadata or in an input file.
>
> it doesn't seems to work or I am still missing something. I fixed
> timestamps to (1 second interval):
>
> $ r.timestamp clip_LT51910261987057XXX02_B1
> 26 Feb 1987 09:12:36 / 26 Feb 1987 09:12:37
>
> $ t.register input=test maps=clip_LT51910261987057XXX02_B1 --o
>
> Still ruins end time timestamp:
>
> $ r.timestamp clip_LT51910261987057XXX02_B1
> 26 Feb 1987 09:12:36
>
> t.register fails with -i or increment='1 seconds':
> ERROR: The increment option requires the start option
>
> ? Ma
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20161201/83bb243a/attachment.html>