Excellent, thank you. Am I correct then in assuming that I can treat all of my multipolygon data as type=boundary for the purposes of using v.generalize? The end goal is to buffer the geometry and then export it back out as a shapefile.<br>
<br>Thanks again for your assistance.<br><br>Roger<br>--<br><br><div class="gmail_quote">On Wed, Apr 15, 2009 at 10:13 AM, Martin Landa <span dir="ltr"><<a href="mailto:landa.martin@gmail.com">landa.martin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2009/4/15 Roger André <<a href="mailto:randre@gmail.com">randre@gmail.com</a>>:<br>
<div class="im">> Got Version 6.4 working last night and started to experiment with<br>
> v.generalize. I'm using it on a group of polygons that represent the<br>
> Hawaiian islands and noticed some interesting behavior. In other systems, I<br>
> would expect these features to be treated at "multipolygons", however in<br>
> GRASS I see that I have the option of specifying point, line, boundary, or<br>
> area. I'm not exactly sure what the difference between boundary and area<br>
> is, but it does seem to make a difference in the v.generalize output which<br>
> of them I choose. Can someone clarify for me how these geometry types<br>
> affect the operation v.generalize?<br>
<br>
</div><a href="http://grass.osgeo.org/grass64/manuals/html64_user/vectorintro.html" target="_blank">http://grass.osgeo.org/grass64/manuals/html64_user/vectorintro.html</a><br>
<br>
-> Vector model and topology<br>
<br>
M.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">Martin Landa <landa.martin <a href="http://gmail.com" target="_blank">gmail.com</a>> * <a href="http://gama.fsv.cvut.cz/%7Elanda" target="_blank">http://gama.fsv.cvut.cz/~landa</a><br>
</div></div></blockquote></div><br>