Hi Michael,
2012/2/17 Michael Barton michael.bar...@asu.edu:
To be consistent with other kinds of GRASS datasets, we should be able to
list strds, stvds, etc from g.list. Because this will require some updating
of other aspects of GRASS, as you note, it is good to start thinking of it
now.
Hi Michael,
this is a complex task. I will try to sketch a road map:
1.) Standard options for the new space time datasets must be specified
in lib/gis/parser_standard_options.c, as identifier the
abbreviations of space time raster, vector and raster3d datasets
should be used: stds, strds, stvds
The GUI gets its list from g.list, so nothing needs to be done there. A couple
things can be crossed off the list at least.
Michael
On Feb 16, 2012, at 4:22 PM, Sören Gebbert wrote:
Hi Michael,
this is a complex task. I will try to sketch a road map:
1.) Standard options for the new
Hi Michael,
2012/2/17 Michael Barton michael.bar...@asu.edu:
The GUI gets its list from g.list, so nothing needs to be done there. A
couple things can be crossed off the list at least.
But g.list do not know anything about space time datasets or
registered maps in the temporal database.
To be consistent with other kinds of GRASS datasets, we should be able to list
strds, stvds, etc from g.list. Because this will require some updating of other
aspects of GRASS, as you note, it is good to start thinking of it now.
Hopefully, you won't need to do this all since there are are
