[GRASS-dev] [GRASS GIS] #2409: last call for options keys consolidation

GRASS GIS trac at osgeo.org
Fri Nov 28 07:32:34 PST 2014

#2409: last call for options keys consolidation
 Reporter:  martinl               |       Owner:  grass-dev@…              
     Type:  task                  |      Status:  new                      
 Priority:  blocker               |   Milestone:  7.0.0                    
Component:  Default               |     Version:  unspecified              
 Keywords:  standardized options  |    Platform:  Unspecified              
      Cpu:  Unspecified           |  

Comment(by wenzeslaus):

 Replying to [comment:69 martinl]:
 > Replying to [comment:68 huhabla]:
 > > If such invasive changes are performed, then i would expect that all
 the consequences of these changes are recognized and fixed before the
 > I will fix it today.

 Before doing so, I would suggest to re-think the change, especially the
 one for 3D raster. We don't have an agreement and I even don't see what
 you are currently trying to implement:

 > d.legend --h 2>&1 | grep 3D
 raster3d   Name of 3D raster map
 > g.region --h 2>&1 | grep 3D
 3draster   Set region to match 3D raster map(s) (both 2D and 3D values)
 res3   3D grid resolution (north-south, east-west and top-bottom)

 Moreover, I'm not sure what do you want to do with module names such as
 `d.rast`, `r.to.rast3` and all temporal datatypes.

 Please, react also to the notes made by [comment:34 me], [comment:54 Anna]
 and [comment:68 Soeren] about the need for the change and the motivation
 behind the decisions for change of `rast3d` to `raster3d/3draster/volume`.
 From what was said I would especially point out that it seems to me that
 possibility to shorten the options is valued much more than documentation
 consistency and Python interface.

Ticket URL: <http://trac.osgeo.org/grass/ticket/2409#comment:70>
GRASS GIS <http://grass.osgeo.org>

More information about the grass-dev mailing list