Latest Contributions by MJChurchill

When editing cells sequentially in a Shapefile table, ArcGIS Pro will begin to fail to correctly recognize what should be entered in the cell. It will fail to recognize keystrokes, leave characters behind from the previous cell value, enter characters out of order, and will even jump to other cells in the same column (usually previous cells). This behaviour also occurs when editing in the attributes pane when you are hitting enter to get to the next field then start typing. Steps to create the issue: 1. Load a Shapefile (and optionally another layer or layers) into an ArcGIS Pro(2.6.x) map. 2. Turn on labels for any of the layers and zoom the map so a certain number of labels are visible(perhaps as few as 20 but this may depend on your computer's speed, how many layers you have, how many have labels turned on, perhaps even the number of characters in the labels, etc.) 3. Open the attribute table of the Shapefile. 4. Begin editing by typing in a cell then hitting enter to get to the next record and do that repeatedly without pausing for more that a second or two between hitting enter and beginning to type in the next cell. (Or, select a feature and open the attributes pane and begin editing fields by typing then hitting then typing, etc. to edit multiple fields for the record. This assumes of course that there are at least several fields in the table.) This issue occurs with ArcGIS Pro 2.6.x (I am currently at 2.6.2 but began noticing this issue at least at 2.6.0). It has likely been present since the ability to edit in this way was added. (This functionality was requested in an idea in 2017 by Nicholas McNamara.) Also see Rich Emerson's idea which seems related ("Do not refresh screen if editing an attribute not connected to display properties") My system info, in case it is pertinent: Windows 10 Pro, 16GB memory; 64-bit; Intel(R) Core(TM) i7-7500U CPU @ 2.7GHz 2.90GHz The workarounds for this issue are pretty simple: just turn off labels or pause drawing while editing. However, it is annoying and you can end up with weird values in your data if you don't immediately notice it's happening. (Thankfully I don't generally work with important dollar figures or planning measurements.) This is more of a bug than an idea but Esri support recommended I post it here. ... View more

Thank you in advance for any assistance. My problem is that arcpy functions do not seem to recognize each others' results. Specifically: arcpy.da.SearchCursor does not seem to recognize SelectLayerByAttribute having cleared the selection; and SelectLayerByLocation does not recognize either that SelectLayerByAtttribute cleared the selection or that it was then used to make a new selection. The code sample below is from a longer script which iterates through features selected by the user then uses one of those features, given by the user as a parameter to the tool, to do further analysis. But I have limited the code sample below to the part that is a problem. I am running the script as a tool in an ArcGIS Pro project. (2.5.0) & the data is a Shapefile of lines. Note that in the full code, the argument rstart would be the parameter to the tool and would be selected by the user from a list created by the tool validation script (from ROUTENUM values of selected features). However, for the example, assume that at least one record was selected before the tool was run and the function in the code was run with the call: generateNewRoute(211)‍ Here is the code: import arcpy ## Get references to ArcGIS Pro objects pro_proj=arcpy.mp.ArcGISProject("CURRENT") r_map = pro_proj.listMaps("Map")[0] routelyr = r_map.listLayers("routes")[0] def generateNewRoute(rstart): fields = ['ROUTENUM'] wc="ROUTENUM = " + str(rstart) rnums=[] cnums=[] nnums=[] # correctly prints "ROUTENUM = 211" so SQL seems fine arcpy.AddMessage(wc) # Clear any existing selection arcpy.SelectLayerByAttribute_management(routelyr, "CLEAR_SELECTION") # Check that no records are selected: (This should now return a # list of all records (the behaviour of SearchCursor if no records # are selected) but instead returns a list of records that # were selected prior to running the tool with arcpy.da.SearchCursor(routelyr, fields) as selectioncleared: for n in selectioncleared: nnums.append(n[0]) arcpy.AddMessage("Should be all recs:" + str(nnums)) # select the feature we want to use in SelectLayerByLocation # In this case the feature with ROUTENUM = 211: arcpy.SelectLayerByAttribute_management(routelyr, "NEW_SELECTION", where_clause=wc) # Check that the record was selected: This correctly prints the message # "Selected records: [211]" with arcpy.da.SearchCursor(routelyr, fields) as selectedrecs: for r in selectedrecs: rnums.append(r[0]) arcpy.AddMessage("Selected records: " + str(rnums)) # Select records touching the boundary of the selected record. arcpy.SelectLayerByLocation_management(routelyr, "boundary_touches", select_features=routelyr, selection_type="NEW_SELECTION") # Check the result: This should return a list of records touching # the endpoints of record 211. But, instead it returns a list of # records touching the endpoints of records selected prior to # running the tool (or, if no records were previously selected, a # list of all records that have any endpoints touching an endpoint # of another feature) with arcpy.da.SearchCursor(routelyr, fields) as connectedrecs: for c in connectedrecs: cnums.append(c[0]) arcpy.AddMessage("Connected records: " + str(rnums)) ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ What I need is a list of the features touching the boundary of a feature selected by SelectLayerByAttribute_management (in the example, record with ROUTENUM = 211 but ultimately with values that would be generated in the code, not from a preexisting selection.) If someone could tell me what I am doing wrong here, I would be very appreciative. Thanks, M.J. ... View more

Hello, I am wondering if anyone else has encountered the following issue: I have a polygon layer in ArcMap with several classes. One of the classes is symbolized with an outline and a simple fill, the rest are symbolized with an outline and no fill. Transparency for all layers is set to 0. In the ArcMap window the data displays as it should with the background white and the filled polgyons grey: [ATTACH=CONFIG]26122[/ATTACH]  However, when I export the map (I've tried exporting as .jpg and .pdf), it makes the background the same colour as the filled polygons: [ATTACH=CONFIG]26123[/ATTACH] If anyone knows how to prevent this from happening, please let me know. Thanks, M.J. ... View more