Hi, re. r34409: Replace r.buffer with a script using r.grow.distance
I am wondering, does r.grow.distance do the right thing in Lat/Lon? If not, then the C version of r.buffer still has an important advantage and should stay. e.g.: (latest SVN for r.in.poly; see attached) g.region n=60S s=85S w=30 e=60 res=0:05 r.in.poly in=- out=dot_map << EOF P 45E 72:30S = 1 dot EOF g.region n=43:20S s=90S w=10 e=80E r.buffer in=dot_map out=dot_map.500nm dist=500 units=nautmiles d.mon x0 d.rast dot_map.500nm d.grid 30 ?, Hamish
<<attachment: rbuffer_C.png>>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
