Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-29 Thread Rich Shepard
On Fri, 29 Jun 2018, Helmut Kudrnovsky wrote: citing the d.vect manual: color=name Feature color Either a standard color name, R:G:B triplet, or "none" Default: black fill_color=name Area fill color Either a standard color name, R:G:B triplet, or "none" Default: 200:200:200 I've not specif

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-29 Thread Helmut Kudrnovsky
>Ideally, the overlaps and duplicates would/could be displayed in a >contrasting color for easy identification. citing the d.vect manual: color=name Feature color Either a standard color name, R:G:B triplet, or "none" Default: black fill_color=name Area fill color Either a standard color name,

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-29 Thread Rich Shepard
On Fri, 29 Jun 2018, Helmut Kudrnovsky wrote: d.vect layer=2 ? Helmut, I did this then ran v.clean. The number of duplicate centroids dropped from 107 to 4, but refreshing the display showed the same areas as when there were more duplicates. When time permits I might try looking at eac

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-29 Thread Helmut Kudrnovsky
Rich Shepard wrote > On Fri, 29 Jun 2018, Markus Metz wrote: > >> After import with v.in.ogr, overlapping parts have a category value set >> in >> layer 2. If you want to get rid off all overlapping parts, check with >> v.category op=report if any centroids still have a category value in >> layer

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-29 Thread Rich Shepard
On Fri, 29 Jun 2018, Markus Metz wrote: After import with v.in.ogr, overlapping parts have a category value set in layer 2. If you want to get rid off all overlapping parts, check with v.category op=report if any centroids still have a category value in layer 2. Sometimes these areas can be clea

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-29 Thread Rich Shepard
On Fri, 29 Jun 2018, Markus Metz wrote: After import with v.in.ogr, overlapping parts have a category value set in layer 2. If you want to get rid off all overlapping parts, check with v.category op=report if any centroids still have a category value in layer 2. Sometimes these areas can be clea

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-29 Thread Markus Metz
On Fri, Jun 29, 2018 at 5:49 PM, Rich Shepard wrote: > > On Wed, 27 Jun 2018, Markus Neteler wrote: > >> You may want to take a look here: >> https://grasswiki.osgeo.org/wiki/Vector_topology_cleaning > > > Markus, > > After repeating v.in.ogr with larger snap thresholds until it told me it > did

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-29 Thread Rich Shepard
On Wed, 27 Jun 2018, Markus Neteler wrote: You may want to take a look here: https://grasswiki.osgeo.org/wiki/Vector_topology_cleaning Markus, After repeating v.in.ogr with larger snap thresholds until it told me it did as well as it could and I should now use v.clean, is there a tool that

Re: [GRASS-user] v.clean: recommend tools and sequence [RESOLVED]

2018-06-28 Thread Rich Shepard
On Thu, 28 Jun 2018, Rich Shepard wrote: I find this sentence ambiguous: "For import, try to find a snapping threshold for v.in.ogr that produces an error-free output (during import the module suggests a threshold)." I've not seen a suggested threshold when I run v.in.ogr. When I press the [Ent

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-28 Thread Rich Shepard
On Wed, 27 Jun 2018, Markus Neteler wrote: You may want to take a look here: https://grasswiki.osgeo.org/wiki/Vector_topology_cleaning Markus, I find this sentence ambiguous: "For import, try to find a snapping threshold for v.in.ogr that produces an error-free output (during import the mod

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-27 Thread Rich Shepard
On Wed, 27 Jun 2018, Markus Metz wrote: In your case, the focus is also on v.in.ogr rather than v.proj. Try to get a reasonably clean vector with v.in.ogr (+ v.clean) before reprojecting the vector. Markus, Yes, I'll re-import it and play with the threshold values. Thanks, Rich _

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-27 Thread Markus Metz
On Wed, Jun 27, 2018 at 8:59 PM, Rich Shepard wrote: > > On Wed, 27 Jun 2018, Markus Neteler wrote: > >> You may want to take a look here: >> https://grasswiki.osgeo.org/wiki/Vector_topology_cleaning > > >> Normally the module gives you a suggestion. > > > Markus, > > Thanks for the URL. The foc

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-27 Thread Rich Shepard
On Wed, 27 Jun 2018, Markus Neteler wrote: You may want to take a look here: https://grasswiki.osgeo.org/wiki/Vector_topology_cleaning Normally the module gives you a suggestion. Markus, Thanks for the URL. The focus is on v.in.ogr rather than v.proj so I'll try to translate from the for

Re: [GRASS-user] v.clean: recommend tools and sequence

2018-06-27 Thread Markus Neteler
On Wed, Jun 27, 2018 at 4:43 PM, Rich Shepard wrote: > At the end of v.proj processing of the public_forests map three warnings > were presented: > > WARNING: Number of incorrect boundaries: 39934 > WARNING: Number of centroids outside area: 528 > WARNING: Number of duplicate centroids: 107 > >

[GRASS-user] v.clean: recommend tools and sequence

2018-06-27 Thread Rich Shepard
At the end of v.proj processing of the public_forests map three warnings were presented: WARNING: Number of incorrect boundaries: 39934 WARNING: Number of centroids outside area: 528 WARNING: Number of duplicate centroids: 107 The v.clean module has 13 tools and an action threshold for use.