#789: g.region option to expand the computational region of about "some" pixels? --------------------------+------------------------------------------------- Reporter: nikos | Owner: grass-dev@lists.osgeo.org Type: enhancement | Status: new Priority: normal | Milestone: 7.0.0 Component: default | Version: unspecified Resolution: | Keywords: g.region, expand computational region Platform: Unspecified | Cpu: Unspecified --------------------------+------------------------------------------------- Comment (by hamish):
did you try the g.region align=rastermap option? fwiw, -a grows outwards. > Matching the region over a point map is the problem! The > points at the borders (happens quite often to me when the > resolution of the raster map is low and so does the > resolution of the region successively) are not taken > into account. could you explain that more? I don't understand it. can you provide an example using Spearfish's bugsites + elevation.dem or something from the NC standard dataset? fwiw the region growing I've done has always been for cosmetic reasons. in those cases usually make the res=res*2 (or 10) with the -a flag, then run g.region again with the original region value. Hamish -- Ticket URL: <https://trac.osgeo.org/grass/ticket/789#comment:1> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev