Latest Contributions by JoshuaBixby

ArcPy already has a full-blown context manager for managing geoprocessing environments:  EnvManager—ArcGIS Pro | Documentation ... View more

Although I agree ArcGIS Pro, and especially ArcGIS Server, has lots of unnecessary overhead if you only want to run ArcPy, what are the licensing issues you run into with ArcGIS Pro in the cloud?  ... View more

Unless you are willing to provide a working link, or an example result file, it is difficult for anyone to comment when they have no idea what exactly the XML contents look like. How is this related to your other post? (OGC URL is not working - Esri Community).  You haven't responded there but seemed to be asking a similar question. ... View more

Not to nitpick on semantics, but saying "Microsoft's Crowd Strike software" implies: 1) the software is called 'Crowd Strike', and 2) Microsoft either develops or owns the software.  CrowdStrike is a company and not a software product, and the company is not owned by Microsoft.  The affected software is Falcon Sensor, part of the CrowdStrike's Falcon multi-platform security product.  The botched update causing the issue only impacts Microsoft Windows software, but that doesn't mean Microsoft has anything to do either directly or indirectly with what is happening. It is impossible to say whether your hosted feature services are impacted by the CrowdStrike issue because no one in the community here knows your organization's technical architecture and software products. ... View more

The containerized version of ArcGIS Enterprise is Introduction to ArcGIS Enterprise on Kubernetes—ArcGIS Enterprise on Kubernetes | Documentation ... View more

Regarding your first question about ArcSOC.exe, you won't need to do anything for that process if you address the ArcGISServer.exe process because CPU affinity is inherited by child or spawned processes.  ... View more

Looks to have a misconfigured certificate on the web server:  NET::ERR_CERT_COMMON_NAME_INVALID ... View more

Spent time working through the issue with Esri Support, and it is complex.  The issue has nothing to do with any specific type of workspace, nor anything with CalculateGeometryAttributes itself, it has to do with how Esri has structured their code for hundreds of Python-based tools like CalculateGeometryAttributes.  There are literally hundreds of tools that will all fail to run with Python multiprocessing.  The crazy part is, for most of the tools only a single line of code needs to be changed to make it work. The question then becomes are these issues with documentation or the software, are these defects or enhancement requests, etc....  I haven't closed out the Esri Support case yet, but I suspect it will be a mixture of documentation defects and software enhancements that come out of it. In the meantime, one can at least roll their own code with ArcPy DA cursors. ... View more

Beyond the filters, you are not correctly using the ArcGIS Arcade DateOnly function.  You are passing the function a feature set and column name, which it has no idea what to do with, so that could be why null is getting returned.  ... View more

Are you sure the issue is date related?  If you remove the date-related queries do the other queries work as expected?  If the GRID_ID query is not working correctly for some reason, then it won't matter whether the MARKED_YEAR query is working or not. ... View more

Commented at python - ArcPy function produced None values in multiprocessing - GIS SE, it looks to be a defect with CalculateGeometryAttributes. I was able to create a minimum reproducible example and have submitted to Esri Support to log a defect. ... View more

I suggest you start here:  ArcGIS Enterprise Pricing | Contact Us for Cost & Configuration Options (esri.com) .  Although the web page title says price, it is really more information about licensing than pricing itself.  You need to call Esri to discuss pricing. ... View more

zoomToAllLayers in MapView—ArcGIS Pro | Documentation ... View more

I think this is impossible to implement.  Currently the Select Layer By Attribute tool is a SQL clause builder, and the available conditions in the drop down all map to standard SQL operators that nearly every data provider supports: SQL operator = is equal to <> is not equal to < is less than <= is less than or equal to > is greater than >= is greater than or equal to [NOT] LIKE begins with does not begin with ends with does not end with contains the text does not contain the text [NOT] IN includes the value(s) does not include the value(s) IS [NOT] NULL is null is not null When you go outside the common SQL operators above, the implementation of a given operator starts to vary widely across data provider, to the point of not being supported at all.  Additionally, all of the common SQL operators above operate on a given row where finding duplicates requires looking beyond a given row to an entire dataset itself. There are numerous ways to find duplicates via SQL, and someone can always write custom SQL in Select By Attributes, but that requires knowing what the underlying data provider supports for SQL. I understand the convenience factor of having such an option, but I just don't see it implementable without completely refactoring the tool. ... View more