Hi, I get a similar issue some time ago (but with a vector input) and wrote a little script to work only with raster (no need to transform back to vector)
it's using r.distance ( http://grass.osgeo.org/grass64/manuals/html64_user/r.distance.html), wich "Locates the closest points between objects in two raster maps" and output an ascii line with the intersection point ... you just need to input your 2 raster with basin boundaries and streams, and it will do the job for all your objects at once ;) Cheers, Sylvain 2012/6/6 Rich Shepard <rshep...@appl-ecosys.com> > Running r.basin using r.to.vect basin boundaries and r.to.vect > r.stream.extract weighted streams (but same issue using unweighted > streams). > So far, of 7 sub-basins on which I've run the module only 4 complete > successfully. The other three go through the entire process then fail with > the error message that the outlet needs to be on a stream channel created > by > r.stream.extract. > > I use the same protocol on each sub-basin: zoom in very close to where the > sub-basin boundary and stream channel cross, then note the x, y coordinates > from the status line on the display window frame. > > What might account for this same process, using the same r.stream.extract > map, to work on some sub-basins and fail on others? > > Rich >
_______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
