Latest Contributions by Peter_Green

‎11-28-2023

This is a handy bit of script to have. Just what I was looking for. Thank you.

‎10-18-2023

Thank you very much, Ayan. 😀 That did the trick. Looks as though my expression was not as complete as I'd thought it was. Regards.

‎10-17-2023

Hello and thank you for your time. I'm running ArcGIS Pro 3.1 on Windows 10. I'm attempting to use Attribute Rules to populate selected fields within a feature class each time a new feature is created. These are the steps I've taken: - I've created a new feature layer and added separate fields to hold X and Y coordinates of new features. For testing purposes, I've tried various data types for these fields, including Long, Float, Double. I've also tested with points, lines and polygons. - In Attribute Rules I've created a separate rules for the X and Y fields. The rules are intended to populate the X and Y coordinate fields using the Centroid($feature) function with the x or y centroid of the feature. See the attached image (Attribute_Rule.jpg) for the rule set-up. When a new feature is created in the feature layer the rule appears to run successfully (i.e. no error messages), however the X and Y fields are populated with "0"s and not the actual coordinate. This happens regardless of the projection, feature class type or feature data type. Here is what I've tried. - I've run this with feature classes/maps in both WGS84 and BNG. - I've tried different data types (long, double, float). - I've tried different feature class types (point, line and poly). - I've also tried calculating the X and Y coordinates using the "Calculate Geometry" tool. When this is run, I receive various warning messages, such as "WARNING 160096: The length of the value exceeds that of the field." See attached for full list of warnings. The process still completes and the fields are calculated with the correct centroid coordinates. - It's worth mentioning that I've also created a separate Attribute Rule to calculate the length or area of lines and polygons. This rule works fine and correctly calculates the values. Not sure what else to try here. I've noted that others have reported similar issues on other posts dating back to v2.7 (circa 2021) but there didn't seem to be a resolution at the time. Thanks for reading. Please let me know if you have any suggestions. Thanks, Peter

‎12-10-2019

I now have a completed script. The following runs successfully from Python Shell. Although I do get errors when running the Script from a toolbox in ArcGIS Pro. I will post a separate question if I can't fix it. It's been a real challenge to my python skills but really enjoyable. The only other thing I'd say is it has been void of comments and are there better ways of tagging python questions? I realise my initial post was a "how do I pythonise this logic and set of processes?" then started to post a python solution. Is it better to come in with some code from the off?.... print ('Comparing Pending against Confirmed...') ##Select ScotWind_Applications_Confirmed by location within 5km of the selected row of ScotWind_Applications_Pending## with arcpy.da.SearchCursor("ScotWind_Applications_Pending", ["OBJECTID", "ScotWind_Applications_SMPJoin_AppID", "Rank", "SHAPE@AREA"], sql_clause=(None, "ORDER BY Rank DESC")) as cursor: for row in cursor: ##Select the current row in ScotWind_Applications_Pending## arcpy.SelectLayerByAttribute_management ("ScotWind_Applications_Pending","NEW_SELECTION", "OBJECTID = {}".format(row[0])) ##Create a Layer of all Confirmed Applications which is updated on each iteration## arcpy.MakeFeatureLayer_management (ScotWind_Applications_Scoring, "ScotWind_Applications_Confirmed") arcpy.management.SelectLayerByAttribute ("ScotWind_Applications_Confirmed", "NEW_SELECTION", "Status = 'Confirmed'", None) area_sum = 0 with arcpy.da.SearchCursor("ScotWind_Applications_Confirmed", ["SHAPE@AREA"]) as cursor2: for row2 in cursor2: area_sum = area_sum + row2[0] print (area_sum) universal_sum = area_sum + row[3] ##Select all Confirmed Applications on each iteration that are within 5km of the arcpy.management.SelectLayerByLocation("ScotWind_Applications_Confirmed", "INTERSECT", "ScotWind_Applications_Pending", "5 Kilometers", "SUBSET_SELECTION", "NOT_INVERT") featurecount = int(arcpy.GetCount_management("ScotWind_Applications_Confirmed").getOutput(0)) print (u'{0}, {1}, {2}, {3}'.format(row[0], row[1], row[2], row[3])) print (featurecount) print (universal_sum) codeblock5 = """def Reclass(Status): if universal_sum > 4500000000: return 'Capped Out' elif featurecount== 0: return 'Confirmed' else: return 'Defeated'""" arcpy.management.CalculateField("ScotWind_Applications_Pending", "Status", "Reclass(!Status!)", "PYTHON3", codeblock5) arcpy.Delete_management("ScotWind_Applications_Confirmed")‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

‎12-05-2019

Some success. I am now iterating through rows of a layer with a selection in the correct descending Rank and my other layer selection is correctly nested meaning a refresh of the select by attribute of that layer prior to the SelectLayerByLocation: print ('Creating Confirmed and Pending subsets...') ##Create a Layer of all Pending Applications ## arcpy.MakeFeatureLayer_management (ScotWind_Applications_Scoring, "ScotWind_Applications_Pending") arcpy.management.SelectLayerByAttribute ("ScotWind_Applications_Pending", "NEW_SELECTION", "Status = 'Pending'", None) print ('Comparing Pending against Confirmed...') ##Select ScotWind_Applications_Confirmed by location within 5km of the selected row of ScotWind_Applications_Pending## with arcpy.da.SearchCursor("ScotWind_Applications_Pending", ["OBJECTID", "ScotWind_Applications_SMPJoin_AppID", "Rank", "SHAPE@AREA"], sql_clause=(None, "ORDER BY Rank DESC")) as cursor: for row in cursor: ##Select the current row in ScotWind_Applications_Pending## arcpy.SelectLayerByAttribute_management ("ScotWind_Applications_Pending","NEW_SELECTION", "OBJECTID = {}".format(row[0])) ##Create a Layer of all Confirmed Applications which is updated on each iteration## arcpy.MakeFeatureLayer_management (ScotWind_Applications_Scoring, "ScotWind_Applications_Confirmed") arcpy.management.SelectLayerByAttribute ("ScotWind_Applications_Confirmed", "NEW_SELECTION", "Status = 'Confirmed'", None) ##Select all Confirmed Applications on each iteration that are within 5km of the arcpy.management.SelectLayerByLocation("ScotWind_Applications_Confirmed", "INTERSECT", "ScotWind_Applications_Pending", "5 Kilometers", "SUBSET_SELECTION", "NOT_INVERT") featurecount = int(arcpy.GetCount_management("ScotWind_Applications_Confirmed").getOutput(0)) print (u'{0}, {1}, {2}, {3}'.format(row[0], row[1], row[2], row[3])) print (featurecount) codeblock5 = """def Reclass(Status): if featurecount == 0: return 'Confirmed' else: return 'Defeated'""" arcpy.management.CalculateField("ScotWind_Applications_Pending", "Status", "Reclass(!Status!)", "PYTHON3", codeblock5) arcpy.Delete_management("ScotWind_Applications_Confirmed")‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I would now like to get the sum of the SHAPE@AREA of ScotWind_Applications_Confirmed and the current SHAPE@AREA of the current row of ScotWind_Applications_Pending in each pass of searchcursor in order to write a pre-condition. If the sum of both is > a numerical maximum, say 8,900, update Status to "Capped Out" else carry out the codeblock 5 and it's calculatefield.

‎11-26-2019

Some progress. The reclass of the Status field now works if the getcount = 0. I swapped the input and target realising (I think) that carrying out a selection on the currently selected row was not the intention. I am now selecting by location the ScotWind_Applications_Confirmed within 5km of the selected feature in the searchcursor. However the results suggest that I need to re-think how I get the searchcursor to re-read the ScotWind_Applications_Confirmed layer each time a feature's Status field is update to 'Confirmed'. Update code: print ('Creating Confirmed and Pending subsets...') ##Create a Layer of all Pending Applications ## arcpy.MakeFeatureLayer_management (ScotWind_Applications_Scoring, "ScotWind_Applications_Pending") arcpy.management.SelectLayerByAttribute ("ScotWind_Applications_Pending", "NEW_SELECTION", "Status = 'Pending'", None) print ('Comparing Pending against Confirmed...') ##Select ScotWind_Applications_Confirmed by location within 5km of the selected row of ScotWind_Applications_Pending## with arcpy.da.SearchCursor("ScotWind_Applications_Pending", ["OBJECTID"], sql_clause=(None, "ORDER BY Rank")) as cursor: for row in cursor: ##Select the current row in ScotWind_Applications_Pending## arcpy.SelectLayerByAttribute_management ("ScotWind_Applications_Pending","NEW_SELECTION", "OBJECTID = {}".format(row[0])) ##Create a Layer of all Confirmed Applications which is updated on each iteration## arcpy.MakeFeatureLayer_management (ScotWind_Applications_Scoring, "ScotWind_Applications_Confirmed") arcpy.management.SelectLayerByAttribute ("ScotWind_Applications_Confirmed", "NEW_SELECTION", "Status = 'Confirmed'", None) ##Select all Confirmed Applications on each iteration that are within 5km of the arcpy.management.SelectLayerByLocation("ScotWind_Applications_Confirmed", "INTERSECT", "ScotWind_Applications_Pending", "5 Kilometers", "SUBSET_SELECTION", "NOT_INVERT") featurecount = int(arcpy.GetCount_management("ScotWind_Applications_Confirmed").getOutput(0)) print (featurecount) codeblock5 = """def Reclass(Status): if featurecount== 0: return 'Confirmed' else: return 'Defeated'""" arcpy.management.CalculateField("ScotWind_Applications_Pending", "Status", "Reclass(!Status!)", "PYTHON3", codeblock5) ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

‎11-26-2019

The results of the print (featurecount) are correct. Could there be in issue where featurecount = 0 impacting on the codeblock here as those row's Status field are not update. Only those row's Status field in the else statement. codeblock5 = """def Reclass(Status): if featurecount == 0: return 'Confirmed' else: return 'Defeated'"""‍‍‍‍‍ I also changed the query codeblock5 = """def Reclass(Status): if featurecount > 0: return 'Defeated' else: return 'Confirmed'"""‍‍‍‍‍‍‍‍‍‍ and still get same result. Only where featurecount > 0 do the row's Status field update. Here is the Python Shell providing what I think is the correct getcount: Creating Confirmed and Pending subsets... Comparing Pending against Confirmed... 0 0 0 0 0 1 0 0 0 0 Processing Complete in 315.59900619999996seconds. >>> ‍‍‍‍‍‍‍‍‍‍‍‍‍‍

‎11-25-2019

I am updating this question, adding some python. I have what I think is a searchcursor iterating through each row of a layer, selecting the current feature, performing a select by location against another layer (which happens to be from the same feature class but with a different query). Count the selected features in each pass. If feature count is zero then reclass a field to "Confirmed" else reclass the field to "Defeated". I have added a print to see the feature count in the python shell at each pass. It is returning the corrent count however where featurecount == '0' the Status field is not updating to "Confirmed". It is correctly updating the Status field to "Defeated" where the else statement is true: print ('Creating Confirmed and Pending subsets...') ##Create a Layer of all Confirmed Applications and Layer of all Pending Applications## arcpy.MakeFeatureLayer_management (ScotWind_Applications_Scoring, "ScotWind_Applications_Pending") arcpy.management.SelectLayerByAttribute ("ScotWind_Applications_Pending", "NEW_SELECTION", "Status = 'Pending'", None) print ('Comparing Pending against Confirmed...') ##Select ScotWind_Applications_Confirmed by location within 5km of the selected row of ScotWind_Applications_Pending## with arcpy.da.SearchCursor("ScotWind_Applications_Pending", ["OBJECTID"], sql_clause=(None, "ORDER BY Rank")) as cursor: for row in cursor: arcpy.SelectLayerByAttribute_management ("ScotWind_Applications_Pending","NEW_SELECTION", "OBJECTID = {}".format(row[0])) arcpy.MakeFeatureLayer_management (ScotWind_Applications_Scoring, "ScotWind_Applications_Confirmed") arcpy.management.SelectLayerByAttribute ("ScotWind_Applications_Confirmed", "NEW_SELECTION", "Status = 'Confirmed'", None) arcpy.management.SelectLayerByLocation("ScotWind_Applications_Pending", "INTERSECT", "ScotWind_Applications_Confirmed", "5 Kilometers", "SUBSET_SELECTION", "NOT_INVERT") featurecount = int(arcpy.GetCount_management("ScotWind_Applications_Pending").getOutput(0)) print (featurecount) codeblock5 = """def Reclass(Status): if featurecount == '0': return 'Confirmed' else: return 'Defeated'""" arcpy.management.CalculateField("ScotWind_Applications_Pending", "Status", "Reclass(!Status!)", "PYTHON3", codeblock5) endtime = time.clock() print ("Processing Complete in " + str(endtime-starttime) + "seconds.") ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

‎11-19-2019

Hello. Python 3.6.8, ArcGIS Pro, file geodatabase. I have a feature class Applications which is the result of a previous script. Fields I am interested in are Status (string), Rank (integer), Area.Shape. One of the features in Applications already has a Status = "Confirmed". It's the row with the highest Rank. Other Status values are null, "Failed", "Pending". Below is a mixture of aspiration of the script and a proposed method although I have to admit this is stretching the limits of my current python. I am not sure this process is possible after looking a other scripts that use da.updatecursor? I would like to - Create Pending_Applications layer from Applications feature class where Status = "Pending" Create Confirmed_Applications layer from Applications feature class where Status = "Confirmed". Iterate in order of Rank field the Pending_Applications- select the record of the current row If the selected feature intersects the Confirmed_Applications layer update the Status field to "Defeated" else if it does not intersect Confirmed_Applications update the Status field to "Confirmed" (if sum of Area.Shape of the Confirmed_Applications + the Area.Shape of the current row =< 8,000) else update the Status field to "Capped Out" (if sum of Area.Shape of the Confirmed_Applications + the Area.Shape of the current row > 8,000) update the Status field to "Capped Out". Once a row is updated would the next iteration re-read the Confirmed_Applications layer again with additional features where the Status had been updated to "Confirmed" in previous iterations? Many tanks. Marc

‎04-24-2019

I have used check geometry and get 262 features with the Problem value of "short segments". However, I have run a check geometry on last year's retained fgdb feature class that was sucessfully imported last year into the same enterprise geodatabase and the report presents similar findings. Some features "short segments". I will attempt your other suggestions of creating an empty schema enterprise geodatabase and appending the data. Thank you

‎04-24-2019

I have tried to copy and paste into the enterprise geodatabase connection. It provided data transfer progress. Yesterday it appeared to copy all features: but ArcCatalog hung for several hours after displaying all features had been copied and the desktop slowed down until unusable. A forced crash of ArcCatalog was required and there was no imported featured class: 2nd and 3rd attempts show some progress in transferring features then I get a Paste failed error:

‎04-23-2019

I am attempting to import feature classes in a fgdb into an enterprise database. ArcGIS for Desktop 10.3.1. Enterprise Databases in SQL Server 2014. Two of the features classes are large. In ArcCatalog when I select to import feature class (single) into the enterprise database and select to import one of the large feature classes I get the error 000224: Cannot insert features. When I select to import feature class (multiple) and select all the feature classes in the fgdb that I want to import into the enterprise database the smaller feature classes import, then when the processing attempts to import the two largest features classes the same error 000224 occurs. I am replacing existing feature classes in the enterprise database by attempting to import the new and when succesfully imported and tested remove the existing and rename the new feature classes to those of the originals. Enterprise database properties that I can view in SQL Server Management Studio are ROWS Data: Initial Size 104,024 MB and Autogrowth/Maxsize is 10%, unlimited. LOG: Initial size 74,248MB, Autogrowth/Maxsize 2,097MB,152MB. The original feature classes that currently exist in the enterprise geodatabase have the following Storage Properties; one has Index Space 1,273MB, Row count 12839349, Data space 15,007MB and the other has Index Space 2,085MB, Row count 36072588, Data space 23,140.688MB. The new versions should not vastly vary from the existing in terms of those properties. Previous methodology was to merely delete the original feature classes and import the new. I am being more cautious in wanting to import the new and retain the existing until tested. The fgdb feature classes that I want to import I can load into ArcMap and view without error. I am using a dataloader connection that has insert permissions and I have tested successfully importing other objects into the enterprise geodatabase. Could amending the Autogrowth/Maxsize properties on the enterprise geodatabase resolve the issue? Many thanks.

‎10-01-2018

Issue is back. After 3 weeks of the user being able to connect to the databases with the connection (now that a new account with a shorter username) the user logs in today and gets the same message and can't connect. "Failed to connect to database. Underlying DBMS error[IM002:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specifiedNo extended error.]" No change in configuration, same connection file on the user's c:\ drive on their desktop. Other accounts in the User Group can connect, read and edit. My hunch is this is some issue with Windows Authentication rather than GIS Enterprise database configuration. Can anyone help or point me in the direction of some things to examine? Thanks.

‎09-18-2018

Thanks for your help George. When I closed the case with ESRI their response was exactly the same. I've asked our IT Partners to capture this requirement when creating new accounts that need access to our GIS databases. The IT Partners do the support but did not do the initial configuration and I don't have the help of a dedicated DBA but I am learning!

‎09-18-2018

This was resolved. I pinned down our IT Partners, who created a new test Windows Account. This account was given the operating system connection files and could successfully connect to the databases with the connections. The new member of staff whose account could not connect had their Windows account disabled and re-created, were given the connection files and still could not connect. The new member of staff's Windows Account name was 16 characters long. We created another new account, reducing the length of characters to 15. This new Windows account can connect using the connection files succesfully.

Online Status	Online
Date Last Visited	6 hours ago

My Ideas

Latest Contributions by Peter_Green

Re: Copy enterprise geodatabase to file geodatabase

Re: Calculating Centroids using Attribute Rules

Calculating Centroids using Attribute Rules

Re: Iterate through rows, select row, select by location, update cursor

Re: Iterate through rows, select row, select by location, update cursor

Re: Iterate through rows, select row, select by location, update cursor

Re: Iterate through rows, select row, select by location, update cursor

Re: Iterate through rows, select row, select by location, update cursor

Iterate through rows, select row, select by location, update cursor

Re: Error 000224: Cannot insert features when importing large feature class into enterprise database

Re: Error 000224: Cannot insert features when importing large feature class into enterprise database

Error 000224: Cannot insert features when importing large feature class into enterprise database

Re: Failed to connect to database. Underlying DBMS error[IM002:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specifiedNo extended error.]

Re: Failed to connect to database. Underlying DBMS error[IM002:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specifiedNo extended error.]

Re: Failed to connect to database. Underlying DBMS error[IM002:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specifiedNo extended error.]

Calculating Centroids using Attribute Rules

Re: Iterate through rows, select row, select by lo...

Re: Failed to connect to database. Underlying DBMS...

Re: Failed to connect to database. Underlying DBMS...