Latest Contributions by JoshuaBixby

Since the SQL Server 2014 question has been answered, I will just point out the latest release of ArcGIS for Server is 10.3. ... View more

One could argue this is a bug, but even if it is a bug, there is a low probability it will be addressed.  The issue appears to be cleaning up the ArcSDE application server connections, and the ArcSDE application server no longer exists at ArcGIS 10.3.  Sure, ArcGIS 10.3 clients can connect to existing ArcSDE application servers (I think), but Esri won't put a high priority or much resources into addressing an issue with arcpy.DisconnectUser when the issue is dealing with retired functionality. The SDE command line tools also don't exist at 10.3, but if older versions of them are working for you, I would say that seems like the best path forward.  Regarding Plink, why not just install the SDE command line tools on the machine the database maintenance script is running on.  That way, you wouldn't have to use Plink and remote into another machine. Since the ArcSDE application server is dead, I would suggest you start considering changes to your architecture in the coming year or so.  In the meantime, goes with whatever works for you because getting potential bugs fixed for retired functionality is an uphill battle. ... View more

See the following:  Will the ArcGIS for Home Use Program will include ArcGIS Pro? Although the answer seems to be yes, I am not sure whether that applies with the prerelease versions of ArcGIS Pro, which is where we are still at today. ... View more

I wouldn't go as far as saying you can only use one cursor at a time.  There are several factors that affect how and whether multiple cursors will work together on a data set.  The types of locks that the cursors require are one factor.  The order of which cursors are opened first can be a factor.  The backend data storage format is another factor.  When it comes to using multiple cursors to access spatial data, having the data in an enterprise DBMS makes a big difference. ... View more

If you install 64-bit Background Geoprocessing, background processing in ArcGIS Desktop only uses the 64-bit version.  Now, you can disable background processing and keep everything in-process, which would be 32-bit, but you can't do 32-bit background processing when the 64-bit product is installed. Installing the 64-bit Background Geoprocessing won't change ad-hoc Python code in the interactive Python window, that will still run 32-bit.  That said, since ArcGIS Desktop is compiled to be Large Address Aware, it seems 4 GB of address space is available on 64-bit Windows instead of the regular 2 GB. If you wrap your code into a Python Toolbox and run it as a tool, I am not sure whether that executes in the background as 64-bit or would still be in-process and 32-bit.  I know I have tinkered with this before, but my memory fails me at the moment. For me, the most straightforward way to use 64-bit Python and ArcPy is to develop the code and execute it outside of ArcGIS Desktop, a standalone script some might say.   I develop in PyCharm usually, so I just configure PyCharm to use the 64-bit Python interpreter and ArcPy instead of the 32-bit.  When I install 64-bit Background Geoprocessing, it usually automatically updates the IDLE (Python GUI) shortcut in All Programs to use 64-bit instead of 32-bit. ... View more

Bigger picture, you don't need to be using both search cursors and update cursors since both cursors are open on the same FC.  You can iterate over an update cursor without updating any values, in effect using it like a search cursor.  Usually you wouldn't want to do that because it creates more locks and may have a bit more overhead in terms of performance.  In this case, since you are going to open update cursors on the FC already, just work with update cursors. Furthermore, you should be able to restructure the code to do everything with a single update cursor.  Instead of creating a new update cursor each time, since your insertFD lists aren't doing anything anyways, you can just reset the cursor and iterate over it again.  Resetting a cursor and reusing it is much more efficient and clean in terms of locks than recreating new cursors every time. ... View more

Since you are using a search cursor and update cursor against the FC at the same time, and the search cursor creates the first set of locks, it may be causing an issue since the update cursor will want to generate more locks.  Not sure, just thinking aloud. One thing to try, put a del rows statement at the bottom of your try statement (indented to the same level as your search cursor statement).  Deleting the search cursor explicitly will more cleanly remove the locks before you move onto the next FC.  In theory, reassigning the rows variable to a new search cursor object should release the locks on the earlier search cursor, but that may not be happening cleanly. ... View more

Regarding your use of the older/original UpdateCursor, you are using incorrect syntax.  You are getting lucky, if one wants to call it that, because there is a bug in the UpdateCursor where passing a Python list instead of a text-based where_clause causes the where_clause to be ignored.  In effect, using cursor = arcpy.UpdateCursor(fc) generates the same cursor for you. The fact that switching everything to the Data Access cursors meant the code didn't work at all, not even the first FC, is telling you something is wrong with the code even for the first FC.  What exactly happened when you use arcpy.da UpdateCursors?  Does it run and nothing happens?  An error code is generated? ... View more

By stall out, what exactly do you mean?  Does it stop running and hang?  Does it complete but not update what you expect?  Does it stop running and generate an error? ... View more

Which version of ArcGIS Desktop are you using?  Does ListVersions in the ArcPy Data Access (arcpy.da) not work for you?  Or, do you want to only work with a subset of all versions?  Or yet, do you not know how to iterate over a list? ... View more

At first glance, you seem to be mixing older/original cursors and the newer data access (arcpy.da) cursors.  Your syntax for the update cursors seems wrong.  The arcpy.da.UpdateCursor syntax is (in_table, field_names, {where_clause}, {spatial_reference}, {explode_to_points}, {sql_clause}) whereas the arcpy.UpdateCursor syntax is (dataset, {where_clause}, {spatial_reference}, {fields}, {sort_fields}).  You appear to be passing your field list as a where clause to your update cursors. Overall, I recommend switching to using all arcpy.da cursors. ... View more

Tough part about forums and not knowing people personally, comments can be read multiple ways.... Anyhow, two other bugs were issued related to the aforementioned Support case:  BUG-000084666 and BUG-000084667.  Even though the impact might seem limited on the surface, cases like this can point to larger issues with managing precision deeper in the software stack.  What isn't stated in the public-facing Support system is that the "bug is not coordinate specific and it is not spatial reference specific."  Although the illustrative example involved working in a coordinate system that presented an unusual real-world case, it has been demonstrated the issue is abstracted from a single coordinate system. In the end, the true impact may be small but maybe not.  It isn't always easy to tell until developers dig into the bug deeper. ... View more

Esri Support issued a formal bug: Bug BUG-000084665: Attempting to create an equilateral triangle with lengths of 0.0027 gives, "The feature could not be created. The geometry is invalid." However, the distance between each vertex is greater than the XY Tolerance (0.001) and the XY Resolution (0.0001). Alternate Solution: Ensure the distance between each vertex is at least 0.0029 units. I can't say I am a fan of the Summary text.  I think it downplays the scope and impact of the bug, i.e., someone might think it is about triangles and not the much larger issue of all polygons and lines. The workaround is basically to not trust the XY Tolerance or XY Resolution of spatial references.  Caveat utilitor. ... View more

OK, I think I got a better picture of what you are after now.  Are you planning on using ArcGIS API for JavaScript and consuming GIS services or build something in ArcGIS Online?  I ask because the example you provide is javascript driven and tends to lend itself to Web-based APIs.  Unfortunately, my background isn't in those Web-based APIs, so I don't think my advice would be worth much. ... View more

Did you see the screenshot before you posted it?  I see your Inbox and other stuff.  Trimming the screenshot to relevant parts makes it easier to work with. Anyhow, yes, layer files are supported, but I think you are looking at this from the wrong perspective.  Layer files reference data sources, so are you sure the actual data source is supported?  Are you working with a personal geodatabases possibly? ... View more