Removing unwanted verticies

5349
8
01-29-2013 10:52 AM
TravisThomas
Emerging Contributor
What tool or method can be used to remove vertices staked ontop of one another? Dealing with one feature class here and one polygon, (no stacked polys). At the present time I am deleting each one as they appear after running a topology. Any hints?
Tags (2)
0 Kudos
8 Replies
T__WayneWhitley
Honored Contributor
Repair Geometry (Data Management)
Desktop » Geoprocessing » Tool reference » Data Management toolbox
http://resources.arcgis.com/en/help/main/10.1/index.html#//00170000003v000000
0 Kudos
WadeLobb
Regular Contributor
If you are using Arc 10 or later the edit vertices toolbar will help

http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//001t00000097000000.htm

To delete a vertex, click the Delete Vertex tool  and click the vertex to delete. To delete multiple vertices, drag a box around them.
0 Kudos
JonathanQuinn
Esri Notable Contributor
I'd suggest you look into the Simply Polygon tool as well.  There are options for specifying how far away vertices need to be from each other to remove them.  Make a backup of your data if you play with this tool, as it will change the geometry of your original data.
0 Kudos
TravisThomas
Emerging Contributor
Presently using the manual "Edit vertices" routine and it is toooooo time consuming for the amount of data.  I tried the "Repair Geometry" without success - the duplicate vertices are still there.  Perhaps my feature set is not open for this type of data management.  Any more hints?
0 Kudos
T__WayneWhitley
Honored Contributor
hmmmm, are you executing on a shapefile?....personal or file gdb fc?

Not sure why the repair geom didn't work.  I'm not sure if true curves are going to be an issue, but you could try, if not already in shp format, exporting out to shapefile, then import back into a file gdb.  Only thing is you are likely to lose any true type curves because shapefiles do not support them.

EDIT:  In a pinch, if I had an insane number of duplicate geometries, I'd do something like read the geom coords into an array by script, then eliminate adjacent dup coords (not closing a ring), then write that back out to a fc.  Again, you'd lose true curve information, anything based on parametric curves will be lost.  However there are ways to sometimes target those shape parts and convert them back to curves once in the gdb.  lol, let's see if the other means works 1st.
0 Kudos
JohnSobetzer
Honored Contributor
Other options include using the generalize tool for selected features if you are in an edit session and find issues, or using the Integrate tool on a dataset.  Use a copy of your data, or have a backup for Integrate in case you don't like the result, or use the Feature class to feature class tool to create a new one.  You will likely want to fiddle with the generalize value, or with the Integrate/Featuer Class to Feature class tolerances to get what you want.
0 Kudos
TravisThomas
Emerging Contributor
Thanks T.W.W.
After talking to a co-worker it maybe that the verticies are not coincident.  The overall dataset is huge with several editors and therefore several validations are run.  We have checks in place for editing versions but the way we actually work within the versiions maybe the issue.  Does the Repair Geometry tool have a tolerance (cluster)?

Thanks John S.
I will try the methods you have provided on the next dataset.  Unfortunately, I had to manually delete the extra verticies and get the data in to meet a deadline.
0 Kudos
T__WayneWhitley
Honored Contributor
hmm, that's very interesting and no I don't think so -- sounds like what you may be alluding to is setting up a topology, there is a cluster tolerance you can set up there.  Not sure about any licensing restrictions if any - if you have ArcInfo (or Advanced, as it is now called), then no worries.

Here's the thing though - setting up a topology requires import into a gdb feature dataset and is potentially a bit time-consuming to initially process and set up the rules.  Plus, I don't fully know your situation and while using a topology is most effective for some workflows, it can be overkill and bog down other workflows....have to use your judgement.

Could be all you want to do is execute Integrate (but make sure you make a backup copy of the dataset 1st).  Results will vary and you may be unpleasantly surprised...no need to go on about that, you can imagine I'm sure.  I think of Integrate as sometimes an expedient means to 'slam stuff' together without the validation a topology would enforce.  It is shooting from the hip, so exercise care (copy the dataset and experiment) and define a close (small) measure of tolerance...

One more thing, since you've got me babbling -- I once had points (fire hydrants, I think) collected so that, as you describe, were sometimes very nearly coincident, but the 'slam together' approach was no good -- I need to identify the dups.  So what I did was run a small Buffer with dissolved overlaps to 'enclose' the duplicate candidates.  What that did was to enable me to very quickly select the dissolved buffer areas that were not 'round' thus larger in area.  Area is a criteria I can select, export, and provide a report to someone needing to 'see' both (or more in some instances) candidates to figure out what is going on and how to then assimilate the data into the single shapes they should be.  Yes, so that's Buffer in proximity analysis.

Hope that helps.

-Wayne
0 Kudos