Latest Contributions by BlakeTerhune

I've done something similar and the Near table worked for me. When I was doing this, I also found it frustrating that the Near table would only show the ObjectID of the features, requiring additional joins to actually see what features the OIDs were for. I created this Python script that will create a Near table with a key field of your choice in the output. I haven't tested it much but maybe you can get some use out of it. import arcpy import os try:     # Set local variables     sourceGDB = r"C:\temp\mytempsource.gdb"     outputGDB = r"C:\temp\mytempoutput.gdb"     ## IN and NEAR features can be the same     in_fc = "FeatureClassIn_Name"     in_fc_keyfield_name = "KeyField_Name"     in_fc_keyfield_type = "Long"     in_fc_path = os.path.join(sourceGDB, in_fc)     near_fc = "FeatureClassNear_Name"     near_fc_keyfield_name = "KeyField_Name"     near_fc_keyfield_type = "Long"     near_fc_path = os.path.join(sourceGDB, near_fc)     search_radius = "25 Feet"     # Create near table and make as TableView     neartable_inmem = os.path.join("in_memory", "neartable_inmem")     arcpy.GenerateNearTable_analysis(         in_fc_path,  ## in_features         near_fc_path,  ## near_features         neartable_inmem,  ## out_table         search_radius,  ## search_radius         "NO_LOCATION",  ## location         "NO_ANGLE",  ## angle         "ALL",  ## closest         "0",  ## closest_count         "PLANAR"  ## method     )     arcpy.MakeTableView_management(neartable_inmem, "neartable_view")     print "Near table view created"     # Add new IN and NEAR key fields to near table     in_kf = "IN_{}".format(in_fc_keyfield_name)     arcpy.AddField_management(         "neartable_view",  ## in_table         in_kf,  ## field_name         in_fc_keyfield_type,  ## field_type     )     near_kf = "NEAR_{}".format(near_fc_keyfield_name)     arcpy.AddField_management(         "neartable_view",  ## in_table         near_kf,  ## field_name         near_fc_keyfield_type,  ## field_type     )     print "Key fields added"     # Join and calc IN key field     arcpy.AddJoin_management(         "neartable_view",  ## in_layer_or_view         "IN_FID",  ## in_field         in_fc_path,  ## join_table         "OBJECTID",  ## join_field         "KEEP_COMMON"  ## join_type     )     arcpy.CalculateField_management(         "neartable_view",  ## in_table         in_kf,  ## field         "!{}!".format(in_fc_keyfield_name),  ## expression         "PYTHON_9.3"  ## expression_type     )     arcpy.RemoveJoin_management("neartable_view")     print "{} field populated".format(in_kf)     # Join and calc NEAR key field     arcpy.AddJoin_management(         "neartable_view",  ## in_layer_or_view         "NEAR_FID",  ## in_field         near_fc_path,  ## join_table         "OBJECTID",  ## join_field         "KEEP_COMMON"  ## join_type     )     arcpy.CalculateField_management(         "neartable_view",  ## in_table         near_kf,  ## field         "!{}!".format(near_fc_keyfield_name),  ## expression         "PYTHON_9.3"  ## expression_type     )     arcpy.RemoveJoin_management("neartable_view")     print "{} field populated".format(near_kf)     # Export final near table     kf_near_table = "{}_NEAR".format(in_fc.replace('.', '_'))  ## Replace any dot with underscore and add _NEAR suffix     kf_near_table_path = os.path.join(outputGDB, kf_near_table)     arcpy.CopyRows_management(         "neartable_view",  ## in_rows         kf_near_table_path  ## out_table     )     print "Final near table output at {}".format(kf_near_table_path) except Exception as err:     print err     ## If there was an ArcPy error, write all of the messages returned by the last tool     if arcpy.GetMessages(2):         print arcpy.GetMessages() finally:     # Cleanup     arcpy.Delete_management("in_memory")     arcpy.ClearWorkspaceCache_management() ... View more

Psst! Posting your code with syntax highlighting is appreciated! Posting Code blocks in the new GeoNet ... View more

You can do this in PyScripter. Go to Tools ---> Options ---> IDE Options Then in the Code Completion part add arcpy to the Special Packages list. It does have a noticeable impact on performance though. It will hang for a few moments sometimes on the first load but once it gets the special packages read, it works fine. ... View more

Thanks Jake, that was very helpful. The only extra step I needed was to add a new directory (of type Cache) in ArcGIS Server Manager (not just the data store registered folders). That allowed me to choose the new cache directory in step 4 you described. And an extra note on that, the cache directory that you add needs to be the folder containing the cache folder, not the folder that contains the cache file. The first time I added the directory in Server Manager, I went all the way down to the last folder that contained the cache file, but it actually needs to be one folder up from that. ... View more

So is everyone editing on the same version? You can test it now by just creating a new version. ... View more

Seems like you would want to create the search cursor on just the selected features instead of everything in the point feature class. I think the way you have it now would copy all rows in the point feature class to the related tables each time a new point was added (creating duplicate records in the related tables). ... View more

If you are editing the same record on the same version as someone else, there is conflicting data. I don't know why ArcMap would just crash, but I can see that there is potentially a problem here. Can you try doing this without anyone else editing or create a new version to do your edits in? I've used calculate field in ArcMap on thousands of records without issue; it just took a bit to process. ... View more

Yeah, I was looking at the return value for the next() method. I see the second second sentence at the very beginning clearly says: Returns an iterator of lists. But down at the bottom under the Method overview for next(), it says: Returns the next row as a tuple. I tested both the next() method and just iterating through the whole cursor in a for loop and both give the row as a list (like you said). Esri's documentation for the next() method is just wrong. ... View more

When you make directory path strings, you can either use the double backslash to escape the special character, or you can use the r prefix to designate the string as "raw" so it will not consider a single backslash as a special character. You have combined both methods and will probably not work. You need to do one or the other. Personally, I like to use the raw string method: arcpy.env.workspace = r"G:\GISAdmin\Database_Management\Compress.sde" ... View more

Are you using versions? What is your method/criteria for selecting the records? ... View more

Even though the documentation says tuple, it does return a list. Thanks for the clarification! ... View more

In addition to the points Darren Wiens made, the rows returned by the update cursor are a tuple. In Python, a tuple is what's called an immutable object; it cannot be changed. You have to convert the row from a tuple to a list before you can change the values. Then you can pass the altered row list back to the cursor's updateRow() method (which accepts a tuple or list). You can also create the update cursor with only the fields you are interested in so you don't have to loop through all the fields unnecessarily. This code assumes the data type of the length_val field is integer. It also assumes that if total_length was a string, that it would never have more than one number. aoi_fields = ["total_length", "length_val"] with arcpy.da.UpdateCursor(aoi_table_gdb, aoi_fields) as cursor:     for row in cursor:         rowList = list(row)         if isinstance(rowList[0], int) or isinstance(rowList[1], float):             rowList[1] = int(rowList[0])         elif isinstance(rowList[1], basestring):             # Pull out only the number from the string             rowList[1] = int(filter(str.isdigit, rowList[0]))         else:             rowList[1] = None         cursor.updateRow(rowList) I used this thread for extracting the number from the string. Alternatively, you could use Calculate Field to do this (instead of an arcpy.da cursor). ... View more

Same. Worked for me in PyScripter with ArcGIS 10.2.2 using a path to the local C:\ drive. ... View more