#789: g.region option to expand the computational region of about "some" pixels?
---------------------------------------------------+------------------------
Reporter: nikos | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Default | Version: unspecified
Keywords: g.region, expand computational region | Platform: Unspecified
Cpu: Unspecified |
---------------------------------------------------+------------------------
Comment(by nikosa):
Replying to [comment:11 hamish]:
> your initial idea of "g.region -a vect=mmmm res=xxxx" solves it. Set the
resolution to 1000 there (or whatever) and the -a flag will ''always''
grow outwards in all 4 directions. So you run the above, then run g.region
a second time with your finer resolution. If your second finer-resolution
fits evenly in the initial coarser one, you now have a grown region with
bounds rounded to nice whole numbers, a bit bigger than your points map so
catching them all!
Maybe it does so. And, maybe I have placed, in the example above, the
{{{
# assume that the raster was just about the same size of what the
(grass-)region is:
r.mapcalc landcover_cropped = landcover.30m
}}}
in the "wrong" place. This was part of my "pareto" implementation using
MODIS data (low-res, to be assessed) and Landsat (higher-res, as a
reference). I have to go through this again. If I remember well, I was
forced to have "this" very step in-between of the grid creation/centroid
extraction operations.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/789#comment:12>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
