Latest Contributions by JamieKass

Yes, I developed something similar that creates a unique string representation of area, centroid X, and centroid Y. It is imperfect, as different datasets may require tweaking of the decimal tolerances, but it works alright the way it is. def repGeomString(shp):     return str(round(shp.area)) + '|' + str(round(shp.centroid.X, 2)) + '|' + str(round(shp.centroid.Y, 2)) I call this in a search cursor loop and add it to a dictionary with the OID as key, much in the same way you did it. I have experienced finding polygons with mysterious null centroids, but if you account for them somehow that's the only trip-up. This wouldn't be necessary if FindIdentical worked on large datasets. I wish the internal tolerances of this tool were exposed so we could improve these imperfect geometry estimators. I've included a sample function I've wrote that returns a dictionary relating each OID to its overlapping OIDs, based on if repGeomString is equal. Buffering often leads to small changes in shapes that should be identical, and therefore this function gets thrown off sometimes, but usually works quite well. def fasterFindID(fc):     """Records geometrical attributes of all features, then returns a dictionary:         overlapDict: key = OID; value = identical overlap OIDs. The parameter fc         is assumed to be the product of an overlap operation like Union or Intersect."""     # this creates a representation of a geometry string by concatenating various attributes to create a "unique" identifier     def repGeomString(shp):         return str(round(shp.area)) + '|' + str(round(shp.centroid.X, 2)) + '|' + str(round(shp.centroid.Y, 2))     # two dictionaries to keep track of duplicate geometries and their OIDs     geomDictByOID = {}  # key = OID; value = represented geometry string     uniqueGeoms = {}  # key = represented geometry string; value = list of OIDs with same geometry     oidFieldName = arcpy.Describe(fc).oidFieldName     nullCentroids = []     # gather geometries, and if centroid null, append to list     with arcpy.da.SearchCursor(fc, ("OID@", "SHAPE@")) as cursor:         for row in cursor:             try:                 # get full k,v pair of OID and geometries                 geomDictByOID[row[0]] = repGeomString(row[1])                 # initialize empty list as value of unique geometry key                 uniqueGeoms[repGeomString(row[1])] = []             except:                 nullCentroids.append(row[0])     # if null centroids exist, convert features to point and reread centroids     # post-conversion, centroids will exist... for some reason     if len(nullCentroids) > 0:         # Format to string tuple for SQL query, and remove trailing comma for len = 1         if len(nullCentroids) > 1:             nullCentroidsFormat = str(tuple(nullCentroids))         else:             nullCentroidsFormat = str(tuple(nullCentroids)).replace(',', '')         arcpy.MakeFeatureLayer_management(fc, 'nLyr', '"{0}" IN {1}'.format(oidFieldName, nullCentroidsFormat))         nullCentroidsPts = arcpy.FeatureToPoint_management('nLyr', arcpy.Describe(fc).name + 'NullCentroids')         # loop through null centroid features and read new centroids         with arcpy.da.SearchCursor(nullCentroidsPts, ("OID@", "SHAPE@")) as cursor:             for row in cursor:                 # get full k,v pair of OID and geometries                 geomDictByOID[row[0]] = repGeomString(row[1])                 # initialize empty list as value of unique geometry key                 uniqueGeoms[repGeomString(row[1])] = []     # for each geometry key in uniqueGeoms, append all OIDs that match     for oid, g in geomDictByOID.iteritems():         uniqueGeoms .append(oid)     # create dictionary that relates each oid to its overlaps     overlapDict = {}     for oid, g in geomDictByOID.iteritems():         if len(uniqueGeoms ) > 1:             overlapDict[oid] = [k for k in uniqueGeoms if k != oid]     # Delete potentially large dicts     del geomDictByOID     del uniqueGeoms     return overlapDict ... View more

No, they are still different, although the string length difference has changed from 4 to 1. (???) I am running this on a buffer product, and likely these true curves are the culprit. My question is: how does FindIdentical do it? I just need to replicate that without the bells and whistles that slow it down so much. All I'm really interested in is which shapes are identical to each other after a union operation on buffers. ... View more

The string lengths of the WKT values differ, and although the differences are slight, any difference renders them unequal. The FindIdentical tool obviously has some internal geometry tolerance that allows it to overlook these slight differences, and I wonder if we can simulate this in some way by altering the WKT values. I am trying to explore geometries this way because running FindIdentical on large features (>100,000) often crashes or takes forever to run. ... View more

I apologize, but it turns out this is a repeat of a previous issue: http://forums.arcgis.com/threads/69714-Debug-Python-Toolbox Again, a syntax error, this time in a dictionary comprehension, foiled my Python Toolbox. Since it was a syntax error in Python, I figured the debugger should be able to inform me of it. Why does it pick up some errors and ignore others? ... View more

There are over a thousand lines, plus 6 other .py files that get called with close to 500 lines each, so it's not feasible to publish the whole thing. Plus, it's proprietary =D I suppose I'd need someone at ESRI to take a look at it. ... View more

Now having an identical error, yet no GitHub merge conflict text. Even turned on SublimeLinter in SublimeText2 to try and find errors, and came up with nothing. If these are not syntax errors, and are in fact logic errors, why does the .pyt shut down completely and not let me run through the logic of the tool and experience the error myself? Currently, the .pyt has a big red X and tells me "no syntax errors". Any help? ... View more

UPDATE: this error is only thrown for the Union operation, while Identity and Intersect work just fine. ... View more

Let me clarify -- my .pyt calls other custom modules, and if there is a syntax error in one of these modules, a red X appears (rendering the toolbox unusable) and the message is "no syntax errors" even though there is one, though not in the .pyt. Shouldn't the debugger be able to point me to the file with the error? My particular syntax error arose because I am using GitHub and had a merge conflict, which wrote a bunch of lines like "<<<<<<HEAD" as guidance for manual edits. Since one of the custom module scripts had the error, compiling the .pyt worked fine, but as the module is imported, opening the toolbox in ArcGIS won't work. Could there be more direction to errors in imported modules? Otherwise, debugging becomes difficult. ... View more

I found that if you don't specify a search radius, the tool won't split properly, or not at all. ... View more

Just solved it. I never had this issue before, but perhaps this is a new limitation in 10.1? The input parameter to Union must be a list, at least in my case. I put the single input into a list, i.e. arcpy.Union_analysis([input], output) and my tool runs smoothly. If this is a hard rule, it should be emphasized in the tool help. ... View more

I am getting the exact same error, but my input is just one feature class (in order to find overlapping regions). It is called within a Python Toolbox workflow, and consistently throws this error. When I run it outside the tool run session, it works fine. Maddening. Any clues as to what might be going on? ... View more