Latest Contributions by ThomasLaxson

Yeah, that's what I was afraid of. I'll probably end up doing something similar, but I'll use try/except with getattr, instead of eval. Maybe I'm missing something, but it seems to me that the factory pattern would make more sense than whatever hidden implementation is going on here. They may very well be using the factory pattern on the back-end C classes (I'm assuming that's what they are). But the combination of inconsistent return types and no introspection makes for grotesquely un-Pythonic code. ... View more

No need to mess around with ArcObjects and .NET. You can create your own edit stack. You can simply set a global variable that tracks the edits and is then accessible to other buttons. For example, depending on the complexity of the edits performed by your add-in, you could have a global list to which you append information about the edits. Here's an example of a simple edit button (it just buffers the selected features) with undo and redo buttons. Note that these are not the built-in undo/redo buttons, but Add-In buttons that you create. The edits here will be in a separate stack from the built-in edits. import arcpy import pythonaddins MXD = arcpy.mapping.MapDocument('CURRENT') FN_SHAPE = 'SHAPE@' # Global variables that will store the edit histories forward and backward undo_stack = list() redo_stack = list() class MakeEdits(object):     def __init__(self):         self.enabled = True         self.checked = False     def onClick(self):         # Get the selected layer in the table of contents         lyr = pythonaddins.GetSelectedTOCLayerOrDataFrame()         # Get a count of selected features in the selected layer         fid_set = arcpy.Describe(lyr).FIDSet         if fid_set == '':             count = 0         else:             count = len(fid_set.split(';'))         # If at least one feature is selected         if count > 0:             # Enable global modification of the undo_stack             global undo_stack             # Get the name of the layer's OID field             fn_oid = arcpy.Describe(lyr).OIDFieldName             with arcpy.da.UpdateCursor(lyr, [fn_oid, FN_SHAPE]) as cur:                 for row in cur:                     # Add the relevant details to the editing stack                     undo_stack.append((lyr, fn_oid, row[0], row[1]))                     # An arbitrary example edit                     row[1] = row[1].buffer(500)                     cur.updateRow(row)             arcpy.RefreshActiveView() class RedoEdits(object):     def __init__(self):         self.enabled = True         self.checked = False     def onClick(self):         global undo_stack         global redo_stack         if len(redo_stack) > 0:             # Get the last item in the edit stack             edit = redo_stack.pop()             # Clear any existing selection on the layer, or else the cursor may             #   not hit the necessary feature             arcpy.SelectLayerByAttribute_management(edit[0], 'CLEAR_SELECTION')             # A where clause to select the most recently edited feature             wc = '{} = {}'.format(edit[1], edit[2])             with arcpy.da.UpdateCursor(edit[0], FN_SHAPE, wc) as cur:                 for row in cur:                     # Update the undo edit stack                     edit_out = list(edit[:-1])                     edit_out.append(row[0])                     undo_stack.append(edit_out)                     # Apply the edit                     row[0] = edit[3]                     cur.updateRow(row)                     break         arcpy.RefreshActiveView() class UndoEdits(object):     def __init__(self):         self.enabled = True         self.checked = False     def onClick(self):         global undo_stack         global redo_stack         if len(undo_stack) > 0:             edit = undo_stack.pop()             arcpy.SelectLayerByAttribute_management(edit[0], 'CLEAR_SELECTION')             wc = '{} = {}'.format(edit[1], edit[2])             with arcpy.da.UpdateCursor(edit[0], FN_SHAPE, wc) as cur:                 for row in cur:                     edit_out = list(edit[:-1])                     edit_out.append(row[0])                     redo_stack.append(edit_out)                     row[0] = edit[3]                     cur.updateRow(row)                     break         arcpy.RefreshActiveView()         return‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Since the edit stack is not preserved outside of a given add-in edit session, you can simply set a global variable that tracks the edits and is then accessible to other buttons. For example, depending on the complexity of the edits performed by your add-in, you could have a global list to which you append information about the edits. Here's an example of a simple edit button (it just buffers the selected features) with undo and redo buttons. Note that these are not the built-in undo/redo buttons, but Add-In buttons that you create. The edits here will be in a separate stack from the built-in edits. import arcpy import pythonaddins MXD = arcpy.mapping.MapDocument('CURRENT') FN_SHAPE = 'SHAPE@' # Global variables that will store the edit histories forward and backward undo_stack = list() redo_stack = list() class MakeEdits(object):     def __init__(self):         self.enabled = True         self.checked = False     def onClick(self):         # Get the selected layer in the table of contents         lyr = pythonaddins.GetSelectedTOCLayerOrDataFrame()         # Get a count of selected features in the selected layer         fid_set = arcpy.Describe(lyr).FIDSet         if fid_set == '':             count = 0         else:             count = len(fid_set.split(';'))         # If at least one feature is selected         if count > 0:             # Enable global modification of the undo_stack             global undo_stack             # Get the name of the layer's OID field             fn_oid = arcpy.Describe(lyr).OIDFieldName             with arcpy.da.UpdateCursor(lyr, [fn_oid, FN_SHAPE]) as cur:                 for row in cur:                     # Add the relevant details to the editing stack                     undo_stack.append((lyr, fn_oid, row[0], row[1]))                     # An arbitrary example edit                     row[1] = row[1].buffer(500)                     cur.updateRow(row)             arcpy.RefreshActiveView() class RedoEdits(object):     def __init__(self):         self.enabled = True         self.checked = False     def onClick(self):         global undo_stack         global redo_stack         if len(redo_stack) > 0:             # Get the last item in the edit stack             edit = redo_stack.pop()             # Clear any existing selection on the layer, or else the cursor may             #   not hit the necessary feature             arcpy.SelectLayerByAttribute_management(edit[0], 'CLEAR_SELECTION')             # A where clause to select the most recently edited feature             wc = '{} = {}'.format(edit[1], edit[2])             with arcpy.da.UpdateCursor(edit[0], FN_SHAPE, wc) as cur:                 for row in cur:                     # Update the undo edit stack                     edit_out = list(edit[:-1])                     edit_out.append(row[0])                     undo_stack.append(edit_out)                     # Apply the edit                     row[0] = edit[3]                     cur.updateRow(row)                     break         arcpy.RefreshActiveView() class UndoEdits(object):     def __init__(self):         self.enabled = True         self.checked = False     def onClick(self):         global undo_stack         global redo_stack         if len(undo_stack) > 0:             edit = undo_stack.pop()             arcpy.SelectLayerByAttribute_management(edit[0], 'CLEAR_SELECTION')             wc = '{} = {}'.format(edit[1], edit[2])             with arcpy.da.UpdateCursor(edit[0], FN_SHAPE, wc) as cur:                 for row in cur:                     edit_out = list(edit[:-1])                     edit_out.append(row[0])                     redo_stack.append(edit_out)                     row[0] = edit[3]                     cur.updateRow(row)                     break         arcpy.RefreshActiveView()         return‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

For anyone else who might come across this, an answer on StackExchange worked for me. "this is a resources issue"​. Doing whatever you can to use fewer resources; e.g.: - Ensure you're in a 64-bit/background environment) - Generalize/Simplify your geometries - Repair geometries - Use fgdb (my issue was that I was processing data in an .mdb that some dinosaur had sent me) Best of luck. ... View more

You've got to love ESRI's completely misleading error messages. After encountering the same problem as you, I'm just going to start ignoring the messages--I'll probably save a lot of wasted time. ... View more

This is discussed in detail here: http://forums.arcgis.com/threads/79087-Problem-importing-arcpy-in-ArcMap-console-64-bit-DLL-conflict The most reasonable solution to me is uninstalling Python and then running the repair installation of ArcGIS. ... View more

In my experience, these types of issues appear to be caused by installing PyScripter after installing ArcGIS. The PyScripter installation futzes with the system environment variables and causes some inconsistent behavior, such as sometimes not properly importing arcpy, yielding this error: ImportError: DLL load failed: %1 is not a valid Win32 application. Then again, sometimes it works just fine. The only thing that worked for me was uninstalling Python and then running the repair installation of ArcGIS. ... View more

This error (010093) often occurs when trying to create an improperly named raster file. For GRIDs, the naming restrictions include: ...a grid should not be named with spaces or any other special characters in its name. A multiple-band grid cannot have more than 9 characters in its file name, and a single-band raster dataset cannot have more than 13 characters. Todd, this probably applies in your case, if you're using HUC 12s; the appending of your four characters ('fdr_') puts you over the 13 character limit. See ESRI's help page on GRIDs for more info. ... View more

Internally, we convert the polygon mask to a raster then use that raster to do the extraction. Is this type of behind-the-scenes processing documented somewhere? Being aware of such extraneous steps could really help to reduce processing time. For example, I'm masking 500 rasters to one polygon layer. According to this, it would save me a ton of processing time to convert the polygon layer to a raster just once and then use that raster as my mask layer. The help page for the Extract by Mask tool does not mention this crucial piece of information; is there some other resource where such details are noted for all tools? ... View more

If it's a coworker, then you should be happy that your company/organization can now run a little bit more efficiently due to the code that you wrote. Just make sure that your superiors know who wrote the code when your next performance review rolls around. ... View more

I know this is an old question, but I just encountered a need for this functionality as well, so I thought I'd share my solution: Use Extract By Polygon, and set the extraction area parameter to 'OUTSIDE'. See: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Extract_by_Polygon/009z0000002q000000/ No need to convert between vector and raster and run a series of clips and reclassifications. Just one tool and done. ... View more