[GRASS-user] Fixing poor quality .gdb files

[Rich Shepard]

I have a data source (a US state) whose GIS data files in .gdb format lack
clean topology. v.in.ogr reports (for one example) that 29671 polygons
overlap and suggests re-importing starting with snap=1e-09. I end up
re-running v.in.ogr through snap=0.1 without completely fixing all overlaps
and other errors. One question is: how many times should I re-run v.in.ogr
with different smap tolerances if the data are not fixed?

Next I run v.clean using snap as the tool and 1 as the threshold. For many
of these files this does not fix all the errors.

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?

TIA,

Rich