[GRASS-dev] Major changes in the temporal framework
soerengebbert at googlemail.com
Fri Dec 27 18:33:15 PST 2013
i will try to support your suggestion. I will introduce two GRASS
variables to be set via g.gisenv.
to disable the mapset check and the writing of the timestamps of each
map to the map metadata
in the spatial database as text files. You can set these variables
Settings these variables "True" should (hopefully, because untested)
allow the registration of maps outside the current mapset, even if you
do not have the permission to modify the maps.
A warning will be printed if these variables are set True.
BUT, be aware that this feature can lead to the corruption of the
temporal database and
unwanted side effects. You can mess up the temporal database if you
are not 100% sure what you are doing.
It is no longer possible to access the timestamp information of these
maps using the C-libraries, because
the timestamp information is not available in the map metadata text files.
2013/12/28 Luca Delucchi <lucadeluge at gmail.com>:
> On 22 December 2013 00:07, Sören Gebbert <soerengebbert at googlemail.com> wrote:
>> Dear all,
> Hi Soeren,
>> just for your information:
>> I will commit several modification to the temporal framework (grass7
>> trunk) in the next weeks, that will change the SQL database layout and
>> the API. The goal is to make the temporal frameworks SQL database
>> interaction much faster, reducing the number of tables to scale better
>> with tens of thousand of maps, improving the PostgreSQL
>> compatibility/performance and make it better maintainable.
> these changes could be useful for create temporal dataset using maps
> outside current mapset?
> this change for my point of view is really important, if you break the
> API could I suggest you add also this "feature" to temporal framework?
> Thanks a lot
>> Best regards
More information about the grass-dev