[GRASS-dev] [GRASS GIS] #3538: add r.clip into core modules

[GRASS GIS]

#3538: add r.clip into core modules
--------------------------+-------------------------
  Reporter:  martinl      |      Owner:  grass-dev@…
      Type:  task         |     Status:  new
  Priority:  normal       |  Milestone:  7.6.0
 Component:  Raster       |    Version:  svn-trunk
Resolution:               |   Keywords:  r.clip
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------

Comment (by wenzeslaus):

 Replying to [comment:7 Nikos Alexandris]:
 > Replying to [comment:5 martinl]:
 > > Replying to [comment:4 martinl]:
 > > > Replying to [comment:2 Nikos Alexandris]:
 > > > > I would (re-)name it to `r.extract` or reword the
 label/description of the module to read something like: "Clips out portion
 from the input map based on either the extent of the current region or a
 vector map".
 > > >
 > > > -1 `r.extract` brings more confusion which is not really necessary.
 `r.clip` does the same as G7:v.clip - clips input raster/vector map based
 on current region or vector map if defined.
 > >
 > > It remembers me issue with G7:v.clip label
 > >
 > > {{{
 > > Extracts features of input map which overlay features of clip map.
 > > }}}
 > >
 > > something like
 > >
 > > {{{
 > > Clips features of input vector map which overlay features of clip map.
 > > }}}
 > >
 > > We could also sync modules, modify `r.clip` as below:
 > >
 > > * vector -> clip (required)
 > > * add -r flag
 > >
 > > ?
 >
 > Why not. It would make things more clear I guess.

 I'm not sure if I understand, why is clip required? The reason I wrote
 r.clip was getting just the portion of the raster map which in the
 computational region and clip by vector makes sense too. Does `required:
 clip, -r` rule (G7:g.parser) fit with your intention?

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