[GRASS-dev] problem initializing temporal gis

Luca Delucchi lucadeluge at gmail.com
Fri Jul 11 02:15:30 PDT 2014

On 28 June 2014 12:32, Sören Gebbert <soerengebbert at googlemail.com> wrote:
> Hi Luca,

Hi Soeren,

> Yes, it is possible to add any amount of fields in the future. Older
> databases must then be updated to support the new fields, otherwise
> the updated framework will not work with them.

ok, so maybe it is better to collect idea and change only few times,
do you think I should open a ticket?

> However, a specific unit field that can be set by the user will
> conflict with the unit field of raster and voxel maps. IMHO the unit
> of a space time raster dataset should be derived from the units of the
> registered raster maps. Well i did not implemented this, since from my
> experience are units used very seldom for maps. So the correct
> implementation would add a units fields to raster and 3d raster map
> tables and to STRDS and STR3DS tables. The STDS SQL code must be
> updated to aggregate the unit information. But what to do if map layer
> have different units? Or if only a subset of the registered maps have
> units?

In r.support there is units field, could we use this?
Can you do some example of map layer with different units?

> So maybe the semantic type option is sufficient right now?

But it accept only min, max, sum, mean value?

> Best regards
> Soeren



More information about the grass-dev mailing list