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

GRASS GIS trac at osgeo.org
Sun Jan 11 17:17:59 PST 2015

#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:189 glynn]:
 > Replying to [comment:187 wenzeslaus]:
 > > `r.mapcalculator` may create some confusion because is not part of
 standard GRASS GIS distribution (compilation switched off by default). It
 is also not in the documentation. I don't know if the confusion is also on
 the QGIS site. Another issue is that it is in Shell, not Python, so it
 should not work in GRASS 7 on MS Windows as far as I understand. Finally,
 so revision of messages is needed, error message "Calculating
 $GIS_OPT_OUTFILE. Try expert mode." shown after `r.mapcalc` failed just
 caught my eye.
 > r.mapcalculator was never converted to Python. It was deemed unnecessary
 now that r.mapcalc uses G_parser(). r.mapcalculator was created when
 r.mapcalc didn't use G_parser() which meant that it couldn't generate a
 GUI option dialog.
 > If there's some situation where it's useful, it should be converted to
 Python. Otherwise, it should be removed from the 7.0 tree.

 I think it is needed for QGIS and perhaps other things wrapping GRASS
 modules. Although I don't know much, the issue appears to be that they
 don't know what maps needs to be prepared. I've never really studied the
 problem. There might be some other way for callers to deal with the
 expression. For example, temporal framework also wraps `r.mapcalc` and its
 quite successful. Or `r.mapcalc` or some module derived from it (similarly
 as `r3.mapcalc` is) can just parse the expression and output the names in
 some key-value/parseable form, or there can be a Python function for it.
 Some inside from application developers using GRASS GIS would be helpful.

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

More information about the grass-dev mailing list