[GRASS-user] Fixing poor quality .gdb files [RESOLVED]

[Rich Shepard]

On Tue, 18 Aug 2020, Rich Shepard wrote:

> While I can use v.build to see the errors I would like to better understand
> the work flow for removing all errors that occur when importing with
> v.in.ogr. How can I most quickly generate fully topologically clean output?

I used the wrong v.clean options. What works for both .shp and .gdb files
that have issues after being imported is:
v.clean input=<mapname> output=<mapname>_clean tool=bpol,rmdupl type=boundary

Rich