Re: [GRASS-dev] [GRASS GIS] #3491: i.group cannot read from other mapsets

2019-05-01 Thread GRASS GIS
#3491: i.group cannot read from other mapsets
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Imagery  |Version:  unspecified
Resolution:  fixed|   Keywords:  i.group
   CPU:  All  |   Platform:  All
--+-
Changes (by marisn):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Replying to [comment:5 sbl]:
 > Partly fixed I would say:
 No, this issue is completely fixed as it was about i.group.

 > However, groups from other mapsets are still not fullly useable e.g. in
 i.cluster.
 > In addition, i.cluster seems to try to write to the imagery group
 directory in the other mapset (the signature file), so further adjustments
 downstreams seem to be required...
 This is a different issue. Groups are designed to be useable only in the
 current mapset. I changed i.group behaviour as I have new i. modules just
 reading from and not writing to groups and thus being fine with current
 changes. Other i. modules still follow the old design principles.

 I am closing this issue as fixed. A discussion on group/subgroup behaviour
 in context of i. modules writing their files into group should be held and
 accordingly new issues should be opened per each module not matching
 expected behaviour.
 See also: #3525 and https://marc.info/?l=grass-dev=152474676813985=2
 and https://marc.info/?l=grass-dev=152481635118286=2

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3491: i.group cannot read from other mapsets

2019-04-30 Thread GRASS GIS
#3491: i.group cannot read from other mapsets
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Imagery  |Version:  unspecified
Resolution:   |   Keywords:  i.group
   CPU:  All  |   Platform:  All
--+-

Comment (by sbl):

 Partly fixed I would say:


 {{{
 grass77 ./nc_spm_full_v2alpha/user1/ --exec i.group group=mygroup
 subgroup=subgroup input=aspect,basin,boundary --o

 Starting GRASS GIS...
 Cleaning up temporary files...
 Executing  ...
 Adding raster map  to group
 Adding raster map  to group
 Adding raster map  to group
 Adding raster map  to subgroup
 Adding raster map  to subgroup
 Adding raster map  to subgroup
 Execution of  finished.
 Cleaning up temporary files...


 grass77 ./nc_spm_full_v2alpha/stefan --exec i.group group=mygroup@user1 -l

 Starting GRASS GIS...
 Cleaning up temporary files...
 Executing  ...
 group  references the following raster maps
 -
  
 -
 Execution of  finished.
 Cleaning up default sqlite database ...
 Cleaning up temporary files...
 }}}

 However, groups from other mapsets are still not fullly useable e.g. in
 i.cluster.

 {{{
 grass77 ./nc_spm_full_v2alpha/stefan/ --exec i.cluster group=mygroup@user1
 subgroup=subgroup signaturefile=sign classes=3

 Starting GRASS GIS...
 Cleaning up temporary files...
 Executing  ...
 WARNING: Subgroup  doesn't have any raster maps
 ERROR: Subgroup must have at least 2 raster maps
 Execution of  finished.
 Cleaning up default sqlite database ...
 Cleaning up temporary files...

 }}}

 In addition, i.cluster seems to try to write to the imagery group
 directory in the other mapset (the signature file), so further adjustments
 downstreams seem to be required...

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3491: i.group cannot read from other mapsets

2019-04-30 Thread GRASS GIS
#3491: i.group cannot read from other mapsets
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Imagery  |Version:  unspecified
Resolution:   |   Keywords:  i.group
   CPU:  All  |   Platform:  All
--+-

Comment (by marisn):

 There have been some changes in group handling. IMHO this issue has been
 fixed in r73633 and r74107

 Please test with trunk.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3491: i.group cannot read from other mapsets

2019-04-29 Thread GRASS GIS
#3491: i.group cannot read from other mapsets
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Imagery  |Version:  unspecified
Resolution:   |   Keywords:  i.group
   CPU:  All  |   Platform:  All
--+-
Changes (by sbl):

 * milestone:  7.2.4 => 7.8.0


Comment:

 Enhancement tickets should point to 7.8.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3491: i.group cannot read from other mapsets

2018-02-06 Thread GRASS GIS
#3491: i.group cannot read from other mapsets
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Imagery  |Version:  unspecified
Resolution:   |   Keywords:  i.group
   CPU:  All  |   Platform:  All
--+-

Comment (by neteler):

 The group management has been discussed long time back, see also #70 and

 https://lists.osgeo.org/pipermail/grass-dev/2008-June/038371.html

 However, things can certainly be discussed and their technical feasibility
 be revisited again.

--
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev