[GRASS-dev] [GRASS GIS] #70: imagery modules: strip @mapset part

[GRASS GIS]

#70: imagery modules: strip @mapset part
--------------------------+-------------------------
  Reporter:  hamish       |      Owner:  grass-dev@…
      Type:  task         |     Status:  new
  Priority:  major        |  Milestone:  8.0.0
 Component:  Imagery      |    Version:  svn-trunk
Resolution:               |   Keywords:  imagery
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------
Changes (by marisn):

 * platform:   => Unspecified
 * milestone:  6.4.6 => 8.0.0
 * component:  Default => Imagery
 * cpu:   => Unspecified
 * type:  defect => task


Comment:

 GRASS 7.8.0 will contain code allowing i.group to list content of groups
 in other mapsets. It also handles correctly creation of groups with maps
 from other mapsets (fully qualified map names). It was implemented in
 r73633 and r74107. See also: #3491

 Still other imagery modules are working according to initial design –
 groups are useable only in the current mapset. Thus a new design should be
 proposed and modules changed to fit the new approach. I am not certain if
 such invasive changes should be done in GRASS 7.

 One of options would be to handle groups like raster colours – in each
 mapset an override (shadowing) could be implemented. If a module requests
 write option to group, files are written into current mapset and thus
 changes are visible only in the current mapset. Downside – changes are
 accessible only from current mapset – it could be problematical for sig
 files.

 Other approach would be to take signature files and classification results
 out from groups completely. There would be no big change in not writing
 classification output to group. With signature files it is more tricky, as
 new functions handling sig files then should be introduced or sig file
 handling should be shifted to the user (output to specified path/file
 instead of current mapset).

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/70#comment:23>
GRASS GIS <https://grass.osgeo.org>