Latest Contributions by RandyBurton

I've had that feeling, too.  Glad to help. ... View more

As you asked about using a dicitonary as part of the solution, here is an approach similar to the one suggested by Nicholas Klein-Baer‌.  I used the collections dictionary which simplifies things when the values are lists. One issue that may be contributing to the problem is that when 2 features using the same field names are joined, the joined feature's fiields will be renamed, usually by appending "_1".  You should check the join to verify that you are using the proper field names. Here is my test code: import collections d = collections.defaultdict(list) polygons = 'buildoutPolygons1' # outer polygons that border groups of parcels parcels = 'buildoutParcels1' joined = 'in_memory\\test_join' # this can be temporary # join blocks to parcels arcpy.SpatialJoin_analysis( target_features = parcels, join_features = polygons, out_feature_class = joined, join_operation = "JOIN_ONE_TO_ONE", join_type = "KEEP_COMMON", match_option = "HAVE_THEIR_CENTER_IN") # NOTE: both polygons and parcels contain the fields: OBJECTID and PARCEL # the join has appended "_1" to these fields from polygons # *** verify this before continuing *** fields2dict = ['PARCEL_1', 'PARCEL' ] # key is from polygons and value is from parcels # an alternative is to use OBJECTID_1 in place of PARCEL_1 # search cursor processes joined feature into dictionary with arcpy.da.SearchCursor(joined, fields2dict) as cursor: for key, value in cursor: d[key].append(value) # print d # dictionary will be in format { 'BLOCK_ID' : [ 'PIN_ID_1', 'PIN_ID_2', ... ], ... } # examining the dictionary will help determine if length of for k in d.keys(): print k, "parcels = {} : field length = {}".format(len(d ),len(d )*12) # the PARCEL field in polygons will be the key, PARCELS will be updated updateFields = ['PARCEL','PARCELS'] # BLOCK matches dictionary key # NOTE this will fail as field length needs to be about 800 characters wide # shapefiles have a text field limit of 250 characters # update cursor uses dictionary d to update PINS field with arcpy.da.UpdateCursor(parcels, updateFields) as cursor: for row in cursor: row[1] = ','.join(d[row[0]]) # row[0] is key for dictionary, row[1] will be updated with list cursor.updateRow(row) arcpy.Delete_management(joined) # delete in_memory object # refresh may be required to see changes‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ As I mentioned in my previous post, some of the parcel id numbers concatenate into a string longer than the width of the field.  Lines 31 an 32 will print an estimate of the required field width to store the concatenated string. R3590700000 parcels = 66 : field length = 792 R3601400000 parcels = 7 : field length = 84 R3733600000 parcels = 3 : field length = 36 R3612900000 parcels = 4 : field length = 48 R3681301000 parcels = 4 : field length = 48 R3681100000 parcels = 2 : field length = 24 R3676401100 parcels = 5 : field length = 60 R3682300000 parcels = 1 : field length = 12 R3602300000 parcels = 2 : field length = 24 R3701400000 parcels = 1 : field length = 12 R3690600000 parcels = 2 : field length = 24 R36103010A0 parcels = 8 : field length = 96 R3675500000 parcels = 12 : field length = 144 R3610302000 parcels = 6 : field length = 72 R3691500000 parcels = 1 : field length = 12 R3613301000 parcels = 5 : field length = 60 R3608900000 parcels = 10 : field length = 120 R3608601000 parcels = 1 : field length = 12 R3602601000 parcels = 16 : field length = 192 R3610100000 parcels = 3 : field length = 36 R3663801000 parcels = 54 : field length = 648 R3729700000 parcels = 6 : field length = 72 R3675400000 parcels = 2 : field length = 24 R3613500000 parcels = 1 : field length = 12 R3710800000 parcels = 1 : field length = 12 R3613600000 parcels = 2 : field length = 24 R3701500000 parcels = 2 : field length = 24 R3666600000 parcels = 2 : field length = 24 R3612901100 parcels = 8 : field length = 96 R3703500000 parcels = 3 : field length = 36 R3678200000 parcels = 4 : field length = 48 R3702500000 parcels = 2 : field length = 24 R3672200000 parcels = 1 : field length = 12 R3677000000 parcels = 6 : field length = 72 R3671100000 parcels = 2 : field length = 24 R3703200000 parcels = 1 : field length = 12 R3676200000 parcels = 2 : field length = 24 R3672300000 parcels = 4 : field length = 48 R3682600000 parcels = 14 : field length = 168 R3610301000 parcels = 2 : field length = 24 R3608600000 parcels = 2 : field length = 24 R3600000000 parcels = 1 : field length = 12 R3710501200 parcels = 2 : field length = 24 R3665700000 parcels = 2 : field length = 24 R3592200000 parcels = 17 : field length = 204 R3612300000 parcels = 2 : field length = 24 R3679300000 parcels = 1 : field length = 12 R3677601000 parcels = 6 : field length = 72 R3733400000 parcels = 1 : field length = 12 R3602401100 parcels = 1 : field length = 12 R3667800000 parcels = 2 : field length = 24 R3678700000 parcels = 4 : field length = 48 R3663700000 parcels = 3 : field length = 36 R3612400000 parcels = 3 : field length = 36 R3679501000 parcels = 8 : field length = 96‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Two of the "buildoutPolygon" features have more parcel id's than will fit in a field width of 250 characters. Hope this helps. ... View more

Although the old InsertCursor still works with 10.8, you may wish to convert to the faster da.InsertCursor. ... View more

Can you share the field layout of the two features that are being joined with, perhaps, some sample data?  It would be helpful in understanding what needs to be done. ... View more

In my experience (only with AGOL), I only update sections.  In your case since you want to add additional domains, the section would be the fields section, and it would only contain the fields using the domain being changed.  This way, the things that cannot be changed, such as "allowGeometryUpdates", are not included.  I also do not include the "drawingInfo" section.  Since you are working with domains, the "types" section may need editing depending on the set up. For example, to add the color Blue to a domain list, start with the comma on line 24 and add through line 28.  Then check it with something like jsonlint for valid json before updating.   Also, experiment on a backup of the service first. { "fields": [{ "name": "Color", "type": "esriFieldTypeString", "alias": "Point Color", "sqlType": "sqlTypeOther", "length": 1, "nullable": false, "editable": true, "domain": { "type": "codedValue", "name": "Colors", "codedValues": [{ "name": "Red", "code": "1" }, { "name": "Yellow", "code": "2" }, { "name": "Green", "code": "3" }, { "name": "Blue", "code": "4" } ] }, "defaultValue": null }] }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

From your picture, it looks like you are getting the feature's definition information.  The "drawingInfo" and "imageData" is indicating the default symbology to use when drawing your feature.  My guess is that you missed the word "/query" at the end of the URL string.  The link you followed shows this example: https://services3.arcgis.com/GVgbJbqm8hXASVYi/arcgis/rest/services/Trailheads/FeatureServer/0/query Trailheads is the name of the feature service, and the first layer (zero) is being queried. ... View more

It looks as if the {0} should be replaced with something via .format.  For example: fc = r"C:\Path\To\File.gdb\feature" FieldMapString = """PIN "PIN" true true false 13 Text 0 0 ,First,#, {0}, PIN,-1,-1;""".format(fc) Print FieldMapString # PIN "PIN" true true false 13 Text 0 0 ,First,#, C:\Path\To\File.gdb\feature, PIN,-1,-1; ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Based on some of your past questions, I assume you are using a file geodatabase with Desktop.  You could do a daily export to a network file that the engineers, etc. could access/query via some program. But, I imagine that it would also be helpful for your engineers to see the data located on a map.  This could be allowing your users to query an online map such as Portal or ArcGIS Online.  Apps like Collector and Explorer would then be easy to use options to query the data. Desktop should come with an AGOL account, so you should be able to do some experimenting. ... View more

Some of the problems I've come across (with iPhones and Collector most frequently) involves auto-correct where an apostrophe or quote will be replaced with the "intelligent" version which can take you to unicode errors. ... View more

My first thoughts would be to examine lines 77-85.  I think the backslashes are causing your problem; they are used to escape certain characters.  I think the specific problem is occurring with the '\2020'.  Put a small r in front of your variables. # Instead of: # Local variables: Output = "C:\Users\Transportation\Desktop\2020CrashDataFiles\Script\Output Files\\Model_Buffer.shp" SpatialJoin_shp = "C:\Users\Transportation\Desktop\2020CrashDataFiles\Script\Output Files\\Joined.shp" # Try: # Local variables: Output = r"C:\Users\Transportation\Desktop\2020CrashDataFiles\Script\Output Files\Model_Buffer.shp" SpatialJoin_shp = r"C:\Users\Transportation\Desktop\2020CrashDataFiles\Script\Output Files\Joined.shp" ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ The other variables in line 88 are from user input parameters in lines 9-10 and lines 77-85.  You may need to check the values the user entered if you are still having issues. ... View more

I made several attempts to generate an error similar to yours, but the tool seemed to handle a variety of situations quite well.  For example, I tried the "POINT_X_Y_Z_M" option with polygon and line features, and the tool responded with appropriate error messages.  Since the error message is coming from inside the AddGeometryAttributes tool, I would suspect the issue is with your wHydrantValveGPS feature layer - perhaps bad geometry, or some other corruption. Does the feature load properly in Desktop?  Have you tried the actual tool in Desktop? The tool's dialog box may provide some additional error messages as the tool validator script will be invoked as the parameters are checked. ... View more