[GRASS-user] overlapping areas seem valid to v.build: why?

Roger André randre at gmail.com
Sat Dec 3 01:26:51 EST 2011

Hamish et al,

I'm well aware of how to set an alias, but I appreciate the suggestion.
Thank you.

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

I appreciate all the helpful suggestions and insightful feedback, and I
think we can stop discussing this now.


On Fri, Dec 2, 2011 at 5:58 PM, Hamish <hamish_b at yahoo.com> wrote:

> Hi,
> if the default behviour of v.in.ogr is not to your
> taste, may I suggest to do:
> echo "alias v.in.ogr='v.in.ogr -c'" >> ~/.grass.bashrc
> but do so at your own risk.
> fwiw, nothing black-box in the import process, just
> search for "no_clean" here:
>  https://trac.osgeo.org/grass/browser/grass/trunk/vector/v.in.ogr/main.c
> The code is relatively well commented and this is
> open source: you are free (and encouraged) to make
> it act any way you like.
> shrug,
> Hamish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20111202/b404024a/attachment.html

More information about the grass-user mailing list