[GRASS-dev] [GRASS GIS] #789: g.region option to expand the computational region of about "some" pixels?
GRASS GIS
trac at osgeo.org
Sun Feb 4 16:35:53 PST 2018
#789: g.region option to expand the computational region of about "some" pixels?
-------------------------+-------------------------------------------------
Reporter: nikos | Owner: grass-dev@…
Type: | Status: new
enhancement |
Priority: normal | Milestone: 7.4.1
Component: Default | Version: unspecified
Resolution: | Keywords: g.region, expand computational
CPU: | region
Unspecified | Platform: Unspecified
-------------------------+-------------------------------------------------
Comment (by lucadelu):
Replying to [comment:20 mmetz]:
>
> The number of pixels is just a number, not a coordinate, therefore the
new option should be of type TYPE_DOUBLE and scanned with sscanf(), not
G_scan_easting()/G_scan_northing(). Should top and bottom also be
adjusted?
Thanks Markus, I modify the patch with your suggestion, just one question,
why TYPE_DOUBLE and not INTEGER (I used INT)?
because the number of pixels should be integer, I don't think is good idea
to permit to add 2.5 pixels ;-)
However I have no answer about top/bottom, I never used them. I try to run
{{{
g.region t=t+8
}}}
or
{{{
g.region t=800
}}}
but nothing changed in the output of g.region -p, so no idea...
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/789#comment:21>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list