Latest Contributions by JoshuaBixby

I just applied the 2.9.1 patch, and I ran some basic tests against polygon feature classes, and I am not seeing what you are seeing. I get <Polygon object at ...> when printing row and row[1]. Can you share a sample of the data set?

I haven't had a chance to dive in, but you should always share what version it last worked for you and what version you are using now. Saying "since updating, I am having a problem" doesn't give folks much to go on, especially if you think the issue is related to a change in Pro versions.

Interesting that Compact doesn't work well for you, we have really good results using that tool to clean up and shrink the size of bloated FGDBs.

@AlexKweya, up until a certain Pro 2.x version (I can't remember the exact version), ArcGIS Pro was not looking for the Office data drivers in the right place when users had Click-to-Run (CTR) installations, so users had to install the MS Access Database Engine driver even if they had an MS Office CTR installation. That issue has been corrected.

In your second code snippet, the overall search cursor and the update cursor in SpatialRenumberPoints are independent of each other. The reason the numbering isn't resetting is that the numbering is starting at 1 and going until the end for all records each time you call SpatialRenumberPoints. What might work is if you pass the CLUSTER_ID value through to SpatialRenumberPoints as a new argument, and then add a SQL WHERE clause to the update cursor in SpatialRenumberPoints to filter records to only that CLUSTER_ID.

Is the Geocoded_20210412 table in the same GDB as the data set being selected against?

Johannes, The WHERE clause does allow you to query other feature classes or tables in the same GDB as the data set being selected against. That said, not ever data source supports is (like shape files). Also, not every data source supports all the functionality the same. The Subqueries section of SQL reference for query expressions used in ArcGIS—ArcGIS Pro | Documentation covers most of the details.

Have you seen this Esri Community thread? It seems related: Solved: ArcMap.cache.data file getting huge - Esri Community

This isn't a Survey123, Python, or even Esri issue; you are running into a limitation of SQL Server. I suggest you do a general internet search for that SQL Server error message and also talk with a SQL Server DBA regarding why you are running into this issue.

Re: Member De-Introduction · ‎12-21-2021

@JoeBorgione, congratulations on retirement, and happy trails on your next chapter. As others have noted, it would be great if you would pop in from time to time.

Online Status	Offline
Date Last Visited	2 hours ago

My Ideas

Latest Contributions by JoshuaBixby

Re: arcpy problem grabbing SHAPE@ token using index

Re: arcpy problem grabbing SHAPE@ token using index

Re: File geodatabase is getting fat extremely

Re: Error Required Microsoft Driver is not installed?

Re: da.SearchCursor: Nested cursor will not 'reset'

Re: Using Subqueries

Re: Using Subqueries

Re: CLEAR CACHE

Re: Python Script - Row Size Error

Re: Member De-Introduction

Esri Forestry Group (EFG)