Ben wrote: > r.carve actually "carves" rivers into a DEM, subtracting > their depths from the DEM. > > r.burn.frict does essentially the same job as v.to.rast > would, except it performs some anti-aliasing on line edges, > so there is no case like this: > > 0100 > 0010 > 0001 > > where a cost surface algorithm that scans for 8 directions > could "slip" diagonally through the cells that represent a > boundary line. > Instead, the line would be rasterized like this: > > 0100 > 0110 > 0011 > > This is (only?) useful for rasterizing lines onto friction > surfaces. It's really just a primitive little script that I > wrote because I needed it for territorial modeling with > r.xtent which involves cost surfaces.
if a module does its job well, then great. congrats. but FYI a couple other ways to accomplish the same thing if it helps. (not sure it will, once done r.mapcalc is pretty hard to beat) - r.grow[.distance] - v.type boundary,line or v.cat add to boundaries -> v.to.rast (see man page) - not G_bresenham_line() but ...? Hamish _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user