[GRASS-dev] odd behavior from t.register when loading from file and no "end date" is specified

[Sören Gebbert]

Hi,

2015-10-18 17:01 GMT+02:00 Markus Neteler <neteler at osgeo.org>:
> On Sun, Oct 18, 2015 at 3:24 PM, Sören Gebbert
> <soerengebbert at googlemail.com> wrote:
>> Hi all,
>> sorry for my late response.
>>
>> The documentation is unfortunately not clear about the use of "-i"
>> flag, increment and text files. I will update this.
>>
>> The main idea is:
>> The -i flag and the increment option will only work if a start time
>> was defined at the command line (no end time!).
>> In case time stamps are set in the input file, then the -i flag and
>> the increment option should not be used.
>
> Wish:
> It would be great to either drop -i and let t.register manage it by
> itself upon presence of start time + no end time + increment defined
> (warning/error otherwise).
> Or at least, to generate some more messages in case of conflicting settings.
> I had the same problem myself and it took me (too) long to identify the problem.

Using an increment does not automatically mean to create time
intervals. It can also be used to create time instances.
I will try to add some more warnings about option usage.

Best regards
Soeren

>
> thanks
> Markus