By the way, it seems that the official stance is that it is preferred to allow the automatic cleaning of non-topological data sets when they are imported. However, I do want to point out that I have seen many, many instances where this auto-cleaning actually causes problems, rather than fixes them. As a result, I explicitly exclude cleaning on every import I do. If cleaning is required, I manually clean the data with v.clean. In many cases only a subset of the full set of cleaning operations performed automatically by v.in.ogr are needed to fix the data. Personally, I do not think this "auto cleaning" should ever have been made the default operation of the import tool.<div>
--</div><div><br>
<br><div class="gmail_quote">On Wed, Nov 30, 2011 at 9:37 AM, Markus Metz <span dir="ltr"><<a href="mailto:markus.metz.giswork@googlemail.com" target="_blank">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">
Moritz Lennert wrote:<br>
<div>> On 30/11/11 14:38, Markus Metz wrote:<br>
>><br>
>> It seems to me that the confusion arises because you made use of<br>
>> features that allow you to skip topological cleaning which is not the<br>
>> default and not recommended.<br>
><br>
><br>
</div>> Maybe this calls for a v.check.topology module ? Or an option in v.build or<br>
> v.clean which does that (i.e. just check, not clean) ?<br>
<br>
Good idea. I would opt for a new option/flag for v.build, which can<br>
already provide rather detailed diagnostics, e.g. dumping topology.<br>
Something like v.build -e for extended topology checks?<br>
<br>
Markus M<br>
_______________________________________________<br>
grass-user mailing list<br>
<a href="mailto:grass-user@lists.osgeo.org" target="_blank">grass-user@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br>
</blockquote></div><br>
</div>