Ah, ok. The causes, please. <div><br></div><div>It's a really powerful tool, and I would like to write some additional documentation on how to use it for generalizing and smoothing large polygon sets, but first I need to make sure that I can anticipate it's behavior a little better. The area attribute swapping was something that I had noticed as well, but I figured that was just something to be expected.</div>
<div><br></div><div>Also, would it be helpful to have additional testers for some of these? I'm not using the raster tools at the moment, but am using the vector tools quite a bit (console only though).</div><div><br>
</div><div>Roger</div><div>--</div><div><div><br><div class="gmail_quote">On Wed, Oct 26, 2011 at 11:51 AM, Markus Metz <span dir="ltr"><<a href="mailto:markus.metz.giswork@googlemail.com">markus.metz.giswork@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Roger André wrote:<br>
> Hi Markus,<br>
> That's good to know. Can you tell me the bug number? I'd like to review<br>
> the details of it.<br>
<br>
</div>There is no bug number, at least I could not find a corresponding bug<br>
number. There were a few complaints about v.generalize in the mailing<br>
lists. In short, you are not the first one to discover this bug.<br>
Additionally, v.generalize was randomly swapping area attributes. This<br>
is also fixed.<br>
<br>
Since you are asking about a bug number, are you interested in the<br>
effects or the causes?<br>
<br>
Markus M<br>
<div><div></div><div class="h5"><br>
<br>
> Thanks,<br>
> Roger<br>
> --<br>
><br>
> On Wed, Oct 26, 2011 at 12:23 AM, Markus Metz<br>
> <<a href="mailto:markus.metz.giswork@googlemail.com">markus.metz.giswork@googlemail.com</a>> wrote:<br>
>><br>
>> On Tue, Oct 25, 2011 at 11:07 PM, Roger André <<a href="mailto:randre@gmail.com">randre@gmail.com</a>> wrote:<br>
>> > Hello GRASS Community,<br>
>> > I'm having a problem that I'm hoping you can help me find the source of.<br>
>> > I think that either A) I am trying to use the v.generalize tool<br>
>> > incorrectly,<br>
>> > B) that my data has some sort of topological problem which I'm unaware<br>
>> > of,<br>
>> > or C) that there is a bug in v.generalize. The simplest way to describe<br>
>> > what's happening is that I am consistently unable to generalize a large<br>
>> > group of contiguous polygons (African states most recently) without<br>
>> > losing a<br>
>> > large number of polygons from my data. I have tried a variety of<br>
>> > different<br>
>> > things, all without success, and now I'd like to ask if someone would be<br>
>> > willing to verify that what I'm seeing isn't a problem of my own<br>
>> > creation.<br>
>> > I've posted my data files at <a href="http://www.macrogis.net/africa" target="_blank">www.macrogis.net/africa</a>, along with a<br>
>> > before-and-after image of the specific problem I've encountered. I'm<br>
>> > using<br>
>> > GRASS v 6.4.1 which I downloaded from the main website 2 months ago.<br>
>><br>
>> This bug has been fixed in GRASS 6.4.2<br>
>><br>
>> Markus M<br>
><br>
><br>
</div></div></blockquote></div><br></div></div>