<br><br><div><span class="gmail_quote">2007/3/22, Hamish <<a href="mailto:hamish_nospam@yahoo.com">hamish_nospam@yahoo.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Moritz Lennert wrote:<br>><br>> You can try to rerun the entire cleaning operation that v.in.ogr uses,<br>> i.e.:<br>><br>> v.clean in=inmap out=outmap_clean_vinogr<br>> tool=snap,bpol,rmdupl,break,rmdupl,rmsa,chdangle,rmdangle,chbridge,rm
<br>> bridge thresh=0.000001<br>><br>> and maybe play around with the thresh parameter, depending on your<br>> projection and data resolution.<br><br>Hi,<br><br>Radim often made it known that 'v.in.ogr -c' +
v.clean is not the same<br>as v.in.ogr's built-in cleaning.</blockquote><div><br>Can you point me to this resource? (if other than both v.in.ogr and v.clean man pages)<br>I would really appreciate to do further reading on this as often shape files comes from arcgis (quite always in my case) and some "massaging" must be done in order to get them properly usable with grass.
<br><br>Should all these affect the patching of v.clean(ed) shapes and subsequent missing areas in the result?<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hamish</blockquote><div><br>regards<br>raffaele <br></div><br></div><br>