I was mainly just surprised as I thought I remembered (incorrectly it seems)
that all raster commands that create new maps respect the computational region.
Michael Barton
School of Human Evolution Change
School of Complex Adaptive System Science
Center for Social Dynamics & Complexity
Arizona
On Sun, Mar 3, 2024 at 2:48 AM Vaclav Petras via grass-dev
wrote:
>> On March 2, 2024 1:00:23 AM GMT+01:00, Michael Barton via grass-dev
>> wrote:
>> >It's been awhile since I've done this but I thought I remembered that a new
>> >map created with r.copy is constrained by the computational
Thanks. I’ll check it out
__
Michael Barton
Sent from my iPhone
Please excusr any typoz
On Mar 2, 2024, at 6:48 PM, Vaclav Petras wrote:
On Sat, 2 Mar 2024 at 07:04, Paulo van Breugel via grass-dev
mailto:grass-dev@lists.osgeo.org>> wrote:
On March 2, 2024 1:00:23 AM
On Sat, 2 Mar 2024 at 07:04, Paulo van Breugel via grass-dev <
grass-dev@lists.osgeo.org> wrote:
>
>
> On March 2, 2024 1:00:23 AM GMT+01:00, Michael Barton via grass-dev <
> grass-dev@lists.osgeo.org> wrote:
> >It's been awhile since I've done this but I thought I remembered that a
> new map
On March 2, 2024 1:00:23 AM GMT+01:00, Michael Barton via grass-dev
wrote:
>It's been awhile since I've done this but I thought I remembered that a new
>map created with r.copy is constrained by the computational region. That does
>not seem to the case, at least in 8.4 dev. Maybe it has
It's been awhile since I've done this but I thought I remembered that a new map
created with r.copy is constrained by the computational region. That does not
seem to the case, at least in 8.4 dev. Maybe it has been this way for awhile
(long while?) and I didn't notice it.
Michael
