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,

[GRASS-user] 7.5svn: create location from existing map

2018-06-29 Thread Rich Shepard
The directory biota/ contains the subdirectory bulltrout/, which contains two files and two subdirectories: VAR WIND dbf/ vector/. The map is named bulltrout2008. As this mapset became disconnected from the location in which it was originally imported I want to learn how to turn it into a

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.out.postgis

2018-06-29 Thread Paul Shapley
Hi Moritz, My apologies... it appears that the result of 'r.to.vect was indeed sending the attributes to postgres but i was expecting them to appear in sqlite had i 'refreshed' the posgres schema i would have seen them. Best Wishes and thank you, Paul Shapley On 29 June 2018 at 14:50, Moritz Le

Re: [GRASS-user] v.out.postgis

2018-06-29 Thread Moritz Lennert
On 29/06/18 12:38, Paul Shapley wrote: Hi Moritz, Here is the result:- v.db.select APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector DBMI-PostgreSQL driver error: Unable to select: SELECT * FROM grass_gis.APGB_aerial_2_i_segment_drained_peat _with_exposed_haggs_vector ERROR:  relat

Re: [GRASS-user] v.out.postgis

2018-06-29 Thread Paul Shapley
Hi Moritz, Here is the result:- v.db.select APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector DBMI-PostgreSQL driver error: Unable to select: SELECT * FROM grass_gis.APGB_aerial_2_i_segment_drained_peat _with_exposed_haggs_vector ERROR: relation "grass_gis.apgb_aerial_2_i_segment_d

Re: [GRASS-user] v.out.postgis

2018-06-29 Thread Moritz Lennert
On 29/06/18 10:39, Paul Shapley wrote: Hi Markus, OK here is the result of v.db.connect -p v.db.connect -p APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector Vector map is connected by: layer <1/grass_gis.APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector> table

Re: [GRASS-user] v.out.postgis

2018-06-29 Thread Paul Shapley
Hi Markus, OK here is the result of v.db.connect -p v.db.connect -p APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector Vector map is connected by: layer <1/grass_gis.APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs_vector> table in database through driver with key I recal