[GRASS-user] r.grow: Manual Page Needs Additional Information

[Daniel Lee]

Hi there,

I'm not sure if this is what you're looking for, but I've used it before
todo a pixel-based buffer on buildings extracted automatically from a
surface model. If you're not wanting specifically to work with pixels,
though, I honestly don't see the difference either ;)

Best,
Daniel

--

B.Sc. Daniel Lee
Geschäftsführung für Forschung und Entwicklung
ISIS - International Solar Information Solutions GbR
Vertreten durch: Daniel Lee, Nepomuk Reinhard und Nils Räder

Softwarecenter 3
35037 Marburg
Festnetz: +49 6421 379 6256
Mobil: +49 176 6127 7269
E-Mail: Lee at isi-solutions.org
Web: http://www.isi-solutions.org


Am 26. April 2012 10:05 schrieb Markus Neteler <neteler at osgeo.org>:

> On Tue, Apr 24, 2012 at 6:40 PM, Rich Shepard <rshepard at appl-ecosys.com>
> wrote:
> >  I've just been made aware of the r.grow module as part of the solution
> to
> > the map mis-match issue with r.stream.extract. The r.grow manual page is
> > quite clear on how to use it, but is missing important information: when
> and
> > why one should apply this module to a raster map.
>
> If anyone has the answer, please send me a text snipped for inclusion
> into the manual.
>
> thanks
> Markus
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20120427/ae8dc2e6/attachment.html