Latest Contributions by JoshuaBixby

Another approach would be to use regular expressions.  Although regular expressions might be a bit overkill for this specific situation, they are much more flexible to handle more complex situations: with arcpy.da.UpdateCursor(table1,'STREET') as cursor: for row in cursor: row[0] = re.sub(r"^((?:N|S|E|W|North|South|East|West) )+", "", row[0]) cursor.updateRow(row) del cursor The above will result in "N South 5th Street" becoming "5th Street".  If you don't want double prefixes to be removed, just take the "+" out of the regular expression pattern. ... View more

As fun as code golf can be, list comprehensions were proposed and accepted "to create lists" (PEP 202 – List Comprehensions | peps.python.org).  I think many would argue that using a list comprehension to perform a mapping function isn't very Pythonic. ... View more

This won't really be possible because a layer knows what ObjectIDs are selected, but it doesn't know how they were selected.  There are numerous ways to select records, and what is exported in the LYRX or MAPX files are binary references to those ObjectIDs and not references to the tools or methods used to select the records. ... View more

I submitted feedback either last week or earlier this week about it already.  My experience with submitting feedback on documentation through the web pages is that I get better resolution than submitting a documentation defect with Esri Support.  Neither approach results in 100% resolution, not to mention timeliness, but somewhere between 2/3 and 3/4 of my comments get addressed eventually. ... View more

That documentation has an error, one way or the other.  If you copy and paste a bit more of that section:   File-based data, including file geodatabases, shapefiles, in-memory table views, text files such as .dbf, .csv, .txt, .xlsx tables, and feature services that use standardized queries use the ArcGIS SQL dialect that supports a subset of SQL capabilities. Mobile geodatabases, ST_geometry SQLite, GeoPackage, and Excel use SQLite SQL dialect.   The first bullet point says "xlsx tables" use standardized queries, while the second bullet says "Excel use SQLite SQL dialect."  Which one is right?  ... View more

ArcGIS Enterprise on Kubernetes is a completely different product that was introduced at ArcGIS 10.9.  The functionality of ArcGIS Server and ArcGIS Enterprise is being completely reimplemented to run natively in containers, so "ArcGIS Enterprise" and "ArcGIS Enterprise on Kubernetes" are not the same product.  There has never been an "ArcGIS Server" product for Kubernetes, so this really isn't a licensing issue. ... View more

If you are having to regularly restart all ArcGIS Enterprise components in your deployment, then something is definitely not right with the deployment.  If one component is acting up or has to be restarted, that does not mean all components should be restarted. ... View more

Domain logins to ArcGIS Server have to be "mydomain\user" format and not "user/mydomain" format.  What documentation is saying to structure your login that way? ... View more

This is better addressed with Esri Support since community members aren't able to do a call/meeting with you and possibly a screenshare to see what is going on.  I use to run ArcGIS 10.9.1 on Windows Server 2019, and I regularly had several ArcGIS Web Adaptors on the same machine; so I suspect it is something workflow related or environment specific on your end, both of which more information is needed. ... View more

When you say " 6,000+ piece dataset", do you mean the traillistsortpt list is 6,000+ items or the pt_tbl layer has 6,000+ records? ... View more

I only have time to comment on the SearchCursor structure, the current code can be condensed down to two lines: with arcpy.da.SearchCursor(pt_tbl, "NUM_SEC") as cursor2: traillistsortpt = sorted(set(row[0] for row in cursor2)) ... View more

As much as I agree Esri should release a .NET 6 and beyond version for the File Geodatabase API, I think Esri should be more "open" minded and simply release the specificiation.  Releasing the API instead of the specification was a low-bar attempt at being "open" in the first place. ... View more

I am guessing it is a Pro 3.2 issue since: 1) the SQL being passed to SQL Server seems to work fine, and 2) everything renders fine in Pro even with the notification something isn't being parsed correctly. ... View more