[GRASS-user] Problem with r.basin in grass7

[Andrea_Timmermann]

Dear all,

I am running into problems when running r.basin (grass 7.0, win7). I use:
r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801 threshold=19005 dir=“C:\Users\Andrea\Basins”

This is what I get:

"…
‘r.stream.snap’ is not recognized as an internal or external
command,
operable program or batch file.
ERROR: Vector map <o_map_outlet_snap> not found
‘r.stream.basins’ is not recognized as an internal or
external command,
operable program or batch file.
Delineation of basin done
Invalid map <o_map_basin>
Invalid map <o_map_basin>
Parse error
ERROR: parse error
ERROR: An error occurred while running r.mapcalc
------------------------------
An ERROR occurred running r.basin
Please try with another pairs of outlet coordinates"

I have tried with many pairs of coordinates and think that this is not the problem.
I did not find anything about r.streams.snap, but i tried unsuccessfully to install r.stream.basins:

"Downloading precompiled GRASS Addons <r.stream.basins>…
Updating metadata file…
ERROR: Unable to read manual page: [Errno 2] No such file or directory: ‘C:\Users\Andrea\AppData\Roaming\GRASS7\addons\docs\html\r.stream.basins.html’

Does anyone know what the problem is ?

Thank you,
Cheers, Andrea

[neteler]

Hi,

On Thu, Oct 23, 2014 at 4:48 PM, Andrea Timmermann <timmermann@gmx.at> wrote:

Dear all,

I am running into problems when running r.basin (grass 7.0, win7). I use:
r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir="C:\\Users\\Andrea\\Basins"

This is what I get:

".....
'r.stream.snap' is not recognized as an internal or external
command,

...

At time most r.stream.* are disabled in GRASS 7.0.svn.
They are enabled in GRASS 7.1.svn, awaiting further improvements (see
http://trac.osgeo.org/grass/ticket/2296).

We need to decide if we want to move back r.stream.* from GRASS
7.0.svn to Addons.

Markus

[Andrea_Timmermann]

Hi Markus,

Thanks for your response.
I installed the latest 7.1 version, but still have a problem …

When running:
r.basin map=map@Elevation prefix=p coordinates=-71.10394196,43.9865230801 threshold=19005 dir=“C:\Users\Carolits\Basins”

I get:

…
Pass 4 of 4:
Reading features…
Writing raster map…
Converted points/lines: 1 of 1…
v.to.rast complete.
All in RAM calculation…
Reading raster map <p_map_drainage_e>…
Calculating basins using vector point map…
Writing raster map <p_map_basin>…
Delineation of basin done
ERROR: output map exists
ERROR: An error occurred while running r.mapcalc
------------------------------
An ERROR occurred running r.basin
Please try with another pairs of outlet coordinates

Regards,
Andrea.

Gesendet: Donnerstag, 23. Oktober 2014 um 17:15 Uhr
Von: “Markus Neteler” neteler@osgeo.org
An: “Andrea Timmermann” timmermann@gmx.at
Cc: “GRASS user list” grass-user@lists.osgeo.org
Betreff: Re: [GRASS-user] Problem with r.basin in grass7
Hi,

On Thu, Oct 23, 2014 at 4:48 PM, Andrea Timmermann timmermann@gmx.at wrote:

Dear all,

I am running into problems when running r.basin (grass 7.0, win7). I use:
r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir=“C:\Users\Andrea\Basins”

This is what I get:

"…
‘r.stream.snap’ is not recognized as an internal or external
command,
…

At time most r.stream.* are disabled in GRASS 7.0.svn.
They are enabled in GRASS 7.1.svn, awaiting further improvements (see
http://trac.osgeo.org/grass/ticket/2296).

We need to decide if we want to move back r.stream.* from GRASS
7.0.svn to Addons.

Markus

[neteler]

Hi Andrea,

On Thu, Oct 23, 2014 at 9:49 PM, Andrea Timmermann <timmermann@gmx.at> wrote:

Hi Markus,

Thanks for your response.
I installed the latest 7.1 version, but still have a problem ...

When running:
r.basin map=map@Elevation prefix=p coordinates=-71.10394196,43.9865230801
threshold=19005 dir="C:\\Users\\Carolits\\Basins"

I get:
...
Pass 4 of 4:
Reading features...
Writing raster map...
Converted points/lines: 1 of 1....
v.to.rast complete.
All in RAM calculation...
Reading raster map <p_map_drainage_e>...
Calculating basins using vector point map...
Writing raster map <p_map_basin>...
Delineation of basin done
ERROR: output map <tmp> exists

I guess that the internal overwrite setting was missing, please try my
attempt [1] to fix that (fetch the r.basins with the extension manager
to get it, but since you are on Windows you may need to way till
tomorrow or simply modify the Python script at your end with a text
editor - just add one line).

Please let us know how it goes,
Markus

[1] http://trac.osgeo.org/grass/changeset/62365

[Andrea_Timmermann]

Hi Markus,

Thanks for your answer! I have now however another problem …
When running:

r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801 threshold=19005 dir=C:\Users\Andrea\Basins

I get:
" …

v.to.rast complete.
All in RAM calculation…
Reading raster map <o_map_drainage_e>…
Calculating basins using vector point map…
Current region rows: 21612, cols: 21612
ERROR: G_calloc: unable to allocate 21612 * 4 bytes of memory at io.c:41
Delineation of basin done
Invalid map <o_map_basin>
Invalid map <o_map_basin>
Parse error
ERROR: parse error
ERROR: An error occurred while running r.mapcalc"

The computer I am using now has 12GB RAM and still over 160 GB of harddisk space, so I don’t really know what this error means…

Regards, Andrea.

Gesendet: Donnerstag, 23. Oktober 2014 um 22:29 Uhr
Von: “Markus Neteler” neteler@osgeo.org
An: “Andrea Timmermann” timmermann@gmx.at
Cc: “GRASS user list” grass-user@lists.osgeo.org
Betreff: Re: Re: [GRASS-user] Problem with r.basin in grass7
Hi Andrea,

On Thu, Oct 23, 2014 at 9:49 PM, Andrea Timmermann timmermann@gmx.at wrote:

Hi Markus,

Thanks for your response.
I installed the latest 7.1 version, but still have a problem …

When running:
r.basin map=map@Elevation prefix=p coordinates=-71.10394196,43.9865230801
threshold=19005 dir=“C:\Users\Carolits\Basins”

I get:
…
Pass 4 of 4:
Reading features…
Writing raster map…
Converted points/lines: 1 of 1…
v.to.rast complete.
All in RAM calculation…
Reading raster map <p_map_drainage_e>…
Calculating basins using vector point map…
Writing raster map <p_map_basin>…
Delineation of basin done
ERROR: output map exists

I guess that the internal overwrite setting was missing, please try my
attempt [1] to fix that (fetch the r.basins with the extension manager
to get it, but since you are on Windows you may need to way till
tomorrow or simply modify the Python script at your end with a text
editor - just add one line).

Please let us know how it goes,
Markus

[1] http://trac.osgeo.org/grass/changeset/62365

[neteler]

Hi Andrea,

On Fri, Oct 24, 2014 at 3:27 PM, Andrea Timmermann <timmermann@gmx.at> wrote:

Hi Markus,

Thanks for your answer! I have now however another problem ...
When running:

r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir=C:\\Users\\Andrea\\Basins

I get:
" ....
v.to.rast complete.
All in RAM calculation...
Reading raster map <o_map_drainage_e>...
Calculating basins using vector point map...
Current region rows: 21612, cols: 21612
ERROR: G_calloc: unable to allocate 21612 * 4 bytes of memory at io.c:41

So, starting with GRASS 7 revision r62444 (see startup screen or
g.version -g) you will be told *which* module actually failed, so the
G_calloc error will be more useful. To get that, you will need to
update your GRASS GIS 7 installation.

However, a few thoughts before:

Current region rows: 21612, cols: 21612
i.e. 467078544 cells at 24 bytes/cell (AFAIK). That is:

467078544 * 24 / 1024 / 1024/ 1024

[1] 10.44002

Leaving a bit for the operating system etc, you may exceed 12GB RAM if
I got the numbers right.

Are you sure that you want to use 467 million cells? If not, check
"g.region -p", perhaps the computational region resolution is too
high?

best
Markus

[Andrea_Timmermann]

Hi Markus,

Thanks for your help!

We got some more RAM, changed the basins I was using (got smaller ones) and reduced the resolution of the computational region, so I hope I do not run into memory problems.

I downloaded the new grass version and run:
r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801 threshold=19005 dir=“C:\Users\Andrea\Basins”

I get:
"…
Number of isles: 0
ERROR: option : <o_map_outlet_snap> exists.
Reading features…
Writing raster map…
Converted points/lines: 1 of 1
v.to.rast complete.
ERROR: Module built against version $Revision: 62060 $ but trying to use version $Revision: 62364 $. You need to rebuild GRASS GIS or untangle multiple installations.
Delineation of basin done
Invalid map <o_map_basin>
Invalid map <o_map_basin>
Parse error
ERROR: parse error
ERROR: An error occurred while running r.mapcalc"

I still have grass 6.4.4 and grass 7.0 installed, maybe I have too many grasses on my machine ?

I also have two more questions:

• Should I set the computational region to the whole raster map I am using or to the vector map defining my basin? (I tried both alternatives and r.basin writes something a bit different on the screen depending on what I use)
  I am using a mask based on my vector map, so maybe the computations are anyways done only for the area covered by the basin?

• You wrote that I might have 24 bytes/cell … How can I find out how many bytes/cell my raster has? I did not find any information about that and just would like to know …

Thanks!
Regards,
Andrea.

Gesendet: Dienstag, 28. Oktober 2014 um 17:13 Uhr
Von: “Markus Neteler” neteler@osgeo.org
An: “Andrea Timmermann” timmermann@gmx.at
Cc: “GRASS user list” grass-user@lists.osgeo.org
Betreff: Re: Re: Re: [GRASS-user] Problem with r.basin in grass7
Hi Andrea,

On Fri, Oct 24, 2014 at 3:27 PM, Andrea Timmermann timmermann@gmx.at wrote:

Hi Markus,

Thanks for your answer! I have now however another problem …
When running:

r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir=C:\Users\Andrea\Basins

I get:
" …
v.to.rast complete.
All in RAM calculation…
Reading raster map <o_map_drainage_e>…
Calculating basins using vector point map…
Current region rows: 21612, cols: 21612
ERROR: G_calloc: unable to allocate 21612 * 4 bytes of memory at io.c:41

So, starting with GRASS 7 revision r62444 (see startup screen or
g.version -g) you will be told which module actually failed, so the
G_calloc error will be more useful. To get that, you will need to
update your GRASS GIS 7 installation.

However, a few thoughts before:

Current region rows: 21612, cols: 21612
i.e. 467078544 cells at 24 bytes/cell (AFAIK). That is:

467078544 * 24 / 1024 / 1024/ 1024
[1] 10.44002

Leaving a bit for the operating system etc, you may exceed 12GB RAM if
I got the numbers right.

Are you sure that you want to use 467 million cells? If not, check
“g.region -p”, perhaps the computational region resolution is too
high?

best
Markus

[neteler]

HI Andrea,

On Fri, Oct 31, 2014 at 3:18 PM, Andrea Timmermann <timmermann@gmx.at> wrote:

Hi Markus,

Thanks for your help!

We got some more RAM, changed the basins I was using (got smaller ones) and
reduced the resolution of the computational region, so I hope I do not run
into memory problems.

I downloaded the new grass version and run:
r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir="C:\\Users\\Andrea\\Basins"

I get:
"...
Number of isles: 0
ERROR: option <output>: <o_map_outlet_snap> exists.

---> apparently the overwrite fails or you did not specify --o or old
cruft remained as indicated (please clean it first).

Reading features...
Writing raster map...
Converted points/lines: 1 of 1
v.to.rast complete.
ERROR: Module built against version $Revision: 62060 $ but trying to use
version $Revision: 62364 $. You need to rebuild GRASS GIS or untangle
multiple installations.

Mhh, "this should not happen" issue. In a winGRASS installer there
should not be any version mixture.
Helli, Martin, any ideas?

[...]

I still have grass 6.4.4 and grass 7.0 installed, maybe I have too many
grasses on my machine ?

No, that should be fine. At time we are doing heavy cleanup in 7, to
get stuff ready for beta4. Perhaps the installer was autogenerated in
a bad moment. Please be patient and update it again, for us your
feedback is very important.

I also have two more questions:
- Should I set the computational region to the whole raster map I am using
or to the vector map defining my basin? (I tried both alternatives and
r.basin writes something a bit different on the screen depending on what I
use)

This is a question for the author of r.basin, I don't know.

I am using a mask based on my vector map, so maybe the computations are
anyways done only for the area covered by the basin?

... also here.

- You wrote that I might have 24 bytes/cell .. How can I find out how many
bytes/cell my raster has? I did not find any information about that and just
would like to know ...

Here is an overview, I hope it is right

http://grasswiki.osgeo.org/wiki/GRASS_raster_semantics

best,
Markus

[madi]

Dear Andrea,

···

On Sun, Nov 2, 2014 at 6:26 PM, Markus Neteler <neteler@osgeo.org> wrote:

HI Andrea,

On Fri, Oct 31, 2014 at 3:18 PM, Andrea Timmermann <timmermann@gmx.at> wrote:

Reading features…
Writing raster map…
Converted points/lines: 1 of 1
v.to.rast complete.
ERROR: Module built against version $Revision: 62060 $ but trying to use
version $Revision: 62364 $. You need to rebuild GRASS GIS or untangle
multiple installations.

Mhh, “this should not happen” issue. In a winGRASS installer there
should not be any version mixture.
Helli, Martin, any ideas?

Did you update G7 without updating the r.stream* perhaps? I’m not sure if this would lead to the error above mentioned, but to give it a try, please remove and then reistall the r.stream modules using g.extension

[…]

I also have two more questions:

• Should I set the computational region to the whole raster map I am using
  or to the vector map defining my basin? (I tried both alternatives and
  r.basin writes something a bit different on the screen depending on what I
  use)

This is a question for the author of r.basin, I don’t know.

The vector map defining your basin is actually an output of the module. You should set the computational region to include the closing section and the area above it up to the ridges (the top of the mountains). This is the best guess on where your basin is more or less contained. If your entire raster is reasonably small, it is OK to set the computational region to the whole raster, otherwhise, you should try to include the ridges that define your basin of interest. If your selection is wrong, you’ll be able anyway to detect it because your basin will extend to the limits of your computational region. In this case you will know that you should extend the computational region.

I am using a mask based on my vector map, so maybe the computations are
anyways done only for the area covered by the basin?

… also here.

No, the module does not reduce the region automatically. My suggestion would be to set the computational region reasonably larger than the vector and not to use it as a mask. This is because it could prevent including cells that drain into the basin. You can prove it running r.watershed on the raster masked by the polygon representing the basin. Query the flow accumulation that you obtain (you can use r.mapcalc) to see if there are negative values. The negative values are conventionally used in r.watershed to detect cels that are “incomplete” as sinks for other cells to drain into.

Hope this helps,
madi

–

Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-leo@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.

[Andrea_Timmermann]

Dear Markus and Madi,

thanks for your comments !

The problems I had before appeared with the grass version of the 31.10, I downloaded the version of the 30.10 and also reinstalled the r.streams.basins, as suggested by Madi. I could not install the remaining r.stream modules. When I tried to do so I got:

“…
…
7.1.svn\Python27\lib\zipfile.py", line 766, in init
self._RealGetContents()
File “C:\Program Files (x86)\GRASS GIS
7.1.svn\Python27\lib\zipfile.py”, line 807, in
_RealGetContents
raise BadZipfile, “File is not a zip file”
zipfile.BadZipfile: File is not a zip file”

I run r.basin anyways after deleting all files (as suggested by Markus):
r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801 threshold=19005 dir=C:\Users\Andrea\Basins

and I got

“…
ERROR: option : <o_map_outlet_snap> exists.
…
Calculating basins using vector point map…
Writing raster map <o_map_basin>…
Delineation of basin done
ERROR: output map <o_map_mask> exists
ERROR: An error occurred while running r.mapcal”

Markus wrote:

"> apparently the overwrite fails or you did not specify --o or old

cruft remained as indicated (please clean it first)"

I deleted all files before running the r.basin command and I do not know how I can set a –o for the file <o_map_outlet_snap> in my r.basin command … I do not know what you mean with the “old cruft” …

I will reinstall grass on Monday or Tuesday with the newest version and will tell you how it goes.

Please be patient and update it again, for us your
feedback is very important.

I still have a lot of patience and am glad to be able to help you a bit! I think grass is really a good thing !!!

Regards,
Andrea

Gesendet: Sonntag, 02. November 2014 um 18:26 Uhr
Von: “Markus Neteler” neteler@osgeo.org
An: “Andrea Timmermann” timmermann@gmx.at
Cc: “GRASS user list” grass-user@lists.osgeo.org, “Margherita Di Leo” dileomargherita@gmail.com
Betreff: Re: Re: Re: Re: [GRASS-user] Problem with r.basin in grass7
HI Andrea,

On Fri, Oct 31, 2014 at 3:18 PM, Andrea Timmermann timmermann@gmx.at wrote:

Hi Markus,

Thanks for your help!

We got some more RAM, changed the basins I was using (got smaller ones) and
reduced the resolution of the computational region, so I hope I do not run
into memory problems.

I downloaded the new grass version and run:
r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir=“C:\Users\Andrea\Basins”

I get:
"…
Number of isles: 0
ERROR: option : <o_map_outlet_snap> exists.

—> apparently the overwrite fails or you did not specify --o or old
cruft remained as indicated (please clean it first).

Reading features…
Writing raster map…
Converted points/lines: 1 of 1
v.to.rast complete.
ERROR: Module built against version $Revision: 62060 $ but trying to use
version $Revision: 62364 $. You need to rebuild GRASS GIS or untangle
multiple installations.

Mhh, “this should not happen” issue. In a winGRASS installer there
should not be any version mixture.
Helli, Martin, any ideas?

[…]

I still have grass 6.4.4 and grass 7.0 installed, maybe I have too many
grasses on my machine ?

No, that should be fine. At time we are doing heavy cleanup in 7, to
get stuff ready for beta4. Perhaps the installer was autogenerated in
a bad moment. Please be patient and update it again, for us your
feedback is very important.

I also have two more questions:

• Should I set the computational region to the whole raster map I am using
  or to the vector map defining my basin? (I tried both alternatives and
  r.basin writes something a bit different on the screen depending on what I
  use)

This is a question for the author of r.basin, I don’t know.

I am using a mask based on my vector map, so maybe the computations are
anyways done only for the area covered by the basin?

… also here.

• You wrote that I might have 24 bytes/cell … How can I find out how many
  bytes/cell my raster has? I did not find any information about that and just
  would like to know …

Here is an overview, I hope it is right

http://grasswiki.osgeo.org/wiki/GRASS_raster_semantics

best,
Markus

[hellik]

hi,

Andrea Timmermann wrote

Dear Markus and Madi,

&nbsp;

thanks for your comments !&nbsp;
&nbsp;
The problems I had before appeared with the grass version of the 31.10, I
downloaded the version of the 30.10 and also reinstalled the
r.streams.basins, as suggested by Madi. I could not install the remaining
r.stream modules. When I tried to do so I got:
&nbsp;
&ldquo;...
...
7.1.svn&#92;Python27&#92;lib&#92;zipfile.py&quot;, line 766, in __init__
&nbsp;&nbsp;&nbsp; self._RealGetContents()
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn&#92;Python27&#92;lib&#92;zipfile.py&quot;, line 807, in
_RealGetContents
&nbsp;&nbsp;&nbsp; raise BadZipfile, &quot;File is not a zip file&quot;
zipfile.BadZipfile: File is not a zip file&rdquo;
&nbsp;

&nbsp;

I run r.basin anyways after deleting all files (as suggested by Markus):
r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir=C:&#92;&#92;Users&#92;&#92;Andrea&#92;&#92;Basins
&nbsp;
and I got
&nbsp;
&ldquo;....
ERROR: option &lt;output&gt;: &lt;o_map_outlet_snap&gt; exists.
...
Calculating basins using vector point map...
Writing raster map &lt;o_map_basin&gt;...
Delineation of basin done
ERROR: output map &lt;o_map_mask&gt; exists
ERROR: An error occurred while running r.mapcal&rdquo;
&nbsp;

Markus wrote:

&nbsp;

&quot;&gt; apparently the overwrite fails or you did not specify --o or
old
&gt; cruft remained as indicated (please clean it first)&quot;

I deleted all files before running the r.basin command and I do not know
how I can set a &ndash;o for the file &lt;o_map_outlet_snap&gt; in my
r.basin command ... I do not know what you mean with the &quot;old
cruft&quot; ...
&nbsp;
I will reinstall grass on Monday or Tuesday with the newest version and
will tell you how it goes.&nbsp;
&nbsp;
&gt;Please be patient and update it again, for us your
&gt; feedback is very important.

&nbsp;

I still have a lot of patience and am glad to be able to help you a bit! I
think grass is really a good thing !!!

&nbsp;

Regards,&nbsp;

Andrea

&nbsp;

Gesendet:&nbsp;Sonntag, 02. November 2014 um 18:26 Uhr
Von:&nbsp;&quot;Markus Neteler&quot; &lt;

neteler@

&gt;
An:&nbsp;&quot;Andrea Timmermann&quot; &lt;

timmermann@

&gt;
Cc:&nbsp;&quot;GRASS user list&quot; &lt;

grass-user@.osgeo

&gt;, &quot;Margherita Di Leo&quot; &lt;

dileomargherita@

&gt;
Betreff:&nbsp;Re: Re: Re: Re: [GRASS-user] Problem with r.basin in grass7

HI Andrea,

On Fri, Oct 31, 2014 at 3:18 PM, Andrea Timmermann &lt;

timmermann@

&gt; wrote:
&gt; Hi Markus,
&gt;
&gt; Thanks for your help!
&gt;
&gt; We got some more RAM, changed the basins I was using (got smaller
ones) and
&gt; reduced the resolution of the computational region, so I hope I do
not run
&gt; into memory problems.
&gt;
&gt; I downloaded the new grass version and run:
&gt; r.basin map=map@Elevation prefix=o
coordinates=-71.10394196,43.9865230801
&gt; threshold=19005
dir=&quot;C:&#92;&#92;Users&#92;&#92;Andrea&#92;&#92;Basins&quot;
&gt;
&gt; I get:
&gt; &quot;...
&gt; Number of isles: 0
&gt; ERROR: option &lt;output&gt;: &lt;o_map_outlet_snap&gt; exists.

---&gt; apparently the overwrite fails or you did not specify --o or old
cruft remained as indicated (please clean it first).

&gt; Reading features...
&gt; Writing raster map...
&gt; Converted points/lines: 1 of 1
&gt; v.to.rast complete.
&gt; ERROR: Module built against version &#36;Revision: 62060 &#36; but
trying to use
&gt; version &#36;Revision: 62364 &#36;. You need to rebuild GRASS GIS or
untangle
&gt; multiple installations.

Mhh, &quot;this should not happen&quot; issue. In a winGRASS installer
there
should not be any version mixture.
Helli, Martin, any ideas?

[...]
&gt; I still have grass 6.4.4 and grass 7.0 installed, maybe I have too
many
&gt; grasses on my machine ?

No, that should be fine. At time we are doing heavy cleanup in 7, to
get stuff ready for beta4. Perhaps the installer was autogenerated in
a bad moment. Please be patient and update it again, for us your
feedback is very important.

&gt; I also have two more questions:
&gt; - Should I set the computational region to the whole raster map I am
using
&gt; or to the vector map defining my basin? (I tried both alternatives
and
&gt; r.basin writes something a bit different on the screen depending on
what I
&gt; use)

This is a question for the author of r.basin, I don&#39;t know.

&gt; I am using a mask based on my vector map, so maybe the computations
are
&gt; anyways done only for the area covered by the basin?

... also here.

&gt; - You wrote that I might have 24 bytes/cell .. How can I find out how
many
&gt; bytes/cell my raster has? I did not find any information about that
and just
&gt; would like to know ...

Here is an overview, I hope it is right

http://grasswiki.osgeo.org/wiki/GRASS_raster_semantics

best,
Markus

I've just done some test with r.basin and its dependencies of
r.stream.*-modules:

GRASS Version: 7.1.svn
GRASS SVN Revision: 62299
Erstellungsdatum: 2014-10-20
Build Platform: i686-pc-mingw32
GDAL/OGR: 1.11.0
PROJ.4: 4.8.0
GEOS: 3.4.2
SQLite: 3.7.17
Python: 2.7.4
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)

at the moment it seems there are some issues along

        grass.run_command('r.stream.basins', direction = r_drainage_e,
                                             basins = r_basin,
                                             points = v_outlet_snap,
                                             overwrite = True)

in r.basin.

maybe some building issues

as the r.stream.*-modules are still a moving window regarding
trunk/relbranch7 (all are just moved back to addons), we have to wait for
the nightly builds of OSGeo4W/standalone trunk/relbranch7 before further
tests are ready.

I'll do this in the next days.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Problem-with-r-basin-in-grass7-tp5169155p5170859.html
Sent from the Grass - Users mailing list archive at Nabble.com.

[Markus_Metz]

On Tue, Oct 28, 2014 at 5:13 PM, Markus Neteler <neteler@osgeo.org> wrote:

Hi Andrea,

On Fri, Oct 24, 2014 at 3:27 PM, Andrea Timmermann <timmermann@gmx.at> wrote:

Hi Markus,

Thanks for your answer! I have now however another problem ...
When running:

r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir=C:\\Users\\Andrea\\Basins

I get:
" ....
v.to.rast complete.
All in RAM calculation...
Reading raster map <o_map_drainage_e>...
Calculating basins using vector point map...
Current region rows: 21612, cols: 21612
ERROR: G_calloc: unable to allocate 21612 * 4 bytes of memory at io.c:41

So, starting with GRASS 7 revision r62444 (see startup screen or
g.version -g) you will be told *which* module actually failed,

This is not exactly true. You will be told where in the source code
memory allocation failed. This can be somewhere in a library, then you
don't know which module actually failed. You need to check the return
code of the module, as of r62566 automatically done by
grass.run_command in trunk.

Markus M

so the
G_calloc error will be more useful. To get that, you will need to
update your GRASS GIS 7 installation.

However, a few thoughts before:

Current region rows: 21612, cols: 21612
i.e. 467078544 cells at 24 bytes/cell (AFAIK). That is:

467078544 * 24 / 1024 / 1024/ 1024

[1] 10.44002

Leaving a bit for the operating system etc, you may exceed 12GB RAM if
I got the numbers right.

Are you sure that you want to use 467 million cells? If not, check
"g.region -p", perhaps the computational region resolution is too
high?

best
Markus
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

[Andrea_Timmermann]

Hi !

I downloaded the 5-Nov Grass and also updated all the addons extensions I use.

When I run:
“r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801 threshold=19005 dir="C:\Users\Andrea\Basins”

I get:
"…

Building topology for vector map o_map_outlet@Elevation…
Registering primitives…
One primitive registered
One vertex registered
Building areas…
0 areas built
0 isles built
Attaching islands…
Attaching centroids…
Number of nodes: 0
Number of primitives: 1
Number of points: 1
Number of lines: 0
Number of boundaries: 0
Number of centroids: 0
Number of areas: 0
Number of isles: 0
------------------------------
An ERROR occurred running r.basin
Please try with another pairs of outlet coordinates"

I tried to check the return code of the module as mentioned by Markus:

This is not exactly true. You will be told where in the source code
memory allocation failed. This can be somewhere in a library, then you
don’t know which module actually failed. You need to check the return
code of the module, as of r62566 automatically done by
grass.run_command in trunk.

but I could not find the file. Can you tell me where I can find it?

I have now another question …
I was thinking about the note on the wiki page which said that:"… perimeter is affected by a fractal problem and the number is mostly meaningless taken by itself. Hence, perimeter should never be mixed with anything from another dataset or even the same data set at a different cell resolution; it is only good as a percentage comparison to its neighbors in the same dataset.

And about the known issues at the same page: “r.basin hasn’t been designed for working in lat/long coordinates. This means that if you are working in lat/long coordinates, you need to reproject your map first in order to apply the tool”.

The DEMs I am using have a resolution of 0.33 degrees and when I reproject them (projection: 3 (Latitude-Longitude); zone: 0; datum: nad83; ellipsoid: grs80), the areas covered by the DEMs files vary depending on the longitude: the surface covered by one file is larger near the equator than closer to the poles. So I think this means that the cell resolution of my reprojected map is larger near the poles than at the equator? If so, it would only make sense to compare the morphometric parameters for catchments at a similar latitude I think… Am I right? I am a bit confused with this …

Thanks for your answers!
Regards, Andrea.

Gesendet: Mittwoch, 05. November 2014 um 09:55 Uhr
Von: “Markus Metz” markus.metz.giswork@gmail.com
An: “Markus Neteler” neteler@osgeo.org
Cc: “Andrea Timmermann” timmermann@gmx.at, “GRASS user list” grass-user@lists.osgeo.org
Betreff: Re: [GRASS-user] Problem with r.basin in grass7
On Tue, Oct 28, 2014 at 5:13 PM, Markus Neteler neteler@osgeo.org wrote:

Hi Andrea,

On Fri, Oct 24, 2014 at 3:27 PM, Andrea Timmermann timmermann@gmx.at wrote:

Hi Markus,

Thanks for your answer! I have now however another problem …
When running:

r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir=C:\Users\Andrea\Basins

I get:
" …
v.to.rast complete.
All in RAM calculation…
Reading raster map <o_map_drainage_e>…
Calculating basins using vector point map…
Current region rows: 21612, cols: 21612
ERROR: G_calloc: unable to allocate 21612 * 4 bytes of memory at io.c:41

So, starting with GRASS 7 revision r62444 (see startup screen or
g.version -g) you will be told which module actually failed,

This is not exactly true. You will be told where in the source code
memory allocation failed. This can be somewhere in a library, then you
don’t know which module actually failed. You need to check the return
code of the module, as of r62566 automatically done by
grass.run_command in trunk.

Markus M

so the
G_calloc error will be more useful. To get that, you will need to
update your GRASS GIS 7 installation.

However, a few thoughts before:

Current region rows: 21612, cols: 21612
i.e. 467078544 cells at 24 bytes/cell (AFAIK). That is:

467078544 * 24 / 1024 / 1024/ 1024
[1] 10.44002

Leaving a bit for the operating system etc, you may exceed 12GB RAM if
I got the numbers right.

Are you sure that you want to use 467 million cells? If not, check
“g.region -p”, perhaps the computational region resolution is too
high?

best
Markus

---

grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

[neteler]

Hi Andrea,

On Thu, Nov 6, 2014 at 5:46 AM, Andrea Timmermann <timmermann@gmx.at> wrote:

Hi !

I downloaded the 5-Nov Grass and also updated all the addons extensions I
use.

When I run:
"r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir="C:\\Users\\Andrea\\Basins"

I get:
"...
Building topology for vector map <o_map_outlet@Elevation>...
Registering primitives...
One primitive registered
One vertex registered
Building areas...
0 areas built
0 isles built
Attaching islands...
Attaching centroids...
Number of nodes: 0
Number of primitives: 1
Number of points: 1
Number of lines: 0
Number of boundaries: 0
Number of centroids: 0
Number of areas: 0
Number of isles: 0
------------------------------
An ERROR occurred running r.basin
Please try with another pairs of outlet coordinates"

I have just now submitted a bunch of fixes for r.basin, see

http://trac.osgeo.org/grass/changeset/62672

Please try again...

...

And about the known issues at the same page: "r.basin hasn't been designed
for working in lat/long coordinates. This means that if you are working in
lat/long coordinates, you need to reproject your map first in order to apply
the tool".

The DEMs I am using have a resolution of 0.33 degrees

Do you mean 33 arcseconds? Otherwise it would be something like 30km pixels

and when I reproject
them (projection: 3 (Latitude-Longitude); zone: 0; datum: nad83; ellipsoid:
grs80), the areas covered by the DEMs files vary depending on the longitude:
the surface covered by one file is larger near the equator than closer to
the poles. So I think this means that the cell resolution of my reprojected
map is larger near the poles than at the equator? If so, it would only make
sense to compare the morphometric parameters for catchments at a similar
latitude I think... Am I right? I am a bit confused with this ...

Perhaps you can find a DEM in a metric projection for your study area
which would save you some times?

Best
Markus

[Andrea_Timmermann]

Hi Markus,

Thanks a lot for your answer.

I downloaded the new r. basin and run

"r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir=“C:\Users\Andrea\Basins”

and I get this error:

ERROR: ‘r.stream.distance’ required. Please install ‘r.stream.distance’ first using ‘g.extension r.stream.distance’
Traceback (most recent call last):
File “C:\Users\Andrea\AppData\Roaming\GRASS7\addons/scri
pts/r.basin.py”, line 832, in
sys.exit(main())
File “C:\Users\Andrea\AppData\Roaming\GRASS7\addons/scri
pts/r.basin.py”, line 90, in main
check_progs()
File “C:\Users\Andrea\AppData\Roaming\GRASS7\addons/scri
pts/r.basin.py”, line 86, in check_progs
grass.fatal(_(“‘%s’ required. Please install ‘%s’ first
using ‘g.extension %s’”) % (prog, prog, prog))
File “C:\Program Files (x86)\GRASS GIS
7.1.svn\etc\python\grass\script\core.py”, line 593, in fatal
error(msg)
File “C:\Program Files (x86)\GRASS GIS
7.1.svn\etc\python\grass\script\core.py”, line 579, in error
message(msg, flag=‘e’)
File “C:\Program Files (x86)\GRASS GIS
7.1.svn\etc\python\grass\script\core.py”, line 517, in
message
run_command(“g.message”, flags=flag, message=msg)
File “C:\Program Files (x86)\GRASS GIS
7.1.svn\etc\python\grass\script\core.py”, line 361, in
run_command
returncode=returncode)
grass.exceptions.CalledModuleError: Module run None
g.message -e message=‘r.stream.distance’ required. Please
install ‘r.stream.distance’ first using ‘g.extension
r.stream.distance’ ended with error
Process ended with non-zero return code 1. See errors in the
(error) output.

Then I run:

g.extension r.stream.distance

and got:
Downloading precompiled GRASS Addons <r.stream.distance>…
Traceback (most recent call last):
File “C:\Program Files (x86)\GRASS GIS
7.1.svn/scripts/g.extension.py”, line 1083, in
sys.exit(main())
File “C:\Program Files (x86)\GRASS GIS
7.1.svn/scripts/g.extension.py”, line 1071, in main
install_extension(xmlurl)
File “C:\Program Files (x86)\GRASS GIS
7.1.svn/scripts/g.extension.py”, line 479, in
install_extension
ret += install_extension_win(module)
File “C:\Program Files (x86)\GRASS GIS
7.1.svn/scripts/g.extension.py”, line 709, in
install_extension_win
zfobj = zipfile.ZipFile(fo)
File “C:\Program Files (x86)\GRASS GIS
7.1.svn\Python27\lib\zipfile.py”, line 766, in init
self._RealGetContents()
File “C:\Program Files (x86)\GRASS GIS
7.1.svn\Python27\lib\zipfile.py”, line 807, in
_RealGetContents
raise BadZipfile, “File is not a zip file”
zipfile.BadZipfile: File is not a zip file

Thanks a lot for your answers.
Regards,
Andrea

Gesendet: Samstag, 08. November 2014 um 19:01 Uhr
Von: “Markus Neteler” neteler@osgeo.org
An: “Andrea Timmermann” timmermann@gmx.at
Cc: “GRASS user list” grass-user@lists.osgeo.org, “Margherita Di Leo” dileomargherita@gmail.com
Betreff: Re: Re: [GRASS-user] Problem with r.basin in grass7
Hi Andrea,

On Thu, Nov 6, 2014 at 5:46 AM, Andrea Timmermann timmermann@gmx.at wrote:

Hi !

I downloaded the 5-Nov Grass and also updated all the addons extensions I
use.

When I run:
"r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir=“C:\Users\Andrea\Basins”

I get:
"…
Building topology for vector map o_map_outlet@Elevation…
Registering primitives…
One primitive registered
One vertex registered
Building areas…
0 areas built
0 isles built
Attaching islands…
Attaching centroids…
Number of nodes: 0
Number of primitives: 1
Number of points: 1
Number of lines: 0
Number of boundaries: 0
Number of centroids: 0
Number of areas: 0
Number of isles: 0

An ERROR occurred running r.basin
Please try with another pairs of outlet coordinates"

I have just now submitted a bunch of fixes for r.basin, see

http://trac.osgeo.org/grass/changeset/62672

Please try again…

…

And about the known issues at the same page: “r.basin hasn’t been designed
for working in lat/long coordinates. This means that if you are working in
lat/long coordinates, you need to reproject your map first in order to apply
the tool”.

The DEMs I am using have a resolution of 0.33 degrees

Do you mean 33 arcseconds? Otherwise it would be something like 30km pixels

and when I reproject
them (projection: 3 (Latitude-Longitude); zone: 0; datum: nad83; ellipsoid:
grs80), the areas covered by the DEMs files vary depending on the longitude:
the surface covered by one file is larger near the equator than closer to
the poles. So I think this means that the cell resolution of my reprojected
map is larger near the poles than at the equator? If so, it would only make
sense to compare the morphometric parameters for catchments at a similar
latitude I think… Am I right? I am a bit confused with this …

Perhaps you can find a DEM in a metric projection for your study area
which would save you some times?

Best
Markus

[hellik]

Andrea Timmermann wrote

Hi Markus,&nbsp;

Thanks a lot for your answer.&nbsp;

I downloaded the new r. basin and run&nbsp;

[...]

Then I run:

&gt; g.extension&nbsp;r.stream.distance&nbsp;

and got:

Downloading precompiled GRASS Addons &lt;r.stream.distance&gt;...
Traceback (most recent call last):
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn/scripts/g.extension.py&quot;, line 1083, in &lt;module&gt;
&nbsp; &nbsp; sys.exit(main())
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn/scripts/g.extension.py&quot;, line 1071, in main
&nbsp; &nbsp; install_extension(xmlurl)
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn/scripts/g.extension.py&quot;, line 479, in
install_extension
&nbsp; &nbsp; ret += install_extension_win(module)
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn/scripts/g.extension.py&quot;, line 709, in
install_extension_win
&nbsp; &nbsp; zfobj = zipfile.ZipFile(fo)
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn&#92;Python27&#92;lib&#92;zipfile.py&quot;, line 766, in __init__
&nbsp; &nbsp; self._RealGetContents()
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn&#92;Python27&#92;lib&#92;zipfile.py&quot;, line 807, in
_RealGetContents
&nbsp; &nbsp; raise BadZipfile, &quot;File is not a zip file&quot;
zipfile.BadZipfile: File is not a zip file

Thanks a lot for your answers.&nbsp;

Regards,&nbsp;

Andrea

see http://lists.osgeo.org/pipermail/grass-dev/2014-November/071649.html

please give a response to this in the dev ML

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Problem-with-r-basin-in-grass7-tp5169155p5172382.html
Sent from the Grass - Users mailing list archive at Nabble.com.

[neteler]

Hi Andrea,

On Tue, Nov 11, 2014 at 3:30 AM, Andrea Timmermann <timmermann@gmx.at> wrote:

Hi Markus,

Thanks a lot for your answer.

I downloaded the new r. basin and run

"r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801
threshold=19005 dir="C:\\Users\\Andrea\\Basins"

and I get this error:

ERROR: 'r.stream.distance' required. Please install 'r.stream.distance'
first using 'g.extension r.stream.distance'

...

Update:
all the ugly error messages are gone as of r62708 and relevant fixes
earlier today. All this was a good test case to get the message
handling better.

Now you get:

GRASS 7.1.svn (nc_spm_08_grass7):~ > r.basin map=elevation
prefix=my_basin coord=637500.0,221750.0 dir=mydir threshold=1000
WARNING: 'r.stream.distance' required. Please install 'r.stream.distance'
         first using 'g.extension r.stream.distance'
ERROR: An ERROR occurred running r.basin

Concerning this issue:

Then I run:

g.extension r.stream.distance

and got:
Downloading precompiled GRASS Addons <r.stream.distance>...
Traceback (most recent call last):

...

    raise BadZipfile, "File is not a zip file"
zipfile.BadZipfile: File is not a zip file

We have discovered an issue on the Windows build server which creates
the executables of the addon.
In essence, the r.stream.*.exe files are not generates daily as they
should. Martin will look into this asap.

Thanks for your patience! It leads to better code. And I am sure that
all this will be sorted out in the next days.

Best
Markus

[hellik]

Andrea Timmermann wrote

and got:

Downloading precompiled GRASS Addons &lt;r.stream.distance&gt;...
Traceback (most recent call last):
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn/scripts/g.extension.py&quot;, line 1083, in &lt;module&gt;
&nbsp; &nbsp; sys.exit(main())
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn/scripts/g.extension.py&quot;, line 1071, in main
&nbsp; &nbsp; install_extension(xmlurl)
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn/scripts/g.extension.py&quot;, line 479, in
install_extension
&nbsp; &nbsp; ret += install_extension_win(module)
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn/scripts/g.extension.py&quot;, line 709, in
install_extension_win
&nbsp; &nbsp; zfobj = zipfile.ZipFile(fo)
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn&#92;Python27&#92;lib&#92;zipfile.py&quot;, line 766, in __init__
&nbsp; &nbsp; self._RealGetContents()
&nbsp; File &quot;C:&#92;Program Files (x86)&#92;GRASS GIS
7.1.svn&#92;Python27&#92;lib&#92;zipfile.py&quot;, line 807, in
_RealGetContents
&nbsp; &nbsp; raise BadZipfile, &quot;File is not a zip file&quot;
zipfile.BadZipfile: File is not a zip file

the r.stream.* addons are now back again for winGRASS, see e.g.
http://wingrass.fsv.cvut.cz/grass71/addons/grass-7.1.svn/

thanks to Martin.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Problem-with-r-basin-in-grass7-tp5169155p5172960.html
Sent from the Grass - Users mailing list archive at Nabble.com.

[Andrea_Timmermann]

Hi !!

Thanks for the update.
I reinstalled the latest grass (version 13.11) and could also install all the r.stream addons without problems.

There is still a problem with r.basin, however.
When I run:
“r.basin map=map@Elevation prefix=o coordinates=-71.10394196,43.9865230801 threshold=19005 dir=C:\Users\Andrea\Basins”

I get:
"…
…
Width Function | quantiles

===========================
9291 | 0.05
15726 | 0.15
27145 | 0.3
31933 | 0.4
35026 | 0.5
38212 | 0.6
41192 | 0.7
49125 | 0.85
56807 | 0.95
Done!
------------------------------
All in RAM calculation - method …
Reading raster map <o_map_stream_e>…
Reading raster map <o_map_drainage>…
Finding nodes…
Reading raster map <r_elevation_crop>…
Calculate downstream parameters…
Writing raster map <o_map_hillslope_distance>…
First pass
Writing output map
r.stats.zonal done
r.info done
r.mapcalc done
ERROR: Reading raster map <o_map_basin@> request for row -130 is outside region
------------------------------
An ERROR occurred running r.basin
Please check for error messages above or try with another pairs of outlet coordinates"

Best regards,
Andrea.

Gesendet: Freitag, 14. November 2014 um 10:02 Uhr
Von: “Helmut Kudrnovsky” hellik@web.de
An: grass-user@lists.osgeo.org
Betreff: Re: [GRASS-user] Problem with r.basin in grass7
Andrea Timmermann wrote

and got:

Downloading precompiled GRASS Addons <r.stream.distance>…
Traceback (most recent call last):
  File "C:\Program Files (x86)\GRASS GIS
7.1.svn/scripts/g.extension.py", line 1083, in <module>
    sys.exit(main())
  File "C:\Program Files (x86)\GRASS GIS
7.1.svn/scripts/g.extension.py", line 1071, in main
    install_extension(xmlurl)
  File "C:\Program Files (x86)\GRASS GIS
7.1.svn/scripts/g.extension.py", line 479, in
install_extension
    ret += install_extension_win(module)
  File "C:\Program Files (x86)\GRASS GIS
7.1.svn/scripts/g.extension.py", line 709, in
install_extension_win
    zfobj = zipfile.ZipFile(fo)
  File "C:\Program Files (x86)\GRASS GIS
7.1.svn\Python27\lib\zipfile.py", line 766, in init
    self._RealGetContents()
  File "C:\Program Files (x86)\GRASS GIS
7.1.svn\Python27\lib\zipfile.py", line 807, in
_RealGetContents
    raise BadZipfile, "File is not a zip file"
zipfile.BadZipfile: File is not a zip file

the r.stream.* addons are now back again for winGRASS, see e.g.
http://wingrass.fsv.cvut.cz/grass71/addons/grass-7.1.svn/

thanks to Martin.

---

best regards
Helmut

View this message in context: http://osgeo-org.1560.x6.nabble.com/Problem-with-r-basin-in-grass7-tp5169155p5172960.html
Sent from the Grass - Users mailing list archive at Nabble.com.

---

grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

[hellik]

Andrea Timmermann wrote

Hi !!

&nbsp;

Thanks for the update.&nbsp;

I reinstalled the latest grass &nbsp;(version 13.11) and could also
install all the r.stream addons without problems.

&nbsp;

There is still a problem with r.basin, however.

When I run:

&quot;r.basin map=map@Elevation prefix=o
coordinates=-71.10394196,43.9865230801 threshold=19005
dir=C:&#92;&#92;Users&#92;&#92;Andrea&#92;&#92;Basins&quot;

&nbsp;

I get:

&quot;...

...

Width Function &#124; quantiles

===========================
9291 &#124; 0.05
15726 &#124; 0.15
27145 &#124; 0.3
31933 &#124; 0.4
35026 &#124; 0.5
38212 &#124; 0.6
41192 &#124; 0.7
49125 &#124; 0.85
56807 &#124; 0.95
Done!
------------------------------
All in RAM calculation - method &lt;DOWNSTREAM&gt;...
Reading raster map &lt;o_map_stream_e&gt;...
Reading raster map &lt;o_map_drainage&gt;...
Finding nodes...
Reading raster map &lt;r_elevation_crop&gt;...
Calculate downstream parameters...
Writing raster map &lt;o_map_hillslope_distance&gt;...
First pass
Writing output map
r.stats.zonal done
r.info done
r.mapcalc done
ERROR: Reading raster map &lt;o_map_basin@&gt; request for row -130 is
outside region

------------------------------

An ERROR occurred running r.basin
Please check for error messages above or try with another pairs of outlet
coordinates&quot;

tested r.basin here on my side:

r.basin --verbose map=dem_linked@PERMANENT prefix=a
coordinates=-51121.42352,193901.704819 dir=C:\tmp\rstreamtest
threshold=12000
[...]
(Sun Nov 16 13:12:48 2014) Befehl ausgeführt (40 Min 25 Sek)

r.basin finishes here.

please try to reset and align your region to the DEM before a r.basin-run.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Problem-with-r-basin-in-grass7-tp5169155p5173189.html
Sent from the Grass - Users mailing list archive at Nabble.com.