#789: g.region option to expand the computational region of about "some" pixels?
-------------------------+-------------------------------------------------
  Reporter:  nikos       |      Owner:  grass-dev@…
      Type:              |     Status:  closed
  enhancement            |
  Priority:  normal      |  Milestone:  7.4.1
 Component:  Default     |    Version:  unspecified
Resolution:  fixed       |   Keywords:  g.region, expand computational
       CPU:              |  region
  Unspecified            |   Platform:  Unspecified
-------------------------+-------------------------------------------------

Comment (by wenzeslaus):

 I did the change in r72296. Here is a diff of only the naming change:

 {{{
 #!diff
 Index: main.c
 ===================================================================
 --- main.c      (revision 72295)
 +++ main.c      (working copy)
 @@ -337,13 +337,15 @@
      parm.pixels = G_define_option();
 -    parm.pixels->key = "pixels";
 +    parm.pixels->key = "grow";
      parm.pixels->key_desc = "value";
      parm.pixels->required = NO;
      parm.pixels->multiple = NO;
      parm.pixels->type = TYPE_INTEGER;
 -    parm.pixels->description =
 -    _("Number of pixels to increase the bounding box");
 +    parm.pixels->label =
 +       _("Number of cells to add to each side of the current region
 extent");
 +    parm.pixels->description =
 +       _("A negative number shrinks the current region extent");
      parm.pixels->guisection = _("Bounds");
 }}}

 The is an issue with shrinking now reported in #3509.

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

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

Reply via email to