On Mon, Apr 9, 2012 at 12:08 PM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
I can confirm there are issues in how GRASS 7 handles region settings. In my
case, when using v.to.rast, the region settings are reset to the default,
i.e., the raster is converted using the default region settings rather then
the current. I am now at revision 51177. In a previous revision (51117) I
had a problem with region settings when using r.patch, see Ticket #1636
(http://trac.osgeo.org/grass/ticket/1636). These issues seem to be
independend of the mapset (it happens in both PERMANENT and other mapsets).
I can not reproduce this problem. I tested in the North Carolina
dataset, mapset user1.
I displayed boundary_county, zoomed to the default region. Then I
zoomed to a small part of the boundary_county vector and set the
region from display. Then I zoomed to a different part of the vector
that does not overlap with the current region. Thus the current
region, the default region, and the display extents were all different
from each other. Then I ran v.to.rast on the boundary_county vector.
v.to.rast correctly used the current region and nothing was changed
after v.to.rast was completed. This is r51306.
Markus M
Paulo
On 04/09/2012 08:44 AM, Pankaj Kr Sharma wrote:
Dear Grass users and developers,
I just noticed that in grass70 , the v.to.rast module changes computational
region / current region
resolution to the display extent and resolution after finishing.
My maps are in "PERMANENT" mapset. And, I have tried a number of options ,
but cannot reset the resolution of raster thus created to the required
resolution.
Thanks.
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user