[GRASS-dev] [GRASS GIS] #2219: wish: all modules that create a new map should put the module call into history

[GRASS GIS]

#2219: wish: all modules that create a new map should put the module call into
history
---------------------------------+------------------------------------------
 Reporter:  mlennert             |       Owner:  grass-dev@…              
     Type:  enhancement          |      Status:  new                      
 Priority:  normal               |   Milestone:  7.0.0                    
Component:  Vector               |     Version:  svn-trunk                
 Keywords:  history module call  |    Platform:  All                      
      Cpu:  Unspecified          |  
---------------------------------+------------------------------------------

Comment(by mlennert):

 Replying to [comment:4 neteler]:
 > Replying to [comment:3 mlennert]:
 >  * vector/v.vect.stats/main.c
 >    * not generating a map

 No, but having the command history to see which command call was used to
 fill the attribute column could be useful...

 >  * vector/v.lrs/v.lrs.label/main.c
 >    * done in r59251
 >  * vector/v.lrs/v.lrs.create/main.c
 >    * done in r59252
 >  * vector/v.lrs/v.lrs.segment/main.c
 >    * done in r59253
 >  * vector/v.net.visibility/main.c
 >    * done in r59247; additionally r59248

 Thanks !

 >  * vector/v.kcv/main.c
 >    * not generating a map

 Agreed that it's not really useful here.

 > TODO: Here is would be nice to "inject" the vector cmd history into the
 > raster history function (no idea how?) in order to write it out for the
 > raster output:
 >  * vector/v.surf.idw/main.c
 >  * vector/v.neighbors/main.c
 >  * vector/v.to.rast3/main.c

 This should be the same as v.to.rast, no ?

 How about the other way around: raster->vector modules ?

 But again, my main issue is actually that to see that history you have to
 use the -h flag for vectors, but not for rasters...

 Moritz

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2219#comment:5>
GRASS GIS <http://grass.osgeo.org>