[GRASS-dev] [GRASS GIS] #2110: error registering maps outside mapset

[GRASS GIS]

#2110: error registering maps outside mapset
----------------------+-----------------------------------------------------
 Reporter:  lucadelu  |       Owner:  grass-dev@…              
     Type:  defect    |      Status:  new                      
 Priority:  normal    |   Milestone:  7.0.0                    
Component:  Temporal  |     Version:  svn-trunk                
 Keywords:  register  |    Platform:  All                      
      Cpu:  All       |  
----------------------+-----------------------------------------------------

Comment(by huhabla):

 The current behavior is a design decision. Space time datasets accept only
 maps from the same mapset for registration. A new space time datasets will
 be dedicated to the current mapset. The current mapset is part of its
 temporal database identifier. Hence space time datasets from different
 mapsets can be stored in the same temporal database. This assures that
 mapsets can share the same temporal database.

 Space time datasets are new datatypes in GRASS and should behave like
 raster or vector maps. Hence these datatypes are mapsets specific. It is
 possible to access space time datasets from different mapsets for reading,
 if the mapsets share the same temporal database. But it should not be
 possible to modify space time datasets from different mapsets.

 As default the temporal database will be created in the PERMANENT
 directory, so that space time datasets and maps from different mapsets can
 be registered there. This allows the read only access to the datasets from
 different mapsets in the temporal database. To avoid this, the temporal
 database can be set mapset specific. Hence each mapset sees only their
 space time datasets and registered maps.

 This decision was made to reduce confusion, to avoid unexpected behavior
 and to assure a convenient behavior of the temporal framework in the GRASS
 way.

 Examples to support this decision:

 If you register maps from a foreign mapset in a space time raster dataset
 and you remove the maps in the foreign mapset, then the temporal database
 might not be aware of these changes, pointing to maps that have not been
 unregistered. In all following operations the effected space time datasets
 will produce errors.

 If you use "t.remove" with the "-rf" option, the provided space time
 datasets and its registered maps will be removed from the temporal and
 spatial database (g.remove will be called). This operation will fail if
 the registered maps are from different mapsets.


 Attention when several mapsets share the same temporal database:

 It is still a work in progress to grant only access to space time datasets
 and raster maps in the temporal database, that the user has permission to
 read --> configured using the GRASS mapset permission system. Hence you
 might see space time datasets in the output of "t.list" from different
 mapsets, to which you have no permission to access.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2110#comment:1>
GRASS GIS <http://grass.osgeo.org>