Topology AddIn Guinea Pig wanted
Hey everybody,
On a monthly basis I create a bunch of topologys to make sure that my polygon layers don't overlap or have gaps (ESN). I also run a topology on my street layer to find street segments that aren't snapped. This process consists mostly of models.
Since I always try to help my Public safety brethren, I figured I compile my process in a Python AddIn, that "should be easy to use". I started a day ago and have the skeleton of the AddIn finished and now I am looking for a Guinea Pig (I am looking at you Chris Donohue, GISP & Joe Borgione ) to use it!
Latest Update:
- Created an official document: Topology Check Python AddIn (6/30/17)
- Added Error message when the wrong feature is chosen for certain Checks (i.e. polygon feature is chosen for dangle check)
- Now works with ArcGIS Desktop Standard
- Latest test version that includes a polygon break check. This check make sure that your line features are broken when they intersect with a polygon feature. Just select the line feature and polygon feature in the TOC and run the check.
Dropbox - TopoAddIn.esriaddin 10.3.1 + version
Here is what you need:
ArcGIS Desktop Standard 10.3.1 or later versions
Here is how it works:
1. You would download the add in HERE. (10.1 version HERE )
2. Double click it and install it.
3. Open an MXD and add a polygon layer and a street layer.
4.The toolbar should be there but if it is not click on Customize -> Toolbars -> TopoCheck
5. Follow the steps in the screenshot!
As I said it is still a work in progress, especially the street dangle check.
Let me know what you think!
Tim
Tim Witt I have not downloaded or tested your addin yet (although it looks really helpful), but before I start down the "validate topology in <multiple> extent" scripting road, I thought I'd ask if you already have one. I'm testing the use of a two-way replica to a SQL Express personal SDE (also tried checkout to fgdb), but it (both) cause the entire area to be dirty, which takes 2+ hours to validate...then ~3k errors need to be marked as exceptions. Doin the entire state/dirty-area at once, with the personal SDE, crashed after 2 hr 10 min yesterday, but breaking it up worked (my guess it hit a limit somewhere).
I should be able to figure out the code to change extent, validate, repeat...but thought I'd ask if you have that already in your workflow.
Modify the wheel vs reinventing. 
edit: BTW - I have downloaded now and installed now.
Even if you can't Tim, it's not a show stopper for me. It all goes back to the fact that the tool does create various feature classes that are very useful, even with a standard license. Basically the tool considers dangles where there is 15' or less gap between street segments. It creates a buffer feature class which is available to the standard license. (See below) The attribute table of those buffers include all the data from the streets it intersects. In my case I found 321 buffers, which translates to 321 legitimate (= > 15') dangles. (Not too bad with a 57,000 record feature class of roads...)
The way I'm going about fixing them is city by city: First select a city polygon and then do spatial selection to find those buffers that intersect that selected city. And just start zooming to the selected features. I added a field called FIXED inthe buffer attribute, and when I fix the dangle error, I calc FIXED = 1 and move on....
