Re: [GRASS-user] t.register syntax [CORRECTED]

2017-03-22 Thread Rich Shepard
On Thu, 23 Mar 2017, Sören Gebbert wrote: Use the comma separator option for g.list since a comma separated list of maps is required for the maps option in t.register. Soeren, I wondered about the placement of the separator; it did not look right where it was yet I did not try moving it to

Re: [GRASS-user] t.register syntax

2017-03-22 Thread Andres Solarte
try this command t.register -i input=blocked_h maps=`g.list raster pattern=blocked_h_* separator=comma` type=raster start="2013-11-15" increment="1 days" 2017-03-22 20:25 GMT-03:00 Sören Gebbert : > Use the comma separator option for g.list since a comma separated list > of maps is required for

Re: [GRASS-user] t.register syntax

2017-03-22 Thread Sören Gebbert
Use the comma separator option for g.list since a comma separated list of maps is required for the maps option in t.register. 2017-03-23 0:16 GMT+01:00 Rich Shepard : > I thought I had recorded the syntax for creating strds's from existing > raster maps, but I neglected to do so. (t.create worke

[GRASS-user] t.register syntax

2017-03-22 Thread Rich Shepard
I thought I had recorded the syntax for creating strds's from existing raster maps, but I neglected to do so. (t.create worked correctly and the strds exists.) This command fails: t.register -i input=blocked_h maps=`g.list type=raster pattern=blocked_h_*` type=raster separator=comma start="2