Latest Contributions by JoshuaBixby

My recommendation, install and configure an Anaconda environment to work with Visual Studio, then install Arcpy :: Anaconda.org. ... View more

@KoryKramer , I know this is a lost cause, but I have to bring it up, again.  It has been nearly 3 years since this issue was logged and "the team" supposedly made aware of it.  Is the goal at this point just have the mobile geodatabase completely supplant the file geodatabase and the issue of documenting pattern matching in file geodatabases is moot? ... View more

Lots of ways to accomplish this, here is one: from statistics import mean tbl = # path to table with arcpy.da.SearchCursor(tbl, "Count") as cur: avg = mean(row[0] for row in cur if row[0] > 0) ... View more

On my machine with Pro, I don't have or use quotes around my sheet names and everything works fine. >>> import arcpy >>> >>> # pass Excel worksheet with no quotes to search cursor >>> with arcpy.da.SearchCursor(r"E:\tmp\sample.xlsx\Sheet1$", "*") as cur: ... for row in cur: ... print(row) ... (10.0, 'g', 10.3, 1) ... (22.0, 'i', -1.5, 11) >>> >>> # pass Excel worksheet with single quotes to search cursor >>> with arcpy.da.SearchCursor(r"E:\tmp\sample.xlsx\'Sheet1$'", "*") as cur: ... for row in cur: ... print(row) ... Traceback (most recent call last): File "<stdin>", line 1, in <module> RuntimeError: cannot open 'E:\tmp\sample.xlsx\'Sheet1$'' >>> ... View more

In this case, ArcPy cursors are simply iterables to tee, and the cursors are treated just like tee would treat any other iterable when splitting it. The itertools — Functions creating iterators for efficient looping — Python 3.9.4 documentation states: Once tee() has made a split, the original iterable should not be used anywhere else; otherwise, the iterable could get advanced without the tee objects being informed. For ArcPy cursors, the iterators returned back from tee do not have an updateRow() method, which is why I refer back to the cursor object to update the row.  That said, you will notice that I am not iterating the original cursor because doing so would create a situation where the tee iterators miss rows of data. ArcPy cursors are "forward-only" cursors, meaning they can only move one direction through the data set once defined.  Once the cursors has visited row x+1, it can't go back to row x unless the cursor is reset, which takes the cursor back to the start of the data set.  Since ArcPy cursors are forward-only, the tee iterator that is furthest through the data set determines where the original cursor object is in the data set. ... View more

What is your input_xls?  Is it a pandas DataFrame? ... View more

Remove the single quotes from around the worksheet name. ... View more

There is a fair amount of nuance/difference in how different DMBSs implement Date/Time SQL support.  Which back-end DBMS are you working with? ... View more

Can you elaborate more on how exactly you are going about your calculations, and how are you determining the outputs are incorrect?  For example, are you creating basic square polygons of 1 yard x 1 yard and looking at the area field ArcGIS calculates? ... View more

There are a couple of handy things about tee that aren't used in this simple situation.  For example, you can split an iterable into as many independent iterators as you like, it doesn't have to be just two.  Since the iterators are independent of each other, each can be at a various spot.  The tricky part with update cursors is that the furthest ahead iterator determines where the underlying cursor is in terms of the dataset, which is why "look-behind" calculations can be done but not "look-ahead" if you want to update the dataset in one pass. ... View more