Hamish et al,<div><br></div><div>I'm well aware of how to set an alias, but I appreciate the suggestion. Thank you.</div><div><br></div><div>I think there is a misunderstanding here. If you would all please go back to the original question (which was posed by someone other than I), you will see that it asks for clarification regarding how the GRASS topology model deals with overlapping areas. I too had wondered about this, and we discussed the behavior we had both observed to see if we could better understand it. I gave my opinion that the default of cleaning the topology of the input data by v.in.ogr should not have been chosen as the default and gave some reasons why I felt that way - related to the original topic of conversation. Nowhere in any of this did I ask any of you to do anything.</div>
<div><br></div><div>I appreciate all the helpful suggestions and insightful feedback, and I think we can stop discussing this now.</div><div><br></div><div>Roger</div><div>--</div><div><br></div><div><br><br><div class="gmail_quote">
On Fri, Dec 2, 2011 at 5:58 PM, Hamish <span dir="ltr"><<a href="mailto:hamish_b@yahoo.com">hamish_b@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
if the default behviour of v.in.ogr is not to your<br>
taste, may I suggest to do:<br>
<br>
echo "alias v.in.ogr='v.in.ogr -c'" >> ~/.grass.bashrc<br>
<br>
but do so at your own risk.<br>
<br>
<br>
fwiw, nothing black-box in the import process, just<br>
search for "no_clean" here:<br>
<a href="https://trac.osgeo.org/grass/browser/grass/trunk/vector/v.in.ogr/main.c" target="_blank">https://trac.osgeo.org/grass/browser/grass/trunk/vector/v.in.ogr/main.c</a><br>
<br>
The code is relatively well commented and this is<br>
open source: you are free (and encouraged) to make<br>
it act any way you like.<br>
<br>
<br>
shrug,<br>
<span class="HOEnZb"><font color="#888888">Hamish<br>
</font></span></blockquote></div><br></div>