[GRASSLIST:9867] Re: r.cost and distance to nearest feature

[Markus Neteler]

Hi,

what about r.distance and maybe m.cogo? 

M

On Tue, Jan 17, 2006 at 10:10:52AM +0200, M?ris Narti?s wrote:
> Hi,
> 
> 1) submit this as wish list item at
> http://grass.itc.it/bugtracking/bugreport.html (I know, that interface
> sucks and bugzilla is better, but currently we have no bugzilla);
> 2) nearest feature in raster or vector map?
> If it is raster map, may bee You can write such module Yourself. I was
> surprised, that knowledge from "teachyourself C in 24h" is enough to
> code new simple raster module for GRASS. And more - first You can
> implement it in mapcalc - it not as hard as it sounds :)
> 
> Let the source be with you!
> Maris.
> 
> 2006/1/16, Jesse Whittington <jesse.whittington at lycos.com>:
> > When I run r.cost, I frequently receive an error saying that there is not enough memory.  After searching the mail archives I tried increasing my resolution four-fold, partitioning my grids with large overlapping boundaries, and adding the arguement percent_memory=100 with mixed success.  Consequently, it's easier for me to export my data and calculate distance to nearest feature in ArcInfo workstation.
> >
> > I realize that there are a limited number of developers, but I'm sending this message as a request for what might be a simpler algorythm than r.cost to produce:
> >     - distance to nearest feature
> >     - attribute of nearest feature
> >     - direction to nearest feature
> >
> > Otherwise, I think GRASS is a GREAT program,
> > Jesse
> >